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 ITS and COLI . 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.
ITS pages should model these practices as far as possible.
We want campus users to generally follow these standards because:
- Simplicity ensures the greatest likelyhood that pages will be accessible in all regimes (browsers, desktop, mobile, etc.)
- Continuity means it is much easier for us to troubleshoot problems for them.
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:
Tools Available to Users
Headings
Headings are easy to explain, and should be used. They are used by Macros (Table of Contents) and accessibility tools.
Panels
Panels are easy(ish) to explain, and produce callouts that are brightly colored (unlike tables, which are limited to pastels). How do they look on Mobile?
Tables
Tables as standard form of organization, especially for tutorials. Recommended. How do they look on Mobile?
Testing:
- Android: Chrome browser. Tables usable. Look OK.
Macros
Table of Contents - lists heading on pages.
Children. Simply lists pages in space. I strongly recommend this for the home page for each space, as well as parent pages for offices. "Page Tree" purports to do the same thing, and we used it in the past, but it is not visible in the mobile browser version.
Verify that these two work on mobile.