I think one big area where there is a crucial need for more / better documentation is around authentication. Nowadays every site needs to have a robust login system with user registration, e-mail confirmation, etc. If you're using Grok on its own, as I am, to do your project then it takes a whole lot of work just to understand how to get a basic login system going and that can be a big enough problem to make you consider alternatives...<br>
<br>megrok.login is a huge step in the right direction and I am in the process of writing a doc about how to use it to set up a grok authentication / user registration system "with batteries". I still need to work out issues I'm having with modifying the session timeout of the auth cookies though...<br>
<br>In my humble opinion, how a framework handles authentication will be a huge deal breaker when it comes to new users trying to adopt the framework.<br><br>Anyway like I said I'm working on a doc about this myself, but I figured I'd mention this since we're talking about community docs as a whole.<br>
<br>- Thibaud<br><br><div class="gmail_quote">On Fri, May 22, 2009 at 9:27 AM, Paul Wilson <span dir="ltr"><<a href="mailto:paulalexwilson@gmail.com">paulalexwilson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2009/5/22 Tim Cook <<a href="mailto:timothywayne.cook@gmail.com">timothywayne.cook@gmail.com</a>><br>
<div class="im">><br>
> I want to volunteer to help review community documentation on the Grok<br>
> site.<br>
><br>
> I need to get up to speed on some things as far as editing goes but I'm<br>
> happy to do that if the team can use some help.<br>
<br>
</div>I know that the following documentation is outdated or contains inaccuracies:<br>
* Annotations - (what is ISerialBranding? And perhaps a note about<br>
registering IAnnotations during testing)<br>
* REST support (grok.RESTProtocol is used when grok.restskin(name) is favoured)<br>
* Grok Templates (multiple issues arising from the spin-out of<br>
grokcore.component)<br>
<br>
I think an action needs to be taken to update the appropriate<br>
documentation whenever a component / interface has changed.<br>
<br>
Thanks,<br>
Paul<br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</blockquote></div><br>