I am building a website with Atlassian's Confluence to fulfill these goals:
- Document a complex project with multiple websites (Product Management)
- Train non-technical staff to use it Store APIs, repositories, and libraries (Developer Documentation)
- Test automation and quality assurance data and information
- Will be re-used for final users (knowledge base and tutorials)
Note: the platform will be both used for internal and external users with different UIs.
My Confluence Sidebar has a tree structure which follows the same as the website pages
My original idea was to make this test accounts child of Single Sign-On (contextual)
However, since the person (Quality Assurance) is already familiar with the platform he would like to have minimum information as possible.
However, that could cause a problem since new people are not familiar. Also, they avoid reading the website (they want to be explained in person) which makes documentation a waste of time.
Question: should I make the information architecture together (child and parent in the tree structure) or separate as per suggestion from quality assurance (current screenshots)?
I think this is an eternal dilemma, you try to separate things and it becomes hard to manage (inconsistent, error-prone, scattered and redundant info), while when you put things together people complain there is too much stuff to go through- I have conflicting feedback.
Question2: any other tips on how to solve this problem? Confluence has to search filters and I am making images and videos as much as I can but still looking on the best approach