Proposed Changes for Version 3.5.0 Documentation

We would like to support different users with clear paths to follow in finding what they need in the CDAP documentation.

Currently, we provide limited direction for users as to how to engage and work with the docs. Aside from a particular order or certain examples, we don't suggest a particular approach.

To assist, we identify these different users:

1. New CDAP Developer
   
2. Architect trying to understand CDAP at a high level
3. Ops guys looking to install CDAP
4. Passer-by looking to find out what is this CDAP
5. ETL developer looking to build a data pipeline on Hydrator
6. Developer with a bit of experience in CDAP trying to understand "how is...?"

We propose replacing these user stories with these users and interests:

1. User (a Data Scientist)
   1. New to CDAP
   2. Developing a Hydrator Pipeline
      
2. Developer (of Java or other supported languages)
   1. New to CDAP
   2. Developing a first Java Application
   3. Developing a first Plugin
   4. Looking for an answer to a particular question
3. Architect (or a CxO, a corporate officer)
   1. Reviewing CDAP abstractions and components
4. Administrator/Operator (of networks or clusters)
   1. Installing CDAP
   2. Operating CDAP

It's possible that certain users may fall into more than one category. For example, a User may want to install CDAP themselves, in a Standalone setting, as part of a review process, in order to evaluate its appropriateness for their situation before passing it to an Administrator/Operator for adding it to a cluster.

We can identify paths either by user or by theme, where the themes would be the interests listed above.

Wikipedia identifies three broad approaches to the organization of documentation:

Of these different approaches, we employ all of these, and can suggest resources as the user advances in proficiency.

Introduction Pages

Each manual and the Documentation itself has an "Introduction" page.

Currently: These pages are a list of links with descriptions and important terms or phrases marked in bold:

Proposal: Have a tabbed panel that shows for different users appropriate content (note: the content would not be a literal, that is a limitation of the current custom Sphinx extension):

These tabbed panels could be used at the start of each Introduction. As with our existing tabbed-parsed-literals, they would be synchronized, so that all would show the same tab, but with different content, in each area.