Survey of existing page views and markup: Difference between revisions
From MoodleDocs
Amy Groshek (talk | contribs) |
Amy Groshek (talk | contribs) |
||
Line 3: | Line 3: | ||
* Classes .box and .generalbox are utilized in many screen views, but not consistently across different resource and activity types | * Classes .box and .generalbox are utilized in many screen views, but not consistently across different resource and activity types | ||
* Most resources and activities use a combination of IDs and classes to style components | * Most resources and activities use a combination of IDs and classes to style components | ||
==Notes== | |||
* As first concern is non-editing view, student views will be the focus of this initial survey | |||
==File resource== | ==File resource== |
Revision as of 23:09, 6 November 2012
Overall Conventions
- First, the no-brainer: page content is inside of #region-main #region-content
- Classes .box and .generalbox are utilized in many screen views, but not consistently across different resource and activity types
- Most resources and activities use a combination of IDs and classes to style components
Notes
- As first concern is non-editing view, student views will be the focus of this initial survey
File resource
Visible Conventions
- First-level header (optional)
- Content embedded or as link
- Content description, "intro"
Folder resource
Visible Conventions
- First-level header (optional)
- Content description (intro) in its own box
- Content as dynamically generated folder tree (in its own box)
Page resource
Visible Conventions
- First-level header (optional)
- Content (with its own border)
- Last-modified date
URL resource
Visible Conventions
- First-level header
- Either embedded object presenting HTML content at URL or link to URL
- Content description/intro (in border)