Current Confluence Landscape

uPortal spaces in Confluence

uPortal space

The generic uPortal wiki space provides a relatively open, relatively wild, low-barrier-to-entry space where people can contribute documentation and share their tips, techniques, and solutions. It's chaotic and noisy, but it's low barrier to entry and it's okay for people to share three or four different stats recorder implementations and instructions. Random thoughts and opinions, appropriately annotated, are welcome here. Openness is valued over clarity groomedness.

uPortal 2 Manual space

The Manual is a place for well-baked, high-effort, well-groomed documentation. Some documentation may start in the uPortal space and mature to be suitable for inclusion here.

There's an aggressive, some might say pedantic, but well-organized page naming scheme involving prefacing page names with numbers, allowing the space to auto-sort and auto-tree.

There's an important tree-like navigation regime applied here, where content is organized into chapters and sub-sections and so forth. This makes this space relatively more navigable and easier to find one's way around.

Clarity and groomedness is valued over openness. While anyone is welcome to contribute, the expectation is that entries will be edited for content, clarity, grammar, and style, arriving at a manual-like book-like narrative experience, and the expectation is that random thoughts and opinions will not find their way into the manual.

uPortal 3 Manual space

Ditto as the uP2 manual space, but for uPortal 3.

uPortal Development space

This space was intended to do for documentation of project plans and uPortal development values, goals, and tasks what the manual is doing for deployer documentation: providing a clearer, better-groomed, more authoritative, well maintained set of this sort of documentation apart from the chaos of the main wiki space.

Andrew's negative opinion that maybe he should have just kept to himself

This effort has largely failed through neglect and lacks of tremendous amounts of available bandwidth to maintain this space. This is in part because some of the roles identified in the process documented in this space aren't actually staffed and much of the process documented in this space doesn't actually happen. -Andrew Petro