[Grok-doc] proposed 1.0 release text

Sebastian Ware sebastian at urbantalk.se
Thu Oct 1 12:36:43 EDT 2009


I am missing "who is this for?" I don't think we should pitch Grok 1.0  
so much as a framework for "beginners". They will only get frustrated.  
I think we should target pioneers who are prepared to drop into the  
debugger and read source code to understand what is going on.

I am adding some suggestions.

On 1 okt 2009, at 17.23, Martijn Faassen wrote:

> Hi there,
>
> I've done some work on a 1.0 release text. Improvements are welcome!
>
> The Grok_ development team is very happy to release Grok 1.0. Grok 1.0
> is the culmination of 3 years of work after the start of the Grok
> project in late 2006. It presents a stable development platform to
> develop powerful, extensible web applications. Grok is the result of
> years of work by the large Grok development team.
>

The goal of Grok is to address the needs of developers working on  
projects ranging in complexity from Ruby-on-Rails to J2EE. Much effort  
has been put into ease of deployment and to facilitate team development.

With Grok, simple projects are easy to create, but it is with  
increasing complexity and reuse the Grok framework excels.

> Grok 1.0 is not the end of Grok development. Since Grok is extensible
> many powerful new features are being made available directly in Grok
> 1.0 in a growing collection of extension packages. The Grok
> development team is working on a whole host of initiatives to improve
> Grok even further. The Grok documentation team is also busily working
> on improving Grok's extensive documentation resources.
>
> .. _Grok: http://grok.zope.org
>
> About Grok
> -----------------
>
> Grok is a modern Python-based web framework. Grok is powerful in the
> hands of an expert developer, as it excels in reuse and extensibility
> thanks to its use of a component development model. At the same time
> Grok aims to let beginners be productive immediately, so that they
> smoothly walk up the learning curve.
>
> Grok lets you store easily your Python objects in the battle-tested
> ZODB, an object database. Alternatively relational databases are
> supported with Grok, using the `megrok.rdb`_ extension.
>
> .. _`megrok.rdb`: http://pypi.python.org/pypi/megrok.rdb
>
> Grok is developed in the Zope community and is built with Zope
> technologies. In particular, Grok builds on the `Zope Toolkit`_, a
> collection of libraries that make use of a common component
> development model, the Zope Component Architecture. The Zope community
> has more than a decade of experience in developing web applications
> with Python. The Zope Toolkit is the result of this experience,
>
> .. _`Zope Toolkit`: http://docs.zope.org/zopetoolkit/
>
> Grok is WSGI compatible and can therefore be integrated with the wide
> range of WSGI-based technologies available in the Python world today.
>
> Grok technologies themselves are also available for reuse. This has
> enabled developers to use them in combination with the Silva and Plone
> CMS projects, which work with the Zope 2 application server.
> _______________________________________________
> grok-doc mailing list
> grok-doc at zope.org
> https://mail.zope.org/mailman/listinfo/grok-doc



More information about the grok-doc mailing list