Production and Delivery of Content

Traditionally, scenarios are used as tools to help users understand a product or task. In our approach, scenarios are internal tools to inform information architecture and are rarely customer-facing.

What’s it like to not just allow community contributions to your documentation, but depend on them? What if literally anybody could edit the docs and see your work as you write? Mozilla doc team members share their experiences working with radically open documentation for end-users and developers.

Unleash the full potential of DITA through process re-engineering. The biggest challenges for your authors aren’t with learning a structured language or mastering new tools but with topic-based collaboration.

This presentation describes automated documentation using free, open source tools including HTML, XML, Python, CGI, Javascript, JQuery, SQL, Apache HTTP Server and Subversion.Projects covered in the session will include intranet document management system integrating Sharepoint and Subversion as well as documenting a hierarchical system with navigable diagrams and lists.

Thinking about trying mobile for your online help or doc but hesitant because of the need for new tools? App programming? Try using your help authoring tool. We’ll review mobile outputs from Robo Help and Flare, then look at the features that help create the most flexible and controlled content possible.