> From: Matthew Langham [mailto:[EMAIL PROTECTED]
>
> > We are investigating using Cocoon for our next generation
> product. The
> > internationalization stuff,
> > OK we can handle with the I18n Transformer. But what about the
> > customization? I'd like to start a discussion
> > for ideas on how to extend Cocoon to be able to do this in order
> > to come up
> > with a specification.
> >
>
> What do you need that the portal framework doesn't provide?
> The new version
> that is currently being developed is very flexible when it
> comes to this
> type of stuff. Look at the old version of the portal to get an idea.
That seems like an awful amount of work to customize dozens of pages
for dozens of customers.
Right now when we want to customize a certain page for a certain product,
we just copy the file, name it appropriately, and voila! the designer can
have fun.
I'd like something like:
<match pattern="*/somepage">
<map:generate type="serverpages" src="xsp/somepage.xsp"/>
<map:transform type="xslt" src="style/somepage[_{1}].xslt">
<map:serialize type="html"/>
</match>
