[drupal-docs] Drupal.org setup

[Steven Peck]

Excellent idea.  
 
Perhaps a section Configuration Guides in there, on it's it's own, or in Best Practices section.  I am working on one for the way I setup my sites (which are not community oriented) and I'd like to see Bryght's 'corporate site in an hour' adapted in there as well.  I am planning on which modules I use, workflow configuration settings and a brief reason why I picked what I picked.  For instance, until I read the Bryght guide, the book module did not really occur to me as useful for my sites, now, I am considering it.
 
Now that I have all my site upgrades done I will have more time.  Look for it this weekend or check my site where I have the opening paragraph notes and not much else :).
 
I think identifying modules by name and core/contrib should be sufficient.  I would like to keep as much redundant information out of other documents as posible.  It also keeps the guides shorter and th efocus of updating module descriptions concentrated in the section of the handbook that is most appropriate..  A note to see handbook/modules for more descriptive information at the top or at the appropriate spot would serve nicely.  Part of this helps teach people to look up information. 
 
------ posible areas to cover.....
Target site use / market
-description
 
Modules
-core:
-contrib
-custom modules: notes and mention if any unreleased mods/features, etc.
 
workflow settings
-pub/promoted/moderated
 
roles
-brief desciption -types of end users.
 
Blocks
-std, brief overview on paths 
-custom, how used, why.... example or link to blocks conf page.
 
Adaptions
notes on how such a configuration might be adapted, modified or re-purposed to suit other needs/target audiences.
 

________________________________

From: drupal-docs-bounces at drupal.org on behalf of puregin
Sent: Tue 7/5/2005 9:30 AM
To: drupal-docs at drupal.org
Subject: Re: [drupal-docs] Drupal.org setup




On 5 Jul 2005, at 9:12 AM, Steven Wittens wrote:

> I've noticed that often there is confusion that a feature that is
> present on Drupal.org is not in the standard distribution. This
> happened
> recently with the codefilter for example. Similarly, often the question
> is asked "How do I make ... just like Drupal.org?" about the lesser
> known core features.
>
> So, why not make a page which documents which modules we use on
> Drupal.org and how we use them? Here's a start for such a page. I'd
> appreciate it if some of you could improve it and put it in an
> appropriate place ;). I'm not too good with "newbie friendly"
> writing...

That's a great idea.   I'd be inclined to put it under Administrator's
guide,
Drupal modules and features, but fear it might get lost in the many
subsections.  Perhaps we could rearrange things to look like this:

Administrator's guide
     ...
     Drupal modules and features
         Core modules
         Contributed modules
         Example: Drupal.org's configuration

Djun


--
[ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 7055 bytes
Desc: not available
Url : http://drupal3.drupal.org/pipermail/documentation/attachments/20050705/372d231d/attachment.bin