The front page of a wiki space should act as “table of contents,” and more. The ultimate goal is to have complete visibility of every page in a space, with descriptions.
Group the pages into logical groups, and put them under headings.
When new pages are created, whoever created them can add a link to the top page. They get to decide what group heading the page falls under (or whether or not to create a new group heading) and how to describe it. |
Discoverability, discoverability, discoverability. By laying out the entire space hierarchy, you make it easier for someone to find what they are looking for at a glance.
|
The “page tree” macro could be used to produce an automated list of every page in the space, including all nesting. Furthermore, each page could use the “excerpt” macro to declare its own annotation, and the page tree could be configured to display that. While this would make the top-level page easier to write, it has a few flaws:
|
This page acts as an example. Pretend the below describes the pages in a real confluence space.
These aren’t real pages at all, just a visual example.
[fake link] page alpha --- documents the new process for Foo --- UNDER CONSTRUCTION
[fake link] page beta --- big page describing the current process for Foo
[fake link] page b2 --- for Foo Bars --- this page is kinda old
[fake link] page b1 --- for Foo Bazzes --- has an excellent writeup for the blanket legacy process
[fake link] page b3 --- for Foo Quxxes, and the definitive list of project dependencies
[fake link] page gamma --- show how to so something else --- DEPRECATED
[fake link] page omega --- describes something about MFEs (micro frontends)
These are real pages that confluence created by default for this space.
Sample Pages --- one of those pages confluence makes to show off features
Meeting notes --- another of those, as an example
Decision --- more stuff
Product requirements --- blah blah blah
…
…