[drupal-docs] Tag handbook pages with major versions

[Kieran Lal]

Sorry to be the wet blanket on the party.

How many pages are we talking about?   How long will it take to tag  
each page?  What skill level is necessary to know what version a page  
should be tagged to?

Even tackling a very small subsection of the handbook such at http:// 
drupal.org/handbook/modules and http://drupal.org/handbook/config/ 
contribmodules is going to take a lot of expertise in confirming what  
modules these apply to.

Do we copy the 4.6 pages and make them child pages of the 4.7 pages,  
or do we just update them to 4.7?

Kieran
On Sep 9, 2005, at 12:02 AM, Bèr Kessels wrote:

> Taxonomy pages will not be usefull, indeed. Still this is teh  
> easiest way to
> get there.
> The other options are in-body text (ugly) or a big rewrite of book  
> (far too
> high aim).
>
> PLease, if we want to go trough with this, it must at least be  
> doable ;)
>
>
> Op vrijdag 09 september 2005 04:24, schreef Charlie Lowe:
>
>> Good points. What is the advantage of using taxonomy to tag the  
>> pages?
>> Is it just to make it easy--select the term--rather than editing the
>> text and including it in the body? We will be categorizing the pages,
>> but will the resultant taxonomy displays that the tags provide be  
>> useful?
>>
>> puregin wrote:
>>
>>> On 7 Sep 2005, at 7:37 PM, Charlie Lowe wrote:
>>>
>>>> Version tagging is a great idea. But before we jump into this,   
>>>> there
>>>> are a few things we ought to talk about:
>>>>
>>>
>>> This begs the question, 'how will tagging be used?'
>>>
>>>   Do we want to be able to select a Drupal version and see the   
>>> handbook
>>> corresponding to our selection?
>>>
>>>   How will book structure and taxonomy interact?
>>>
>>>   How will 'missing' content be handled?  For example, if there  
>>> is  no
>>> content for 'administering blocks' tagged for 4.6, do we display a
>>> blank page?  Give a warning and fall back to an earlier version?   
>>> How
>>> will book navigation work?
>>>
>>>   Or perhaps we just want to be able to display all tags associated
>>> with the page.
>>>
>>>   I guess all of this is to say - I'm a bit uneasy that we're   
>>> grasping
>>> at tagging to try to impose some external structure on   
>>> documentation
>>> which is in parts fundamentally lacking in cohesion  (pardon me for
>>> saying so).
>>>
>>> As far as versioning goes, I think it's a great idea.  But  
>>> versioning
>>> by tagging seems to be the wrong approach.  How would we handle
>>> branches?  What about content that is independent of version?
>>>
>>>     Djun
>>>
> Bèr
> -- 
> | Bèr Kessels | webschuur.com | website development |
> | Turnhoutsebaan 34/3 | 2140 Antwerpen | België |
> | IM: ber at jabber.org.uk | MSN: berkessels at gmx.net |
> | v.card: http://webschuur.com/sites/webschuur.com/files/ 
> berkessels.vcf
> | pub.key: http://webschuur.com/sites/webschuur.com/files/ 
> berkessels.asc
> | pers: bler.webschuur.com | prof: www.webschuur.com |
> -- 
> [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]
>