@Peter Hanley - Peter you make a valid point RE less technical users. I prefer using plugins for gewgaws (esp SEO tools and the like), custom content types etc and I think this is a better route to follow for theme developers than to include these in the theme (as a general rule). But at the same time these designers should be lauded for the effort they put in. Perhaps they could be encouraged to notify prospective users there may be difficulties if they change the theme (when appropriate). For my own sites I like fiddling with code, but I hesitate to do it for clients - the next person to support their site should be able to do so without a lot of bother... Back to the topic of this post: I would prefer to see this implementation as a plugin, rather than core technology, and more emphasis placed on developing options to extend WordPress as a fully fledged CMS - but once again keeping the big value of WordPress alive - an easy to use platform for everyone, not only the techs. (We tech types have Drupal to satisfy our technical desires). So once again, perhaps a set of well developed and thoroughly tested plugin options to boost the flexibility could be the better option. My two cents worth of comments!