documentation

I am a member of the Web Managers group on LinkedIn. A new subgroup is self-forming for Drupal Web Managers by request of several web managers of Drupal sites, with the comment by several that they don't find answers to their questions about managing Drupal websites on drupal.org

It occurs to me that most web managers create documentation, workflows and web governance documents during the course of their work. I know I do. So, as the group develops, I can see definite possibilities for encouraging participation in documentation here on drupal.org

This June we will celebrate the first ever Drupal for Cities Month.

Drupal for Cities is a month dedicated to building knowledge and sustainable community around using Drupal for cities and municipal government websites and projects.

Get involved
Start Thinking & planning
If you are interested in participating, join the conversation now. Think about what project you might like to lead, or what you would like to get out of the month. (Let us know if you will be at Open Gov West in May.)

Announce what you will do

Hello everyone,

I've just had a debate on the issue queue for core about Fast 404s and how to route around the issue of having Drupal be the 404 handler by default. The debate was enlightening for everyone involved I think. But the consequence should be a documentation page addressing the issue and the multiples available strategies for solving it.

I have posted a few changes and additions to the Prototype Git book and would like to do more, but I am having some frustration with the disorganization of the book.

In addition to a lot of duplication within the Git Book itself, there is a lot of duplication around the rest of Drupal.org's Getting Involved Guide.

For example, there are pages within that book for:

Let's create a wiki or documentation for "How to documentation for creating Drupal 7 multisite configuration".

I can help test and write the documentation. I may need some help setting mine up, too. So this would be beneficial for everyone.

Comment être averti qu'un nouveau commentaire a été posté sur votre site ? Question subsidiaire : comment augmenter votre réactivité en répondant rapidement à ce commentaire ?

Ce video tutoriel tente d'y répondre.

http://www.webenstock.com/fr/blog/2010-12-24-drupal-video-tutoriel-recev...

A bientôt

Karim,

Hey fellow docs enthusiasts!

As some of you may have seen, there is going to be a big Docs Sprint in Vancouver in December (come join us if you're nearby!) The other part of what's going on that weekend, is that the core Docs Team members traveling here, as well as a few core devs (webchick, chx, and dmitrig01) will be gathering on Friday to discuss the Docs Team structure and initiatives in a dedicated retreat style afternoon.

We'll be discussing and brainstorming about things like:

I recently got the opportunity to work on an idea that I've had for a few weeks – some kind of automized technical documentation of Drupal sites. It resulted in a rudimentary but working module Documentation Robot, collecting some technical information about the site where it is installed and summarizing it on a page.

It currently collects information about node types (including CCK fields), installed modules/projects, and user roles. In the pipe is also support for documenting views, panels, better CCK field documentation, and a tonne of other ideas I got. I also want to make the collected information re-usable in a number of different formats (for example DITA or creation of book nodes), but that is further off in the future.

I've been grinding away at this for many days now, and I feel like I'm never going to get past this brick wall. It's also becoming a pressing matter for my client. So I'm considering hiring this out, but first I'd like to take one last swing at getting this challenge solved.

Here's what we've got:
* There are CCK nodes called "quests". These quests have a hidden textfield on them containing a 10-character code.
* Users complete these quests in the real world, and upon doing so are given a little slip of paper with the quest's secret code.

eoriordan says:

I have been thinking of the next step here and the best way to get a bit of momentum behind this again. For me the next step is to begin to create resources based on the personas. What do people think? I think in someways there is so much stuff that we could do that it can be a little overwhelming.