[drupal-docs] Next steps

[Charlie Lowe]

bryan kennedy wrote:
> 
> Actually that is why I wanted to do it on drupal.org so that nothing 
> would suffer from link rot.  In our new handbook all links to handbook 
> content would be internal to the new handbook.  It wouldn't link to the 
> old handbook pages ever.  Once the new book was ready for prime-time it 
> would just be linked up as the main handbook and the old frozen one 
> would be deleted.

I was thinking of links from the Drupal forums to specific pages and 
links from external sites into the handbook. Doesn't seem to be anyway 
to avoid this other than to edit existing nodes.

> 
> 
> I actually think this will create link rot.  If we create everything in 
> a wiki then we don't have the structure imposed by the book module.  
> Then we have to re-find all the links as we move pages over since the 
> wiki will not create node's defined in the book structure.  If the 
> final destination is a book on drupal.org then let's author in a book 
> on drupal.org.  If this isn't possible then let's at least author in a 
> drupal site running the book.module with a protected chunk of node 
> numbers, so that we can move it over to drupal.org once it is ready 
> without having to re-write links.

Yeah. Seems like either way we loose here. Best solution seems like it 
might be to create an alternative Drupal handbook, use path alias to 
name all the pages, then for all internal book links, use the aliases. 
But then copying over the pages into the previous nodes would be a 
problem because path aliases have to be unique. This suggests that the 
new handbook has to be built off of drupal.org, perhaps on a subdomain 
as has been suggested before. I'm starting to think this is the best way 
to go. Besides, wikis are nice, but eating our own dog food is better.