Discussion

For managed_file form API the Properties: #prefix and #suffix does not work.

For those of you who will be attending the Pacific Northwest Drupal Summit, who would have an interest in participating in a Docs BoF/sprint? I'm new to the Docs team, but I wouldn't mind organizing this (whenever the summit site gets BoFs up and running!). I also wouldn't mind helping someone out if they've got more experience in organizing a BoF of this type.

Thoughts?

The other day at the docs office hours, it occured to me that there really is no good way of knowing how documentation you put in the docs wiki is received. I didn't think much more about it then, but the thought has grown and I now think it's a serious problem.

(When I say "feedback" I don't necessarily mean written statements, but also things like usage statistics.)

Feedback serves two really important purposes:

1. It's a motivator. When you see that things you created (or participated in creating) are being used, it's encouraging.

This idea has been batted about recently a bit in IRC and in-person discussions, but I thought I'd post it here:

Should we create a "Drupal Documentation Merit Badge"?

The Drupal Association has just announced Community Cultivation Grants for 2012, and I'd like to get the Documentation Team ready to apply for one at the end of the summer. If you're a Drupal site builder or a module developer, you can help!! Here's the plan:

I'm thinking of changing the time for the weekly Docs Office Hours.

Motivations and considerations:
- It seems like a lot of our office hours participants lately are in Europe, and 1pm West Coast US time is pretty late for them. (Probably not for Asian participants either, and there have been a smattering of folks especially from India who have been interested.)
- It doesn't work well for some North American folks either, just by chance (like they happen to have a meeting at 1pm Tuesdays every week).

Hello wonderful members of the Drupal Documentation Team!

Remember last fall, when we went through an amazing process of discussion and refinement for the Community Docs redesign? Putting aside what happened immediately afterwards (how long it took to get it actually deployed), do you remember how great it was when it was deployed finally? If not, take a look at a Community Documentation page, such as:
http://drupal.org/documentation/modules/dashboard

The Documentation Team has traditionally hosted a documentation sprint at all of the North American DrupalCons, and this past year, also at DrupalCon London (I'm not sure if there were sprints at earlier European DrupalCons or not). [If you're not familiar with the term "sprint", the DrupalCons usually have a day, either just before or just after the main DrupalCon event, where people get together and work in a big room, and we call that a "sprint".]

One thing I find conspicuously missing from drupal.org is API documentation for contributed projects. We've put a lot of effort into coding and documentation standards, and this is paying off in improving Drupal core. But we are not seeing any benefit of this in the contrib space. Contrib modules really have no incentive to provide extensive Doxygen documentation because no-one ever sees it.

I am relatively new to drupal, and i've been evaluating some Module-types like lightbox- or imagecropping- Modules.

There are quite some comparison pages, and even a list of them.
Very usefull.
But i think as static text, they will always be outdated.

So, did someone ever think about dynamic comparison tables for modules?
I'd imagine a view that can pull compatibility, installs, activity etc. directly from the projects, so they would never outdate...

Maybe that's harder than i think?