Hi all
Andreas Hartmann schrieb:
> Thomas Comiotto schrieb:
> On Aug 25, 2008, at 5:15 PM, Richard Frovarp wrote:
>
>> Andreas Hartmann wrote:
>>> Hi Lenya devs,
>>>
>>> there seems to be a consensus that it would be a good idea to ship
>>> the docu publication as an example instead of the default
publication.
>
> I think it's important to ship Lenya with both default and docu
> publication. They have different target domains (i.e. tech-docu
vs. web
> publishing) and both serve as showcase and template for people
building
> their own customized publications. Shipping Lenya with docu
publication
> only will lead to the first impression that you deal with a system
for
> technical documentation only.
That's a very convincing point of view - but might take more resources
for maintenance.
I agree to these points. But instead of shipping multiple independent
sample publications, I'd rather suggest to emphasize the modularity of
Lenya and the publication templating concept.
Here's another random thought:
- Create a "base" pub defining all page generation pipelines
- Use the base pub as a template for both docu and example pub
- Use different layouts for docu and example pub (see below)
- Enable the news module (and other upcoming modules) in the example
pub
All editors should work out of the box in all publications derived
from
the base pub. We can tell people that they risk breaking the editor
support if they don't use the base pub as template. Since the base pub
defines the page flow and the other publications only override the
XSLTs, this should be no problem (given that the editors support the
resource types).
I hear the «we have too many editors and should get rid of some» bell.
This way we would keep the "concrete" publications (docu and example)
minimal. I can imagine this makes it easier to get started with a new
publication.
By using different layouts for docu and example pub, we show how the
layout can be customized.
This sounds very tempting.
But this approach might also add a bit more complexity and dependencies.
We could do the design contest step by step:
1) start with the redesign of the docu pub (regardless of merging with
default pub or not)
2) if we do not merge and develop a web publishing publication, we'll
style that publication in the same way - maybe ask the designer to
help us with it.
WDYT?
Jürgen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
