documentation

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

I'd like to hire someone to write a Texmate command that could "read" the .info, .install, and .module files in a Drupal module and extract the relevant Drupal specific information from them. (input a module folder and output an HTML document) I have an outline of exactly what I would like to read from the files, and how to display the data. There are existing "documentation" tools available, but they are all "function" based, and not "module" based. I want to see "at a glance" (and present to non techies) what tables, menus, hooks, blocks, node types, API functions, ect...

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.

Hi there folks,

I'm sure many of us are excited about the potential of the Memetracker module (I definitely am!).

Memetracker currently has some Python requirements, and many Drupal folks are not accustomed to installing Python/ Linux packages in general.
As a result, many of the issues in the Memetracker issue queue are about getting the Python packages installed correctly.
To help with this, I've written a document that's purely about installing the Python prerequisites:

World Class Social media team seeks reliable team to extend our current work force. Applicants should have excellent communication and strong documentation skills. Must be able to meet once or twice per week in Oakland or San Rafael.

We are looking for several individuals to handle various portions of development.

We are looking for design consultants, documentation specialists, technical consultants, module developers, theme developers, installation techs and Quality Control personnel.