Flatten project structure upon generation

We have a WPF/C# application that has a help string in each XAML file for context-sensitive help. When the user is on the Login page we have a help string that tells the context-sensitive help which topic to display. In this example the string might be "login". We take that string and append ".htm" to the end of it to find the appropriate help topic file inside of the CHM file.

If the technical writer puts the login.htm file into a Robohelp project folder named "\basics\login.htm" off the root then our application would need to look for the login.htm in the same path. Right now we only have the word "login" on the screen. And of course different topics would have different folders so there would be no way we'd be able to tell by file what to append.

What we will have to do is to go back into the code for every screen and change the help string to actually represent the full path of each help file. Which isn't a problem really. That will just have to happen for our next release.

I think the biggest issue we're having with Robohelp is lack of knowledge on how the product works. We're adapting but we make some missteps because we don't see the consequences down the road. We've watched some videos and gotten the basics down but there are more "connecting the dots" things that we need to consider and that will come in time with more and more use.