DOCS - List core audiences/user types about vf-core

[khawkins98]

Ties in with #114 (governance).

[khawkins98]

We now have thoughts on audience for vf-core; from: #321 (comment)

• Lower-level developers
  • need to: build a design system for orgs that work with lifescience info
  • interface: docs, code, command line utils
• Maintainers of design systems
  • need to: add a vf-core pattern to an existing vf-core compatible system
  • primary interface: npm, online docs
• Those curious/learning/evaluating the VF
  • need to: understand what vf-core is
  • primary interface: the static site, github readme, examples of orgs using the VF

What's not above: people building a site using generic VF-core CSS+JS ... I don't think we want that, instead — if there is demand — we might have a vf-boilerplate, but that's a TBD.

We still need to fully consider the EMBL use case, but that's after beta.1

[khawkins98]

I think we've half addressed this -- the other part is an expansion on "build a design system for orgs that work with lifescience info" and the needs there.

That is, we've listed the audiences for vf-core, but not the use cases.

I've previously discussed that use case in https://blogs.embl.org/communications/2018/09/12/faster-scientific-websites-through-reusability/

So distilling some points:

• Reusable, structured CSS, JS
• A pattern library
• Sane defaults for new websites
• Make a "look and feel" more consistent
• Provide versioned upgrades
• Run with and alongside other major tools (Foundation, Bootstrap and from the JS side Angular, React)
• Easily add your own patterns, tweak existing patterns
• Use it without a fixed look (doesn't have to look like EMBL)

Need to stash those in the docs somewhere, too,