Approach to documenting optional/licence-dependent features

This forum is for all Flare issues not related to any of the other categories.
Post Reply
IUseItAsACrash
Propeller Head
Posts: 22
Joined: Wed Jan 30, 2019 2:37 am

Approach to documenting optional/licence-dependent features

Post by IUseItAsACrash »

Hey folks -

I am in the process of documenting software that has one general UI which displays different options based on the purchased licence. For example, in dialog boxes there will be additional options to configure if a certain licence is active. Since my plan is to create only one online output, I wonder how you approach situations like these.

Also, the software in divided up into 4 modules which can be combined freely, making it hard to create a specific online help for the individual module combinations. I asked this question bhere before but havent quite found a satisfying solution.

Another question: What is the best way to approach situations in which the content of dialog boxes (in wizards etc.) changes depending on the previously selected options?

Any thoughts are appreciated!

Thanks.
Post Reply