The merit of semantic markup and web standards for websites cannot be over-emphasized. While it is fairly obvious why this can vastly benefit website design, few realise that web applications can gain the most out of this potent mix.
For starters, the separation of content and presentation means that developers and designers can play well together. When the developers take effort to output XHTML code in a semantic way, giving meaning to the page content, the designers can easily take this away and apply presentation styles to format and control how each part of the pages get rendered. Gone are the days when table or list formatting need to be hard-coded or couple tightly to the application code. By strictly producing content in terms of what they signify (Is that a data table? Or is that best perceived as a list?), developers can defer presentation decisions until the designers can work on them. This also opens up possibilities for content on the page to be reused in a multitude of ways.
Another cool benefit is that different stylesheets can be developed to control how the application screens can be rendered on different media, such as on-screen or on paper. Much like the argument for websites, data and content displayed on these screens can be easily transformed or omitted depending on what’s needed on screen (such as fancy graphics and colours to demarcate areas) and the bare essentials for output destined for printing on black-and-white printers. Not to mention if access by mobile devices are also on the plate, but you get the picture.
In fact, we have been doing this for a while for our own web applications, and this has smoothen our development process where the application screens can be easily skinned to a new look or to blend with existing branding. You can get the screens rendered to a format suitable for print without too much effort (contrast with the traditional way of coding up additional “printer-friendly” scripts). All in all, this method of developing web applications has made it flexible for developers and designers to focus on what they do best and allow for clear separation of tasks. For the target users, what they benefit most is better experience that comes with smaller downloads (verbose presentation rules are left out of the content codes) and better looking screens. What’s not to love about this?
