Hello @Isaac Klein
It's a tricky question because the perception of good will differ from a company to another, or even between two teams in a single company.
For example - this is our public documentation space . It's rendered with Scroll Viewport but the actual structure is 100% identical to what we have on Confluence. Each section corresponds to our platform module (with 2-3 well justified exceptions). That was our decision because it best matched the structure of our product.
Having said that, from the content pro perspective, your Confluence space should...
- organize information into spaces (by team, by subject matter, it's your choice)
- clear unambiguous structure
For example, when creating top level pages, they should represent one level of content. Fruits, Vegetables, Diary, Meat. Going Fruits, Oranges, Vegetables... is a no no.
- Don't go crazy with having a page tree 8 levels deep. 4 should be enough.
- No h1 headings in the body of a page.
- ensure style (macros) consistency
- ordered/number list for processes where order matters, bullet list for stuff where order doesn't matter
- don't overdo it with note/warning etc. macros.
- use screenshots with legible text
- don't create giant tables
- use inline links to cross-reference content
- develop and enforce labelling guide
- sort space permissions - who can edit, who can view, etc.
Do not be afraid to experiment and move content around if you feel your structure no longer meets your needs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.