I'm trying to figure out what is best practise for when you have a topic which has different content for different versions of a product.
Initially, I decided to have a single topic file, containing conditional text. However, when you have multiple versions, this can get rather complicated and probably prone to error.
In some cases, I decided to have multiple topic files, one per version. This is clearer to work with. Unfortunately, the downside is that links to the topic must themselves be replaced with multiple links (one per version) with relative conditions.
Neither way seems the most efficient - is there perhaps even a better way?
P.
Single topic with all versions vs one topic per version?
-
- Senior Propellus Maximus
- Posts: 2630
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: Single topic with all versions vs one topic per version?
For me it depends just how complicated it gets if all the content, with all the conditions, is in a single topic. If it's just a mass of colour then I create separate topics for each target (sometimes using snippets for bits of text that are common across all targets), add all the topics to the TOC and condition them in the TOC.
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx