Right now, this style sheet is a draft, and not This page contains notes concerning the global appearance of Confluence, templates, and generally administration guidelines for appearance, campus-wide. it is not open to anyone outside User Services and OLI/FacTS. The purpose is to create a set of guidelines for creating Confluence content that can be the basis for campus-wide use, tutorials, workshops, and so forth. This will be a set of best practices to encourage standardization of Confluence content around proven styles, arrangements, and use of macros. ITS
ITS pages should model these practices as far as possible.
...
Developing a best-practice stylesheet will require testing to ensure consistency and reliability of macros, markup, or content arrangement. Below are various features we should consider:
Themes
Currently (5.8) we have only two available, and they are similar. Purchased themese are expensive (up to $2500). We can install a theme builder, but this may bring additional complications and compatibility issues. If we upgrade to Confluence 6, our themes created may need to be rebuilt.
The trouble with the current available themes is that they have a sidebar visible on desktop only. This can provide a table of contents for a space, but that TOC must be duplicated in the body of the page, because it (or the child pages list at the bottom of the desktop page) is not visible in Confluence Mobile.
Tools Available to Users
Headings
Headings are easy to explain. The Table of Contents Macro is easy to explain, and uses headings.
Panels
Panels are easy(ish) to explain, and produce callouts that are brightly colored (unlike tables, which are limited to pastels).
Tables
Tables as standard form of organization, especially for tutorials. Recommended.
...
- Android: Chrome browser. Tables usable. Look OK.
Columns
Several ways to use columns. They aren't necessarily difficult to construct, but they complicate views on various devices. I see this as an advanced feature, not recommended for most users.
...