In addition to the previously optimised Resource Pages, Structured Content is the primary means of managing and creating content to be rendered onto course/module websites, as well as ‘alternative formats’ that are increasingly available [PDFs, DAISY, ePub, MP3, Word, Print].
The main work required here was to establish a means for the navigation to be separated but easily accessible from the content, which was achieved as illustrated below:
While most of the Structured Content web views render faithfully (apart from Glossary, not covered this time), more work will need to be undertaken in resolving drag-and-drop activities and alternates to Flash in some cases. Embedded audiovisual content will not display in the player, on screen, but the assets are also hyperlinked so that a more appropriate app can handle these.
In addition to this and the alternative format work going on in parallel (particularly that in improving ‘rich media’ ePub eBooks), there has also been some prototyping work on Android to establish packages of HTML content for syncing offline into an app – which required further work on handling audiovisual content. More on this later, as an update to a prior post on the ‘shell application’, also covered in Anthony Forth’s UK MoodleMoot presentation [see MoodleNews for more].