I like the idea of Job Roles and Checklists:<br><br>We could have a Grok Checklist based on your role<br><br>Designer Checklist<br>-----------------------------<br>This is what you need to know to be an effective designer with Grok:<br>
* CSS (learn CSS here.....)<br>* HTML (learn HTML here ....)<br>* ZPT .....<br><br>Developer Checklist<br>----------------------------------<br>This is what you need to know to be an effective designer with Grok (we've tried to put them into a sensible "learn-this-first" order):<br>
* CSS<br>* HTML<br>* ZPT<br>* Viewlets (learn viewlets first)<br>* ........<br>* Subversion<br><br>Deployment/System Integrator Checklist<br>-------------------------------------------------------------<br>* Python Eggs<br>
* Buildout<br>* Subversion<br>* REST<br><br><div class="gmail_quote">On Fri, May 30, 2008 at 9:58 AM, Kamon Ayeva <<a href="mailto:kamon.ayeva@gmail.com">kamon.ayeva@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Do everyone agree with simplifying the page along the lines of:<br><br>
** Documentation for Grok **<br>
<br>
o The Grok Tutorial<br>
<br>
o The Grok Developer's Notes<br> <br>
o All tutorials and howtos <br><div class="Ih2E3d">
<br>
* Browse Documentation By Topic *<br>
<br>
[The topics here...]<br>
<br></div>...<br><br>+1 for me.<br><br>I can work on it today so we can see the result.<br><br>Cheers,<br><font color="#888888">Kamon<br><br><br><br><br>
</font><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>
<br></blockquote></div><br>