Right now, this style sheet is a draft, and 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 pages should model this practices as far as possible.
We want campus users to basically follow these standards because:
- Continuity means it is much easier for us to troubleshoot problems for them.
- We can ensure that the macros and arrangements they use will look good on a variety of screens: desktop, notebook, tablet, phone, and so on.
Testing will be required to ensure consistency and reliability of macros, markup, or content arrangement.
Headings
Headings are easy to explain. The Table of Contents Macro is also easy to explain, and draws from headings. I recommend this as a basic element usable by all users.
Panels
Panels are easy(ish) to explain, and are a quick way for users to have callouts that are brightly colored (unlike tables, which are limited to pastels).
Tables
Testing:
- Android: Chrome browser. Tables usable. Look OK.
Recommend Tables as standard form of organization, especially for tutorials.
Columns
Page Layout: Confluence displays columns within sections one after another in mobile. Thus, two parallel columns in desktop are delivered left over right.
I do not recommend columns, because they are in one way or another complicated. Yes, they work in mobile, but they require a level of attention to testing that most users simply won't bother with.