Re: Re: [all] Requirements default publication

Andreas Hartmann <[email protected]> writes:

> >>a) low entry barrier
> >>b) best practise showcase (exploring for us and learning for others)
> >>c) show what's possible
> >>
> >>I guess (b) is the main point, isn't it?
> > I think it is mainly b but could possibly be made into a.
> 
> Then I would consider not to use the sitetree framework.
> I know that it will be a integral part of Lenya, but I'm
> afraid it makes the sitemaps harder to read and harder
> to understand what's going on.

I think we'll have to define what we mean when we say sitetree
framework. I envision something simple along the forrest site.xml
mechanism. And I can't see the default publication without it. How can
you autogenerate the navigation if you don't even have site.xml?

It might make the sitemaps somewhat harder to understand but the
intent of the default publication (in the sense of (b)) is not to
*completely* understand all the intricacies of the publication but to
learn how to extend and adapt it to fit your needs.

> >>I'm still against the XHTML doctype if this shall be a
> >>best-practise publication. I agree that this is useful to
> >>integrate existing content. But maybe we should point to the
> >>drawbacks of this approach?
> > Sure we can. It just seems that the XHTML doctype is a very pragmatic
> > approach which can simplify things.
> 
> It only simplifies the initial effort and editing with conventional
> editors. IMHO everything else is more complicated.

I think people want the XHTML doctype, and I think if we ever get the
document describing the xhtml method
(http://cvs.wyona.org/cgi-bin/bugzilla/show_bug.cgi?id=89) this could
make for a nice and simple example.

> > No, the intent is to add pages to the navigation as they are added to
> > the publication. I know this has problems when you start adding
> > hundreds of pages but again KISS.
> 
> How can you define the order of navigation items?

You can't. It's as simple as that :-).

> By manually editing the generated files, or is it planned
> to add, e.g., a "insert before" / "insert after" combo box?

I don't think so, no.

> In my eyes, it is useful to separate navigation from URI structure
> and to enable the integrator to customize the navigation.

The basic mechanism of the sitetree mechanism definitively has to
scale to other methods of editing.

-- 
Christian Egli       [email protected]   +41 1 272 9161
                     Wyona AG, Hardstrasse 219, CH-8005 Zurich
Open Source CMS      http://www.wyona.org http://www.wyona.com