[Grok-dev] Re: I know it sucks, but here goes.... grok.zope.org :)

[Sebastian Ware]

I just want to repost the suggested site structure, since it isn't  
obvious in the layout.

** Evaluate ** (Excite)
  - Introduction screencast
  - Overview (history, philosophy, architecture, features, business  
case ++)
  - "Case Studies" (stories, developer perspective)
  - Code

  ++ The Business Case is for managers

** Learn ** (Educate)
  - Recommended curriculum (suggested reading and learning path)
  - Tutorial
  - Sample applications
  - Forum
  - Online seminars (voice annotated h.234 screencasts)

** Develop ** (Empower)
  - API documentation
  - Best practice (Howtos with sample code (and tests?))
  - Templates (Application, component)
  - Mailing list
  - Bug/feature collector
  - Road map

** Contribute ** (Engage)
  - Guidelines
  - Evangelist Blogs
  - Mailing lists
  - Component directory

Mvh Sebastian


9 jun 2007 kl. 21.23 skrev Alec Munro:

> Hmm, well I'm kind of a fan of the old caveman, but that's not a  
> big deal. I can understand how he's a bit more of a complicated  
> character.
>
> What I would like to see:
> -Recipes. Until recently, I found Zope 3 to be missing a good  
> recipe collection, and I think it would be great to make Recipes a  
> first-class citizen on the Grok site.
> -Source for the website, assuming it's built in Grok.
>
> Other than that, I think this is terrific. Keep up the good work.
>
> Alec Munro
>
>
> On 6/9/07, Lennart Regebro <regebro at gmail.com > wrote:I like this  
> Grok too.
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev