[drupal-docs] Moving Nodes vs. Creating New Nodes

[puregin]

Hi Bryan,

     I've been thinking about this, and it seems to me that the
thing to do is to make a copy of each node which we want
to move, and then move the original.

     The old handbook would eventually become a point-in-time
snapshot.  This way we would have a handbook which
tracks the changes which Drupal will evolve through,
while having historical context (for example, we could
drop the 'migrating from version 3.0' sections in the
new version)

    I've written a little extension to node.module to support
this - in fact I'm hoping that this will provide a programmatic
interface which will let us do the copy via a script.

    Regards, Djun



On 5 May 2005, at 9:20 PM, bryan kennedy wrote:

> Hey Folks,
>
> I am going to have some free time this weekend to work on some of the
> new documentation and wanted to clear up an issue raised when I
> created the new books we have been talking about.  Dries has
> requested that we move current nodes into the new structure (http://
> drupal.org/handbook/v2) versus creating new nodes.  However, I am a
> little confused how we can do this without breaking the current
> handbook.
>
> As an example, how can we have the new books and re-write the section
> on "blocks", let's just say, and put it underneath the new
> "configuration and customization" handbook without removing it from
> it's current place.
>
> I guess we just want to balance several different things
>      -being able to develop an entirely new handbook on drupal.org
>      -not breaking old links
>
> Any suggestions?
>
> bryan
> -- 
> [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]
>