Re: Requirements for default publication II

Christian Egli wrote:
> Hi
> 
> I consolidated the requirements again and added some of the input from
> the discussion on the mailing list.
> 
> Basically the following points are still contentious:
> 
> 1. Doctype: should we have a XHTML doctype? Felix argues that the
>    world wants it whereas Andreas doesn't like it for it's impurity.

I'm not against the XHTML doctype, I'm just against propagandizing it
as a default content doctype.

> 2. Doctype: The simple doctype that we want to use. Is it the Forrest
>    document type or some simple home-grown DTD? Felix prefers the
>    custom home-grown version.

I agree to Felix if we design and *document* a simple schema.

> 3. sitetree framework:
>    Do we roll our own?

 >    Do we use the Forrest mechanism?

Forrest uses an Action that obtains the document type (public
identifier) from the document. This requires accessing the
file for each request, but this doesn't matter when caching
is used. In my eyes, it is a clean and easy solution (if we
extend it to work with schemas).

+1 for the concept

I would suggest to start with Michaels approach (parameter
sitemaps). For the default publication, the doctype parameter
could be obtained using the Forrest method.
Maybe we should just begin and see how it develops.

>    Do we allow for browser-based editing of the navigation?

-1 (not integral part of Lenya)

>    Do we integrate work-flow?

+1 (integral part of Lenya)

Andreas

> 
> Attached is an updated version of the requirements.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ====================================
> Requirements for Default publication
> ====================================
> 
> Motivation
> ----------
> 
> We want to create a default publication for Lenya that
> 
> - can be looked at by a beginner who wants to learn how Lenya works
> - can be used by us to implement new concepts and best practices like
>   sitetree/navigation framework, standard URI space, page envelope,
>   menu framework.
> - provides an "out of the box" publication that can be easily adapted
>   and used
> - the intent of the default publication is not to *completely*
>   understand all the intricacies of the publication but to learn how
>   to extend and adapt it to fit your needs.
> 
> Purpose
> -------
> 1. best practice showcase (exploring for us and learning for others)
> 2. low entry barrier (immediate value after download)
> 
> Document URI space
> ------------------
> - No predefined URI space
> - No URI-doctype mapping
> - URIs can be chosen by the user arbitrarily
> 
> Site structure
> --------------
> - A node can be created anywhere
> - Arbitrary mixture of doctypes
> 
> Doctypes
> --------
> - Two doctypes (as few as possible): simple content doctype and XHTML
>   doctype
> - No collection doctype (just navigation)
> - Homepage: simple content doctype
> 
> Simple content doctype
> ----------------------
> - Editable by Xopus and Bitflux
> Elements:
> - Page Heading
> - Subtitle
> - Lead
> - Paragraph
> - Section heading
> - List
> - List item
> - Table
> - Table row
> - Table cell
> - Image
> - Image caption
> 
> XHTML doctype
> -------------
> 
> - Upload function for XHTML file (including tidy resp. check for
>   well-formedness)
> - Body part of XHTML is extracted and inserted into the content area
>   of the page
> - Check-in upon upload
> - Download function with check-out
> - Editable with Xopus?
> 
> Navigation
> ----------
> - Navigation is built automatically
> - Navigation folding (static)
> - Highlighting of current location
> - Order of nodes in navigation can be edited
> - separate navigation from URI structure (?)
> 
> Components
> ----------
> - Access Controller
> - Publisher
> - Creator
> - Revision Controller
> - Scheduler
> - Site Tree Manager
> - Navigation Framework
> - File Upload
> - Search Engine
> 
> Images
> ------
> - Red dots
> - Upload through file upload
> - Upload screen: caption, no identifier
> - Images on XHTML pages?
> 
> Menu
> ----
> - File
>    New content page
>    New XHTML page
>    Publish
>    Schedule
>    (Delete)
>    Logout
> 
> - Edit (for simple content doctype)
>    Edit with Bitflux
>    Edit with Xopus
>    (Edit XML)
> 
> - Edit (for XHTML doctype)
>    Upload XHTML document
>    Download XHTML download
>    (Edit XML)
> 
> - Tools
>    Scheduler Admin
>    Rollback
>    Create Search Index
> 
> - Help
>    About this publication
>    Lenya documentation
>    About Lenya
> 
> Nice to have
> ------------
> - GUI user administration (as soon as we have it)
> 
> 
> ------------------------------------------------------------------------
> 
>