Re: Expanding on Plone User Manual with additional use cases
Dylan Jay <dylan-Q+/Sk2sTzaxWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
actually the way Drupal defines it, those would be more like howtos. "Site Recipes: This section houses various recipes for building different types of Drupal sites. A recipe is a set of instructions that show how to prepare or make something. This section should not be used for HowTo guides that demonstrate a singular functionality, but rather an overarching objective for your site(s)" So for us that would be more like a description buildout, and which combination plugins and how we integrated them. Perpahs a documentation alternative to buildoutbuilder. On 11/04/2009, at 2:37 AM, Sam Knox wrote: > I totally agree with you Dylan. The forthcoming Community section > would > benefit greatly by having user-submitted recipies. Thanks for passing > along the link to the Drupal stuff. I've actually been working on a > few > recipes for things you can do with PloneFormGen. I'll be more than > happy > to contribute those to the Community section, once it's up and > running. > > http://learnplone.org/documentation/tutorial/ploneformgen-recipies > > Sam Knox > > ------------------------------ > > Message: 2 > Date: Fri, 3 Apr 2009 09:35:18 +1100 > From: Dylan Jay <dylan-Q+/Sk2sTzaxWk0Htik3J/[email protected]> > Subject: Re: [Plone-docs] Expanding on Plone User Manual with > additional use cases > To: Plone Docs List <[email protected]> > Message-ID: <A970DCCB-693A-432D-972A-63D54AA1CCA6-Q+/Sk2sTzaxWk0Htik3J/[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > > Here's drupals site recipes. > http://drupal.org/handbook/site-recipes > Note all drupal's documentation is wiki now and I think site-recipes > and howtos really do (as Joanna sugests) have to be in hte community > section as these are the kind of thing that will get updated > regularly. And may have different ways of achieving the same result > which people should feel free to include as an alternative on the same > page. > > Dylan Jay-4 wrote: > I was talking to a guy in the drupal community the other day and > they've recently restructered their docs. One thing they use a > lot of > is "Site recipes". Howtos on how people solved particular > problems on > particular sites. Given that such uses cases as described below > could > be many and varied, perhaps its a better idea for them to go into > the > upcomming wiki documentation area rather than manuals? Perhaps the > concept of Site Recipe could fit well with us too, including > buildout > examples, permissions structure, and which 3rd party products > were used. > ********* > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Plone-docs mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/plone-docs ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com