What’s the best approach for multi-layered project documentation?

One piece of advice I've found helpful is to write the user manual first. It might sound tedious, but it forces you to see things from the user’s perspective instead of just listing features.

Confluence is a solid choice for knowledge sharing with less technical audiences. For developers, sticking to good old markdown documentation in Gitea usually does the trick without any fuss.

A layered documentation strategy like yours is smart. Remember to keep user manuals simple and focused on tasks. IT documentation should be practical and straightforward, similar to a runbook. Dev and database docs should closely reflect the actual code and database schema so they remain relevant and useful.

I really like separating documentation by audience instead of trying to put everything in one place. For user manuals, I’ve had great success using tools like Flipsnack to create browsable guides. It makes the info feel more accessible. Markdown works fine for the dev stuff, and platforms like Confluence or Notion are great for IT documentation.

I generally think about documentation in terms of who it's for and whether it's permanent or temporary. For instance, user stories might be less valuable once the discussion is over, while API docs should be stable. It helps clarify what needs to be prioritized.