Re: Proposal to manage documentation similar to (or along with) core software.
Alexander Limi <limi-z4DKO/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Apr 14, 2010 at 2:29 PM, Dylan Jay <dylan-Q+/Sk2sTzaxWk0Htik3J/[email protected]> wrote: > So whose job is it to prod those finishing the changes to the kb ui? > That's on me, and I want to finish it this weekend when we work on the Plone 4 feature documentation/overview. I'm going to be prioritizing the typical top level I-just-discovered-Plone cases in preparation for the Plone 4 release, which essentially means: - Plone 4 overview and feature list - Better front page that sells Plone 4 in particular, and Plone in general (but that last part will take a bit longer and we'll focus on Plone 4 first) - Better docs front page, and optimize flow to make it easy to: - Get started - Contribute back to the KB - Better Support page with simpler choices (essentially: mailinglist/forum | chatroom | commercial support | training) Am I missing anything that you think newcomers would be confused by? I like the idea of choosing a "documentation lead" on a per-major-release basis similar to the Framework Team process, with the option to switch along the way, e.g. at 4.3 release. -- Alexander Limi · http://limi.net ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Plone-docs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plone-docs