There have been times in the past, where I indeed questioned myself if the added complexity was really all that necessary. I am glad we didn't revert for our technical/help documentation with Flare.
All that staying back way past, who knows when, putting some time in on weekends - all just to standardize content in some way, fixing indexes, converting snippets, creating a master project, creating a usable style sheet for print and online. Was it all really necessary?
Just today, I discovered we will be releasing a new edition to an existing product line.
Same product, same code base, slightly reduced feature set, reduced installation steps.
70% the same, but with changes/reduction in the remaining 30%.
Am glad we single-sourced and spent the time to fix the documentation for single-sourcing as of last year all through this year. Its taken a long time to really get our docs ready, very demanding task, but i guess its paying off.
I am glad we started single sourcing
I am glad we started single sourcing
If you submit your bug feedback request here, the more likely it'll get fixed or included in a future release
Open Utilities PageLayout Resizer for Flare/Blaze | Batch builder
Open Utilities PageLayout Resizer for Flare/Blaze | Batch builder
Re: I am glad we started single sourcing
single sourcing is rough. you have to change how you document (and in our case try and prepare a dozen or more product that share common features) but the payoff will be well worth it in the long run.
i am glad single-sourcing is finally paying off for you (and your team?)
edit: i was gonna say more ... but i currently hate breathing ... thx pollen!
i am glad single-sourcing is finally paying off for you (and your team?)
edit: i was gonna say more ... but i currently hate breathing ... thx pollen!
Flare: I bought it ... so that means I can break it, right?