I've spent the last couple of weeks getting my head round Flare, and trying to plan the best project structure for our needs. I've still got a lot to learn, but I' think I'm ready to try a "proof-of-concept" using some content that has been crying out to be single sourced.
I think that eventually I will have some global content (stylesheets, conditionals, variables, some graphics etc) and probably one project for each existing document or group of related documents. I was planning to use global project linking eventually, but I don't want to get bogged down in the details of that just yet - I'd prefer to get some useful output first then fine-tune the global structure and content later on.
My question is - if I adopt this approach, will I land myself with a big headache later on trying to move things around, or will that be relatively simple once I'm sure what I'm trying to achieve?
If this goes well, then as well as having proved that Flare meets our needs, I will have the basis of a real project, with real content that I can work on for real. As a sole tech author, with very little spare time between product releases, that's really important, so I need to increase the chances of producing something useful from the outset, and avoid making obvious mistakes.
All opinions and advice welcomed.
