Submitted by Diane (not verified) on Tue, 05/05/2009 - 10:18.
I started using Drupal a year ago, and I HATE the documentation with a passion. Personally, I think it is a bigger barrier to Drupal success than the UX issues that are being addressed.
Yes, we can use the edit tab, which is akin to arranging deck chairs. The problem is not so much in editing individual pages, it is structure, findability, logical connections, relevance.
I would love to help make it better, and I see no way to do that without a slash and burn. One of the biggest issues is just how mashed up everything is together. I get particularly defeated by D5 content - I have never used D5, and don't want to see that documentation. It could be relevant to what I am trying to do in D6, but I don't know if it is, and it usually appears it isn't. Meanwhile, it is so dominant I can't find what I really need.
I think there are models of how to do this well.
Why not create a new, logical structure - which separates documentation by version, by type, etc and create an all hands on deck effort to move the relevant existing stuff to a new structure? That is an effort I could get behind.
Good for you for speaking out.
And yes, the four books I have purchased have all been many times more helpful than the docs, sad but true.
I started using Drupal a year ago, and I HATE the documentation with a passion. Personally, I think it is a bigger barrier to Drupal success than the UX issues that are being addressed.
Yes, we can use the edit tab, which is akin to arranging deck chairs. The problem is not so much in editing individual pages, it is structure, findability, logical connections, relevance.
I would love to help make it better, and I see no way to do that without a slash and burn. One of the biggest issues is just how mashed up everything is together. I get particularly defeated by D5 content - I have never used D5, and don't want to see that documentation. It could be relevant to what I am trying to do in D6, but I don't know if it is, and it usually appears it isn't. Meanwhile, it is so dominant I can't find what I really need.
I think there are models of how to do this well.
Why not create a new, logical structure - which separates documentation by version, by type, etc and create an all hands on deck effort to move the relevant existing stuff to a new structure? That is an effort I could get behind.
Good for you for speaking out.
And yes, the four books I have purchased have all been many times more helpful than the docs, sad but true.