...
- Default presentation layer using css and standards compliance.
- Minimise difference in terms of output to the browser Maximize common markup for browsers so that we really can share skins across institutions. For example using
- consistent way of handling channels, widgets, images, conventions and standards for naming.
- Need to genericise a standardised layout as far as possible though, and leave flexibility with the end using institution to customise to suit their own visual style.
- Try move away from rework upon upgrades and towards some sharing
- Increase customization possible through CSS
- Reduce work while upgrading between uPortal versions
- Ease customization for institution specific look and feel
Suggestions:
- Channels could have some intelligence about the amount of screen-space that they need in terms of column widths, rather than leaving this to the user to deal with.
...
- Adding a tab - need to add a tab, then a column, then a channel - if we could slim this down that would be a huge improvement in and of itself.
...
Discussion
- Not happy with the current customisation options - need improvements to ease of use, accessibility and end-user discovery.
- Consensus that we are turning it off or end-users are not using it - quite a lot of users don't use because it's not that important to them
...
- Jason taking the Rutgers theme, ripping out the logos and adding to possibly 2.5.1. and 2.6
- standards compliant version of SLM
- css driven for layout.
- improvements mostly 'cosmetic', less markup being moved around, quicker rendering, prettier!
- Collier @ VT will contribute the VT theme - with icons ripped out etc
- Sarah modeless integratedModes
- Duffy at Arizona - can add in some tree-controls type layouts.
Rutgers Layout
...
- .
...
General rule: If anyone has something to contribute and it compiles, then it can go in the sandbox for comment (Sandbox - an area of CVS that stuff that's not quite finished and ready to go into the main code tree).
...