Lists Home |
Date Index |
On 2/24/06, Anthony Ettinger <email@example.com> wrote:
> > Generally the rational for using templates to build a Web site is to
> > make it easy for some larger group (over space and/or time) than the
> > original developers to maintain the site. XSLT would not be my first
> > choice for the development and maintenance of the higher level
> > abstractions that can be used to build a Web site. Rather, build a
> > vocabulary designed for those needs and keep the XSLT in the core
> > where it's not going to be exposed to random Web designers.
> From my experience you have this problem regardless of what
> vocabulary/technology you're using. Recreating a presentation
> vocabulary, or simply using xhtml may still result in "bad design"
> phenomenon. My reasoning for using xsl is to have an include/component
> type functionality with parameter passing. And simply creating a new
> markup to facilitate this seems redundant.
Not sure what "problem" you're referring to?
XSLT is a Turing complete language. By using it as your template
language you not only force everyone who designs for your site to
learn XSLT you open a huge can of potential performance, maintenance
and security issues.
You don't need to invent any new languages for includes.
Not sure what you're real use cases for parameter passing are?
Generally I haven't found a need for such with a properly designed Web
site (other than within the site controller itself, but that's another
issue altogether). Rather I end up including XML fragments as
needed. Thus, every piece of information is maintained in one spot
and one spot only. The data that creates the site in the XML files,
the presentation of that data in XSLT. Separation of Concerns is a
good thing in this case...