Re: [all] Requirements default publication

Hi all,

 > Attached you find the requirements for a default publication that
 > Christian and I wrote down according to our discussion at the meeting
 > yesterday. Please review.

have we already stated the purposes of this 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?

(the non-commented items are +1)

Document URI space
------------------
- No predefined URI space
- No URI-doctype mapping

So we will use sitetree framework + DoctypeMatcher?

- 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

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?

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

- Homepage: simple content doctype

Here I could even imagine to use the XHTML "doctype". Homepages
tend to be stylish and differ very much from the content pages.
I wouldn't force the user to use the content doctype for the
homepage (it tempts to tweak the doctype, I know this from
cocooncenter).


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

Do we have such a schema? Otherwise - what about the Forrest doctype?


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?

-1. There are enough good HTML editors.

Navigation
----------
- Navigation is built automatically

I guess you mean the navigation elements are built
from navigation files?

Andreas


- Navigation folding (static)
- Highlighting of current location

Components
----------
- Access Controller
- Publisher
- Creator
- Revision Controller
- Scheduler
- Site Tree Manager
- Navigation Framework
- File Upload

I would add the 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

- Help
   About this publication
   Lenya documentation
   About Lenya



_______________________________________________
all mailing list
[email protected]
http://wyona.org/cgi-bin/mailman/listinfo/all