[documentation] Navigability on Drupal documentation
Luiz
lz_listas at yahoo.com.br
Sun Jun 25 17:51:44 UTC 2006
Dear Charlie!
Thank for your reply!
> On the other hand, one advantage of the book module over a wiki is that
> a page creator must choose where to put new documentation within an
> existing structure and can still link to other pages as well.
I agree with you, it's necessary to give adequate tool to a maintainer
to facilite your job. However, a documentation is writed to final users,
essentialy. And users need a clean, rapid and efficent manner to found
what the users are searching. Wikis are good to this.
The comparative is "simple-minded", I know, but I am not a designer nor
developer, I am seeing the question on eyes of the final user. Maybe by
this fact I have perceived problems in design pages of documentation.
Examples of documentation pages given by me in previous post show best
navigability to final users than Drupal documentation.
Drupal is great, I have installed an intranet in your enterprise using
it without I had necessity to learn PHP or other language, but in
process of learning of Drupal, its documentation was my great problem.
While I was learning Drupal, I was searching tools to building a web
application as well. In the process to evaluate what the best system and
language to our needs, "my eyes shine" when I did found clean and simple
documentation. That examples can have faults, but I found out all
information I needed on efficient manner.
To resolve "how help a contribute" to insert a page without a structure
like parent/child pages, I think one or more persons would be
responsible by this function, and Drupal have already these persons.
Best wishes
Luiz
_______________________________________________________
Yahoo! doce lar. Faça do Yahoo! sua homepage.
http://br.yahoo.com/homepageset.html
More information about the documentation
mailing list