<rant>
MODx and its layouts are mutually exclusive. Period!’
Anyone is welcome to design a layout in any fashion. I would argue that the accessibility merits gained by designing sites only using ems can in many cases be defeated by the purpose, market, user-expectations, user-level and overall information structure of a site. Some sites work well with a completely fluid layout, some sites don’t work at all. Visual design can impart as much of the message as the message itself. Design is communication. Some designs have boundries of width; some of height.
There is no trend or movement toward and entirely elastic web. There is no rule that says a site must be fixed to 768px wide or 950 px wide but things like user accepted norms, and interface conventions mean that jumping into foreign interface design can cause problems.
I design websites for business. The bottom line there is as a vehicle for selling and marketing of a product or service not as an exercise in ideal scenario user interfaces. Fulfilling user need, and making usable interfaces and presenting information in as good a manner as possible is the priority.
</rant>
Deep breath...
<rant class="calmer">
Designing crossbrowser compatible elastic templates in MODx is as easy to do as a standalone HTML page. HTML+CSS. Then slap in your MODx tags and kapow an elastic template. MODx is not Wordpress, Joomla, Mambo, Drupal. It is a content management framework and it is very much a DIY developers application. I don’t know very many people I have come across this site to use a template for MODx.
I would suggest that most people on this site and who use MODx use it because they can easily use their own creation without having to put in loops or copious numbers of function calls into the template or be stuck using dozens of rigid templates that you can’t change because they were poorly written in the first place.
</rant>
Cheers,
Jay
BTW I have been toying with creating a clone of the default Wordpress theme for MODx--just for laughs. -J