One of the important challenges facing the effort to improve Drupal as tech comm tool is getting the right user experience for authors especially when we start adding things like conditional text, single-sourced content and DITA-style mapping.Read more
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 24Read more
Hey Docs Teamsters!
Not sure if any of you have been following my posts about trying a more agile/sprint-based method for the online docs work that needs to be done - I wrote a bunch about it here: http://groups.drupal.org/node/134909 (And there's a link to my blog post about it there as well).Read more
Our current d.o documentation is maintained by angels: highly altruistic people who give without expecting to receive much. We love our angels, but this is not how it's supposed to be, documentation is just as important if not more than code.
In this BoF we'll explore how we could make documentation modular and reusable so that every single page of documentation you write for a project in the future becomes a potential source for reusable, contributable documentation on drupal.org.Read more
Hi, All --
Awhile back I suggested a DITA "mash-up" structure and workflow process that I thought might be a candidate for the Drupal docs--this was based on my prior work as a DITA consultant, my reading of the Drupal doc group discussions, and my own understanding of what I assume are typical problems putting together an open-source, structured/unstructured collection of topics.
My business partner and I have put together a model DITAmashup collection on one of our sites that is accompanied by a post explaining how we did it and what we think are its benefits:Read more