Revise top-level documentation structure

[infotexture]

As discussed in March and June docs calls, the artificial book-based distinction between User Guide & Developer Reference in the documentation should be replaced with more task-oriented groupings.

These changes are intended to improve the navigational structure and make frequently accessed topics more discoverable, rather than hiding them under the current “book” titles.

Initial brainstorming suggests top-level items such as:

• Installing
• Building/Publishing
• Customizing/Extending/Plugins
• Troubleshooting

(Since this change would affect the URL structure of the online docs, it would need to coincide with a major release, since the URLs of topics in released documentation should not be changed.)

The process will begin with a content audit, in which the docs team reviews the current topic structure and proposes new locations in the hierarchy for each topic and suggests index terms for #53.

[infotexture]

August 26 IA Brainstorming Results

Here's the proposed outline from @shaneataylor's recent whiteboarding session:

• about
  • set expectations, including cmd line
  • dita spec support
• release notes
• installing
  • migrating from previous versions
• adding plugins
  • about; source of plugins
  • installing
  • uninstalling
• building output
  • properties or params
  • dita or ant
  • recommend using log files
  • ref verifying section
• customizing HTML
• customizing PDF
• customizing other output types
• customizing generated text
  • i18n
  • best practice: text in one plugin and others require it (for what good requiring does)
• verifying output
  • viewing output
  • viewing logs, log files
• troubleshooting
  • subtopics for, e.g., HTML included here and in associated sections for building, customizing
• reference
• resources

[infotexture]

Proposed outline implemented by @shaneataylor in #162. See PR thread for feedback & discussion.