Hi all,

I've updated http://zode01.lovelysystems.com/ with some improved 
structure and a bit more text. I've added a lot of red "TODO" marks 
where things need completion.

Going forward, I want to identify a few "content champions" as well as 
some other roles. I'm looking for volunteers here. :)

  o *Critical reviewer* -- I would like someone to review the text on 
the site from time to time and offer feedback on clarity, style, 
consistency and message. This person may either act as editor and change 
things on the fly, or just ask the relevant author to change something. 
Ideally, this is someone with an opinion on "Zope" as a whole and its 
place in the world.

  o "Get" section content champion -- needs to complete this section, 
writing about grokproject, zopeproject and probably a manual/source 
install. Needs to write clear instructions that work on all target 
platforms. We can split this section into sub-pages if need be.

  o "Taste" section champion -- needs to complete this section with some 
"tasty" code examples that get people excited about Zope. They don't 
have to be 100% complete applications; rather, they should show what 
sets Zope apart. A developer should be able to read this and think "I 
could get with this". I think we can maybe adopt something from the 
Appetizers section on worldcookery.com, or invenet new examples. They 
could use Grok or plain Zope 3. This probably requires something with a 
strong technical background. I'd love for this to be Philipp, since he 
always does well with this kind of thing in presentations and training, 
though I'm not sure how much time he'll have.

  o "Community" section champion -- needs to provide some details about 
the Zope mailing lists/forums and chatroom. Perhaps include etiquette as 
well. This can probably be cribbed from plone.org/support.

Then, we need a champion for each of the sub-projects. These are:

  - Zope 3 and the "Zope Libraries" -- this is the most important one in 
the short term!

  - Zope 2

  - CMF

  - ZODB

Grok has its own home page, though I think we should keep referring to 
it where it makes sense. Perhaps one day they'll want to join us. ;-)

Each section should have a similar structure. I've populated it for Zope 
3. It is:

  - Front page -- What is it? Why should you care?
  - Download -- download/install instructions
  - Taste -- one page of "why this is cool", on a project-specific level
  - Learn -- any and all *relevant* and *up to date* 
tutorials/documentation, as well as links to books etc. Needs to be 
quality-controlled (there's a lot of outdated or poor Zope 
documentation). We could use the Plone Help Center for this (as per 
http://plone.org/documentation), though for now a folder with pages is 
probably sufficient.

The content champion for each area will probably need to collaborate a 
little.

Here's what I'd like to do going forward:

  o Try to solicit champions from this mailing list as far as we can. 
We're the committed folks (or not).

  o At least get a handle on the "Taste" and "Projects --> Zope 3" 
sections so that these can serve as examples to other projects.

  o Take this to the Zope lists and ask for more help and feedback

  o Ask for help working out a migration strategy from the old site. I 
think this just means "make the old site become old.zope.com, set up 
aliases for any explicit download URLs that people may need, flick the 
switch. The aliases are easily done with Plone's RedirectionTool.

I think we can go live with this in April or May if we keep the momentum 
going. How great would that be? :-)

Cheers,
Martin