Re: [xsl] Modern web site design with XML and XSLT

Subject: Re: [xsl] Modern web site design with XML and XSLT
From: Philip Fearon <pgfearo@xxxxxxxxxxxxxx>
Date: Sun, 3 Jan 2010 13:22:10 +0000
One other simple workflow to consider (the one I currently use for my
website):

1. Design basic website in a WYSYWIG XHTML/CSS desktop-based web design tool
2. [Key difference] Still on the desktop, use a specialist XSLT (1.0
or 2.0) based tool to automate repetetive transform tasks on your
website pages that web design tools are (generally) ineffective at
3. Load XSLT modified website back into the web design tool, check the
visual design aspects using its built-in preview tool
4. Use your preferred tool to upload your verified website onto your web
server
5. Use server-side components to transform and cache, using XSLT,
those parts of your website, that must be updated in real time

Benefits
-----------
1. You can use XSLT 2.0 features
2. Faster loading web pages (as well as being customer-friendly, this
may be important in future for Google page-ranking)
3. SEO friendly - Web bots process 'static' XHTML pages more effectively
3. A 'green' solution: Saves energy (at measurable levels for popular
websites) because the transform is done just once for most of the
website, rather than on each page load
4. Because the transform happens prior to uploading the site, you can
easily check for coherence and verify the site visually
5. Depending on the tool, you can also generate and check
PDF/OOXML/ODF/EPub copies of your website at stage 2


Phil Fearon
http://www.qutoric.com

On Sat, Jan 2, 2010 at 2:31 PM, Rob Belics <rob_belics@xxxxxxxxxxx> wrote:
> You can't find a book with that title. Some naive questions. I'd like to
> take an ecommerce online application I've written and convert all its
> drop-down, CSS, blinking lights, Ajaxy goodness to all XML/XSLT all the
> time but, as I have just started tinkering with this, I run into
> articles about how browsers of today don't support XSLT or it won't work
> with HTML5 and all those other things that make one question whether the
> effort is worth it. I think XML is ideal and I don't know why I couldn't
> convert everything over.
>
> I need either encouragement or discouragement that my (unknown to you)
> web site that uses bleeding edge modern web development techniques
> (CSS3, HTML5, Ajax/Javascript/DOM, etc., works in all browsers) can be
> completely recreated without worry of gotchas halfway through the
> process. That something won't ever be supported so I'm stuck and all
> that.

Current Thread