[drupal-docs] Tag handbook pages with major versions

[Steven Peck]

Some infomration in the handbook could benefit from being versioned.
Other infomration does not necessarily need to be.  When I started
playing with HEAD, I discovered that I will be updating some of my best
practices very soon.

The quesiton, is how to identify and separate out what applies.  This
has always been a challenge and will probably continue to be so.

-sp 

> -----Original Message-----
> From: drupal-docs-bounces at drupal.org 
> [mailto:drupal-docs-bounces at drupal.org] On Behalf Of Benjamin Slade
> Sent: Thursday, September 08, 2005 8:52 PM
> To: drupal-docs at drupal.org
> Subject: Re: [drupal-docs] Tag handbook pages with major versions
> 
> Could we implement an interim solution which has a line in 
> the content 
> saying something like "Last Updated: 2005-Sep-09   For Drupal 
> Versions 
> 4.2+".  Not very elegant, but easy to explain/implement/read, 
> and can be implemented incrementally.
> 
> Maybe someday the book module could be updated to support 
> versioning and 
> release labeling of child nodes?   Ie. revisions of a node could be 
> associated with a release of the handbook.
> 
> Ben Slade
> 
> Charlie Lowe wrote:
> 
> > 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
> >>
> >>
> 
> --
> [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]
> 
>