Currently, Phriction pages list child pages in a "Document Hierarchy" section at the bottom of the page. This listing is hard-coded as 2-ply with a fallback to 1-ply if there are too many direct children.
{F6849508}
The "Table of Contents" is available in a popout menu:
{F6849510}
The page actions are in a standard curtain UI, embedded into the document:
{F6849521}
These behaviors are //okay// but not //great//. I'd like to make these changes:
- **On Wide Screens, Put Navigation and Actions at the Edges**: On normal desktop-sized screens, a lot of real-estate is unused. The actions take up space in the document and the navigation tree isn't visible on screen. The UI would be improved by moving navigation to a persistent left-side menu and actions to a right-side menu.
- **Anticipate Comments**: Visual comments are some ways away, but this design should leave room for inline comments.
- **Provide More Control**: Users should have more control over document hierarchy display.
- **Offer Display Customization**: Provide at least basic support for header colors, backgrounds, images, etc. The primary goal is to let user make different sections of the wiki look visually different.
- **Support Locking Pages**: See PHI1366. The existing lock behavior can likely extend easily to Phriction pages.
These adjacent changes are also desirable:
- **Improve Anchor Behavior:** (T4280) We currently auto-generate very clumsy anchor names and don't support custom anchors. Better anchor generation and more control over anchors would be nice.
- **Apply These Changes to Diviner**: Diviner could benefit from the same navigation treatment. Some of this could probably go to Phame eventually, too.
- **Support `{index ...}` (or similar) as a Remarkup Element**: (PHI1412) Roughly, provide a remarkup element for embedding the hierarchy of some page in another page. This hadn't occurred to me but I think it's quite clever.