Documentation team

I wanted to let everyone know that there will be two sprints immediately after Drupalcon Portland: a doc team sprint focused on the Drupal.org content, followed the next day by a sprint focused on evolving Drupal as a technical communication CMS.

Doc Team Sprint - Friday, May 24

There's a conference coming up in Cincinnati Ohio USA that might be of interest for Drupal Docs folks, in June:
http://openhelpconference.com/

I probably won't be able to attend (just got back from "WriteTheDocs" in Portland), but it sounds interesting.

There's a conference coming up in Portland called "Write The Docs". I don't know much about it (Lee tweeted it on the @drupaldocs Twitter feed so I thought I'd post here too)...

They have a web site:
http://conf.writethedocs.org/
and Twitter:
https://twitter.com/writethedocs

I'm considering going, depending on the cost, logistics, etc., since Portland is not too far away from where I live. How about anyone else?

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

This is an announcement I received today by email... I met some of last year's attendees at this event, and they all said it was great!

The Documentation Group also applied last year to do a book, and we weren't selected. I'm personally not interested in putting together a proposal for this year (especially since I'm not the Docs Team Leader any more), but if there's a group that wants to make a proposal, you might discuss that here to coordinate. You'd need to make sure to have several people who are free to attend on those dates.

Anyway, here's the announcement:

A little over 18 months ago, Ariane K. and I started our tenure as co-leaders of the Drupal Documentation Team. We spent a lot of time working on organization, design, processes, and tools to make it easier for Drupalists to contribute to and use Drupal documentation, and I’m very proud of the many improvements we were able to make (of course, with the help of lots of other contributors!) during that time.

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.