Review existing documentation

[zerocrates]

Current structure

• Home page (contains nothing)
• Contributing (notes for users trying to make PRs, basically)
• For Omeka Classic Developers (changes from classic to S, corresponding terminology... incomplete)
• Register an addon (linked from the addons repo area)
• Key Concepts
  • Access control lists
  • REST API
  • Config
  • Controllers (empty)
  • Debugging
  • Doctrine and entities
  • Forms
  • Home (not sure what this is... probably a blank index page
  • Internationalization
  • Javascript events
  • Modules
  • Events (PHP-side)
  • Representations
  • Routes and Navigation
  • Services and Factories
  • View Helpers (also includes list of available helpers)
  • View Model
  • Working with SASS and CSS
• Modules
  • Internationalization (somewhat duplicates Key Concepts -> Internationalization)
  • Introduction (partially identical to Key Concepts -> Modules)
• Reference (basically lists of things)
  • Configuration settings
  • Core documentation (the generated PHP api docs)
  • Events (PHP-side)
  • Javascript Events
  • JSON LD (not sure what this is really supposed to be, it seems to show a sample response to one GET to the API)
• Themes
  • Introduction
  • Modifying themes
  • Style guide

[zerocrates]

In terms of topics we don't cover that we should: major things I think would include:

These are in the mode of tutorial or "concepts"

• blocks/layouts for sites
• media/file renderers/ingesters
• data types

Basically the big intentional areas of modularity specific to S that aren't currently covered.

Obviously we should merge the Modules and Internationalization stuff... I can't immediately decide if we should be targeting that toward the Modules section or the Concepts section (i.e., which do we keep), but maybe that's a larger structural decision that can wait for some more filled-out content.

The issue with Modules as a section is that most if not all of the documentation will be relevant for module developers. The only major Theme thing we have under Concepts is "Representations" and that's obviously applicable to both.

[zerocrates]

On structure my thoughts are more preliminary... clearly there's issues with ordering and grouping

We probably want to prioritize high in the list "getting started" type information for Modules and Themes, rather than them floating at the bottom as they now do.