Drupal page snippets categorization

responsible authors should tag with the taxonomy term form the relevant version, though many should be edited and tagged. Many authors at least put version info in the comments. Seems like a starting point is to check these all for version tagging, and then reorganize them to 3 child pages for Drupal 4.5/4.6, 4.7, and 5.0.

ok- I started this reorganization. Everyone should feel free to pitch in (Drupal.org is running really slow today, I think).

Hi guys,

I like the idea of snippet categorisation..but i think it's a bad idea to house snippets in the handbook.

http://drupal.org/node/87611#comment-160351

Dub

I don't have any strong feeling about where these should be located- however there needs to be a low barrier for people posting them, and they need to be easy to find. Also, I think there is potentially some benefit to providing an opportunity for people to make their first handbook post in the hopes that they will make more and more substantial ones later.

What would you suggest as an alternative to the handbook?

+1 for some sort of reorganization. Having mystery tags that are not visible until you're actually looking at the page is very awkward. A while ago I proposed exploring some sort of methodology for clarifying our handbooks architecture, but it got no response. Still, I feel that until we figure a way to have handbook navigation by release number (I don't believe it would be practical to actually duplicate the pages themselves, but the nav blocks could be restricted to taxonomy term, no?), we're going to me mired in big mosh piles of vaguely related content.

+1 for the CCK idea. This could add some structure to the area, with fields for Title, Author, description, code, additional remarks.

+1 for splitting the snippets out to their own book, too, if it would help. As long as they're findable, to me it doesn't matter where they're stowed.

Laura

-1 for CCK on drupal.org . The problem is that every module that gets on drupal needs a very strict security review and I can't see the people doing this unless there is an overwhelming benefit which justfifies this big work.

Dub, could you please move your comment to this issue and delete the comment from the handbook? As to snippets in the handbook you are the one that convinced me it was a good idea earlier this year. It has been a huge success with lots of peopl eadding and mining for ideas and solutions that they can tailer to their needs.

I'll look some more this weekend.

I did my best to reorganize the page snippets by Drupal version. Some I left at the top level that seem version independent or are general (e.g. "how to use a snippet"). I tried to categorize them with appropriate taxonomy terms and add the "notice" at the top to most.

Maybe adding the page for Drupal 5.x was hasty...

An outstanding issue now seems to be removing the comments on the top page or making them their own snippets: http://drupal.org/node/23220

I had been going to suggest a separate book for Snippets, but then when I looked at the top level of the Customization and Theming handbook, I concluded that the snippets look fine there. Instead, consider that particular book to comprise two parts: Part I is the User Guide, while Part II is the Reference Library. (Of course, there may be better names.)

Getting the first page of the handbook to show an outline with these headers is no problem. Getting the top level handbooks page (i.e. drupal.org/handbooks) to show the division would take more work, but might not be too hard.

The reality is that the top level navigation approach of drupal.org constrains the organization somewhat. I wouldn't want to see another tab added to the top menu; 7 is about the maximum reasonable. But if we could merge some of the existing tabs (support, forums, and community being an obvious overlap), then there would be space for a "Library" tab.

Gary

old issue