documentation

Just had a bit of a lightbulb moment (and maybe this idea has come up before?) about how to eventually kill comments on handbook pages. Someone asked how we could make sure conversations about a particular page were still visible if they were happening in the issue queue instead of as comments.

I thought, and this is what seemed like a good idea:

• add a field on the issue node-add form for a referenced d.o NID (to reference the handbook page the issue is about)
• build a view block for the handbook pages that displays any issues related to the page

Ta-da?

In order to provide better, richer documentation, we have enabled commenting for OpenPublish documentation's book pages @ http://openpublishapp.com/doc/

Documentation is strictly moderated for spam and off-topic. We have to apologize for overly restrictive moderation and we may relax it in the future, but for now this is the only way to ensure that we do not end-up with long pages of disjointed discussions.

I've just recorded an introduction on how to use the awsome Rules module!
It can be seen on NodeOne's blog.

The screencast is a pilot case on doing semi-regular screencasts in English. (We've been doing them in Swedish for a while.) If you think that this is worth watching and would like to have more unprestigious screencasts, please write a comment on our blog.

Cheers!
//Johan Falk, NodeOne, Sweden

I organized some Drupal 7 documentation sprints the last few Tuesdays (http://groups.drupal.org/node/50403)... They were successful, in that we got a couple of new people going in documentation, and a few patches filed (I'll shout out to trevjs especially, for coming to all of the sprints and patiently working on some patches).

However, the sprints were not very well attended, and we still have a lot to do to get the documentation of Drupal 7 ready for its release (http://drupal.org/node/515870), so I'm wondering how we can get it done.

My questions:

Tengo el placer de anunciarles, que ya desde hace algunas semanas hemos lanzado el sitio web

http://www.ecosistema-drupal.org/

Un sitio dedicado fundamentalmente a compartir la documentación que hemos ido produciendo dentro de nuestra empresa, softwinperu. Sin embargo, recién estamos subiendo la información, conforme pasen los días irán viendo más y más contenido.

While there are many Aegir related tips and documentation available, including scripts for complete Aegir system install on LAMP stack, we often have clients using Aegir the first time on their new VPS, but with enough experience to manage and transfer Drupal sites, and they often tend to overlook some required steps, they still make simple mistakes, or feel lost in a too detailed how-to, so I think it can be useful to post also some simple check-lists to make the work easier for others and to help enjoy Aegir power and

Unfortunately the handbook got scrambled when d.o. upgraded to d6. See http://drupal.org/node/376790.

As mentioned in the issue the work is ongoing and hopefully the docs are fixed soon. mitchell and me thought about doing our on documentation site in the meantime or forever, but I think it's better to stay on d.o. - so people can contribute faster, without the need for registering or even logging into another site.. (Yes, every d.o. user can contribute to docs).

I must confess I am totally confused by workflow. I'm still working in D5 (waiting for modules to be upgrade to D6 so I can upgrade), and would like to set some simple workflows in place. Two examples:

Internationalization is at the same time needed and hard to achieve.
I may be a little late in this redesign discussion, but I think it's important to bring some light to this issue.