Re: Re: [all] Requirements default publication

>>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.

>>Doctypes
>>--------
>>- Two doctypes (as few as possible): simple content doctype and XHTML
>>  doctype
>>
>>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.

>>- No collection doctype (just navigation)
>>
>>What is actually the difference? Do you mean that
>>section overview pages etc. can't be created/web-edited/published
>>etc. but only edited as XML?
> 
> I think the idea is to keep the publication as simple as possible and
> therefor not even have a collection type, i.e. each page is either a
> simple doc or a XHTML doc. That means that there are no section
> overview pages. We could add this but it would complicate the
> publication.

OK, I see. That sounds reasonable.

>>Navigation
>>----------
>>- Navigation is built automatically
>>
>>I guess you mean the navigation elements are built
>>from navigation files?
> 
> 
> 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?
By manually editing the generated files, or is it planned
to add, e.g., a "insert before" / "insert after" combo box?

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

Andreas