[documentation] Sorting the Troubleshooting FAQ

[Steven Peck]

Someone put sorted categories back?  hrmmm....

The reason it isn't is that all the categorizations generally make it
more mouse clicks, neophytes can't find stuff because they don't know
what they are looking for anyway, new content is never in the right
place and it leads to much duplication and no one maintains it.

Blank pages is an error message. :)

In any case, if you are willing to play and maintain it go ahead and
play with it.  You are now the owner of the troubleshooting faq
section.  Organize it to your hearts content. :)

Steven Peck :: www.blkmtn.org

On Dec 17, 2007 1:39 PM, Lee Hunter <lee.hunter at hum.com> wrote:
> I'm thinking the Troubleshooting FAQ should be organized by subject
> area so that when you go to the page
> (http://drupal.org/Troubleshooting-FAQ) you get a short list of about
> six subject areas rather than a very long list in random order
> (currently there are about 60 items ).
>
> Actually there's a bit of this already. There's currently a Hosting
> parent node and a Miscellaneous parent node (although the
> Miscellaneous node only contains one child).
>
> What I'd like to do is create the following child nodes of the FAQ page:
>
> - Hosting Issues [renamed from Webhosting issues for new Drupal users]
> - Site Configuration, Modules and Installation
> - Accounts, Permissions and Login
> - Blank Pages and Missing Content
> - Pages That Display Incorrectly
> - Error Messages
>
> All the existing nodes would then become children of one or another of
> these nodes with the exception of the "How to Troubleshoot" node which
> would remain a direct child of the FAQ page.
>
> I'm wondering if this is the kind of thing I can just jump in and do
> or whether it's the sort of thing that needs to be posted as an issue
> or discussed on this list? Does anyone have any other suggestions or
> plans for this page?
>
> Lee
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/
>