Posted by Amazon on November 13, 2006 at 5:19am
One of the most important and difficult parts of building a site is theming the integrated module output. If distributions are required to support all core themes, then designers will have to ensure that their integrated contributed modules will work with all core themes. This is too difficult. Profile and distribution designers should have the option to included fewer themes in their distribution.
Designers will want to focus on the user experience of their distributions and not on the laborious task of systems integration.
Kieran
Comments
good point
i see no reason why all themes should be supported. no need to impose upon distributors like that.
Been thinking along similar lines, myself.
I've long wondered if there isn't some way that any function responsible for presenting content could not be standardized in such a way that it can expose metadata and formatting along with the content.
A good module supports all themes.
If you develop a module that breaks certain themes, you are clearly doing something wrong: at least you are not passing the HTML generation on to the theme layer properly.
So, as Moshe says: no need to not support any core themes.
http://www.webschuur.com | http://bler.webschuur.com
Bèr, I think Moshe said the
Bèr, I think Moshe said the opposite... and I think it's not a matter of "breaking" themes so much as making sure the output looks decent. IMO, if you just take a core theme, turn on a bunch of modules and go with it, you've potentially got a pretty ugly site ...