[drupal-docs] Task for Drupal documentation writers

[Stefan Nagtegaal]

My apoligise for not having enough time today to coockup some patches.. 
I'll promiss you guys that thais is the first thing i'll do tomorrow 
morning when i wake up.. (After brushing my teeth and some coffee)

Anisa, thanks for the work you did on this.. We can let Dries descide 
if it's good enough to go into core, if others does not have an 
opinion.


Stefan.

Op 17-apr-05 om 20:01 heeft Anisa het volgende geschreven:

>
>  Anisa wrote:
>> These pages have no proper text:
>> http://dev.bryght.com/t/wiki/EditVocabulary
>> http://dev.bryght.com/t/wiki/PreviewForm
>>
>
>
>  So, everything (except configure specific node types) has text, but 
> is it good text?  It's a little hard to tell with everything on it's 
> own page, so I will put it all together here. (I don't want to change 
> the wiki that drastically.  ^.^)
>
>  Sorry about the non-plaintext thing, it was going to be really hard 
> to read otherwise.  I have added all sorts of comments to the wiki:
> http://dev.bryght.com/t/wiki/HelpText
>
>  Right now, just looking at it, I notice a lack of consistency in the 
> starting line, some start with Edit X here, some start with You can 
> edit X here, and some are This is the page to edit X.
>
>  ****************************************
>
> user.module
> - "?q=admin/access/rules":
>
> Access Type
> Rule type
> Mask
> deny
> email address
> %
> allow
> email address
> %@example.com
>
> Explanation of above: it denies all email addresses, except it allows 
> any email address that ends with @example.com but has something before 
> it (Drupal will deny invalid email addresses anyway, so there's no 
> need to check in the access rules if there is at least one character 
> before the "@").
>   o 'add rule'
>  Choose whether the rule you are adding allows a user to sign up or 
> denies them access, then which piece of information to base the rule 
> on.
>
>   o 'check rules'
>   You can check to see if the rules you made work the way you intended 
> here.
>
> - "?q=user/1/edit"
>  Edit %username's settings here.  Among other things, you can block 
> this user, grant additional roles, or change the account password.
>
> taxonomy.module
> - "?q=admin/taxonomy":
>  The taxonomy module allows you to classify content into categories 
> and subcategories; it allows multiple lists of categories for 
> classification (controlled vocabularies) and offers the possibility of 
> creating thesauri (controlled vocabularies that indicate the 
> relationship of terms) and taxonomies (controlled vocabularies where 
> relationships are indicated hierarchically). To delete a term choose 
> "edit term". To delete a vocabulary, and all its terms, choose "edit 
> vocabulary".
>
>   o 'edit vocabulary'
>  Configure your vocabulary here. You can change the title, 
> description, help text, which node types can use this vocabulary, as 
> well as the vocabulary structure. (link to ?q=admin/help/taxonomy) 
> Read more about the configuration options.
>
>   o 'add term'
>  Add a term to the %vocabname vocabulary.  Go back to the categories 
> settings (link to admin/taxonomy).
>
>   o 'edit term'
>  Edit this term. You can change the name, description, synonyms, and 
> weight of this term in its vocabulary.
>
>   o 'preview form'.
>  This page shows you how this vocabulary will actually look on a 
> submission form.
>
>
> comment.module
> - "?q=admin/comment/list/approval"
>  This is the moderation queue for comments. You can approve or delete 
> comments posted by your users with 'post comments' permission. If you 
> want to have your users post comments without going through the 
> moderation queue, you have to enable the 'post comments without 
> approval' permission (link to permissions). ... More help (link to 
> comment help)
>
>  node.module
> - "?q=admin/node/configure/types"
>
> This page lets you set the defaults used during creation of nodes for 
> all the different node types.
> 	• 	comment: Read/write setting for comments.
> 	• 	publish: make this post live and viewable by everyone
> 	• 	promote: promote the node to the front page automatically
> 	• 	moderate: place the node in the submission queue for approval 
> before publishing
> 	• 	sticky: make this node "stick" at the top of lists (i.e. front 
> page, forum threads, etc.)
> 	• 	revision: create a new revision every time the node is edited
>
> Regular end users will not be able to change any of these options 
> unless they have "administer node" permission?.
>
> If upload.module is enabled
>
> If you want users to be able to attach files to nodes, check the 
> attachments column in the appropriate column.
>   o and every 'configure' page for a certain node/post type
>  (no text.  Please add some! )
>
>
> book.module
> - "?q=admin/node/book/$node->id"
>  You can view, edit, or delete individual pages here. You can also 
> change the position of individual pages in a book by using weights.
>
> Weight is how the ordering of lists is controlled in Drupal. The lower 
> the value (including negative) an item has, the higher it is 
> positioned. The higher the value, the lower it is positioned. 
> Confused? Think of gravity: light things float, heavy things sink.
>
> If weights are equal, the default ordering is alphabetical by node 
> title. So, if you were to leave every page in a book outline set to a 
> weight of zero (0), the pages would alphabetical from A to Z, based on 
> their title.
> forum.module
> - "?q=admin/forum/configure"
>  This is where you can configure how all your forums act and display.
>
> statistics.module
> - "?q=admin/logs/pages"
>  These are the pages with the most hits over the past 3 days.
>   
> - "?q=admin/logs/users"
>  These are the users who are on your site the most, as measured by the 
> number of hits. Change the sort by clicking on hits or user.
>
> menu.module
> - "?q=admin/menu"
>  Select an operation from the list to move, change, or delete a menu 
> item.
>
>    o choose the 'edit' operation for a certain menu-item;
>  Edit the menu link to %path. You can change the name, description, 
> parent, and weight of this menu item here.
>
>  ****************************************
>
>  Anisa.
>  Configuring her drupal site... why does it take so long... >.<
> -- 
> [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]