I was just thinking about this issue today.
As a project manager, I have a pretty predictable reaction to XML/XSL/ETC -
"Great - I can finally separate the warring hordes that are the designers,
content-people, and software developers in my organization when it comes to
web development."
But as Itai points out - how do I deal with the fact that the people
traditionally writing the presentation code, what we called "Webmasters" and
what everyone else simply calls the HTML guys, don't know the first thing
about XSL or XSLT or XML or any of that?
My first reaction, and I haven't had a chance to put this into practice, is
to split the technology folks into two disciplines. One side will handle the
logic code (in Cocoon they'd focus on XSP and server-side Java to output
CONTENT in XML, mainly) and the other side will handle XSL and the technical
details of transforming XML documents. My existing HTML people will continue
writing HTML as templates for the XSL technology folks to feed off of.
And they'll be taking a lot of courses in XML and XSLT since with any luck
we'll have more XSL:FO one day and less HTML. Then they'll start migrating
into that group that does XSL.
--Andrew
-----Original Message-----
From: Uli Mayring [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 2:39 PM
To: [EMAIL PROTECTED]
Subject: Re: web-designing with xslt
On Mon, 30 Jul 2001, Itai Erner wrote:
> my first impression is that these solutions are a bit too complex or
demand
> to much hassle from web designers.
We all have to learn using things, so why should web designers not have to
do that? They had to learn HTML or using Dreamweaver one day.
> if using Cocoon in a large scale application - one might find himself
> openning an XSL school for web designer...
And this is a good thing, too.
> what im trying to figure out is if Cocoon (and other XSL based solutions)
> and the very clean separation it supplies is worth it ? but not just from
> the programmers point of view but from the whole organization?
If your web designers aren't into learning new stuff and keeping abreast
of web developments, then their knowledge will be out of date very
quickly and they'll become less useful to your organisation. If you like
it that way, then you should stick to old-fashioned tools - but if you
want to live on the bleeding edge of the Web, then you should take a look
at Cocoon.
Ulrich
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
