Deadlines for submissions to DC Copenhagen are approaching...
In addition to BoFs, I wondered if other people might have ideas for submitting sessions at DrupalCon Copenhagen to get people interested in Documentation, or make contributions to documentation, in addition to the sprint model?
I proposed a session which will first talk about how to communicate ideas visually, then we'll look at some tough Drupal concepts new users struggle with, and we'll actually make stuff. That 'stuff' can be contributed as documentation or used by others to help teach/evangelize Drupal.Read more
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
I tried searching, but I couldn't find the answer. Forgive me if I'm posting in the wrong place...
I see that I can edit handbook pages. I'm wondering why I can't edit module pages. Many times I've found a module on drupal.org and the module's page is less than stellar. It would be great if I could edit them to help make them easier for others to understand. Since there is revisioning, I don't see the harm (though perhaps an approval workflow moderated by the module's maintainer might be better). Who IS allowed to edit a module's main page?
Per a conversation at the documentation BOF about how we are approaching managing documentation at CSU Monterey Bay, here's a screencast and additional information about our approach. Sorry it's been a week, but after the figurative "Drupal Fever" of last week I had a literal fever that laid me up for a while.Read more
This page is for gathering user stories for the development of technical communication tools within Drupal.Read more
Last updated by vegantriathlete on Mon, 2010-04-05 21:51
This wiki page is an outgrowth of this discussion. Its purpose is to give us a place to collaborate on the creation of a proposal for Google Summer of Code 2010. Please leave all new feedback here.
We're aiming to put together a proposal that looks something like this. This means we need
Why this project is neededRead more
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:Read more
In the not too distant future - perhaps soon after D7 work is finished - the Drupal handbooks will move to their own site within Drupal.org and hopefully the doc folks will then have much more control over their tools and templates. While it's very exciting to think that we'll finally be able to address some of our challenges - just adding Views would be amazing - I've been thinking that there's an opportunity here to do something that is WAY more awesome. Something that could return huge dividends to the Drupal docs.Read more