I need to maintain documentation of the same system for different audiences. How do I avoid duplication while still being effective?
I have a publicly-available API, and I also have internal documentation of algorithms that are not meant to be shared publicly. There is also both high-level (overview, conceptual) material and deep details. I'm looking for standard ways to effectively tie them together so disconnects between the two are at least highly visible, without writing custom mechanisms to do so for each project.
Historically my organization has used Doxygen only for low-level design details, but we still have a lot of redundant documentation due to regulatory paperwork... It can be cumbersome to say the least. I know Doxygen provides for public/private tags but I'd like to have further ways of tagging things (high-level, low-level, operational, tool user guide, api user guide, regulatory compliance, etc...)