...
- Valid XHTML/CSS supporting a broad range of standards compliant browsers
- Presentation controlled through the use of CSS with simple markup expressing content
- Graceful degradation in user agents that do not support css.
- Support for mobile browsers
- Support for better print layouts
- Accessibility support (508, W3C Accessibility guidelines?)
- Support internationalization
- Common markup and CSS naming conventions to allow channel developers to produce "widgets" like toolbars, tabular displays, etc. while still allowing individual portals to customize their appearence in a standard fashion.
...
UP 2.5 (March/April?)
- Initial XHTML, CSS selecter naming conventions (id & classname)
- Page structure including elements and logical layout
- Conventions for id/class names (e.g. channels/portlets, controls, headings)
- Support new features such as page refreshes linking to channel anchors
- Should follow JSR-168/WSRP Conventions as closely as possible
- Sample/default CSS skin
- Initial Layout for Simple & Aggregated Layouts
- Serve as a model for future skins/institutional customization
- Provide basic styles & layout for screen, print & mobile.
- Logical breakup for layout/styles/print/etc.
- Place to experiment with CSS skin structure & directory layout
- perhaps explore how to have skins/layouts with shared common elements
...