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 pre-defined styles of text common across word processing and web development applications.  Users should employ headings for outline or nested section headings, for several reasons.

• In Confluence, headings help users identify different sections (and subjects) clearly.  Then, using the Table of Contents Macro, you can rapidly create a self-updating, hyperlinked table of contents on a page. 
• In most other applications, headings do the same things.  For example, try them in Microsoft Word, where you can also install an automated table of contents.
• In all places, headings are used by technologies for the visually impaired, and so are essential for accessibility.

Headings should be used sequentially (Heading 1, Heading 2, Heading 3, and so on.)  Start with Heading 1, and don't skip heading styles as you build your outline.

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 headings on pages.  Configurable based on included headings.  Any lengthy page, with multiple headings (like this one) should have a Table of Contents macro.

Children Display

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.

Horizontal Rule

These are simple lines that can be installed between paragraphs.  A visual accent, they help separate content and can be installed however the user wishes.  

What we