This page is for gathering user stories for the development of technical communication tools within Drupal.
At this stage, we're just gathering information which means:
- The list is incomplete! Please help by editing this page.
- Some things listed here won't be implemented in docs.drupal.org (or at at least not in the forseeable future). However, we can still scope out the whole problem space, so that the things that we address will fit into the bigger picture of using Drupal as the framework for technical communication
- Some of the stories might be fairly broad, which means that they are acting as placeholders until someone gets around to breaking it into more granular stories or it might be that the details will be defined in the specs
As a reader ...
- I want to get back to work as quickly as possible. I do not want to wade through unrelated information or to drill through a hierarchy that doesn't enhance my understanding of what I need to do.
- I want valid links to related information, including task prerequisites.
- I want a way to return to pages that I found useful
- I want to easily communicate any problems I had with the content
- I want to feel confident that the information is valid and generally accepted, not a troublesome hack.
As a writer ...
- I want the option of using a WYSIWYG interface for writing tasks.
- I want an authoring interface that hides/dims options that are not valid for the current page.
- I want to mark paragraphs for variable output (e.g. allowing the output of either Drupal 6 or Drupal 7 versions)
- I want to apply semantic markup by choosing from a list of valid options for the context
- I want to be made aware that specific pages have changed.
- I want to return to pages that I found useful
- I want a good balance between an open-system where many people can contribute, and something where those more familiar with the broader picture related to docs can manage the system.
As a module project owner ...
- I want to be able to follow changes and additions to the documentation surrounding my module
- I want to add documentation for my module without needing to acquire domain expertise in technical communication or knowing how things are structured in the handbooks.
- I want to reduce or eliminate duplicate content (i.e. help text and handbook)
- I want to minimize support issues.
As a person who structures doc deliverables ...
- I want to reduce or eliminate duplicate content
- I want to reuse the same topic in various contexts
- I want to restructure huge quantities of content with ease
- I want to place several nodes on one page.