Second, every page should have the ability to assign a CSS file to it. That way a student can use Mahara to add the content, but them use a CSS page to define the fonts, colors, positioning, etc.
The tags at the bottom of a page should produce HTML5 tags. The student credientials should be iCard format.
]]>Another thing which would be required for better usability would be having the content tabs area floatable. That way you can scroll right to the bottom of the page and still be able to drag and drop content blocks ontoo the preview area.
Mike
]]>
One approach might be to split the page into header, body and footer sections, which gives a simple sequencing schema. (Or header, body section 1, body section 2, body section x..., footer.)
Another possibility, though more ambitious from the point of view of implementing it in Mahara, is to use a CSS framework like the 960 grid system. http://960.gs/
I will take a look at Drupal panels and try to get the gist of the technical implementation.
Mike
]]>Drupal panels:
Blogger body layout options:
]]>For interoperability (with Leap2A) the first thing that strikes me is that any content should be able to be reproduced independently of layout. Linearised, if you like - there needs to be an order - and this may be a similar point to screen readers. If we could separate content and layout - a bit like stylesheets separate content from colours, fonts, sizes, etc. - then the content is more likely to make sense even when separated from the layout. Come to think of it, you probably want the same for mobile devices - at least the ones with smaller screens.
Perhaps people could think about that and I'll dig up what we were starting to write in Leap2A...
Simon
]]>