Comprehensive "Sectioning" of Tapestry
Continuing the work done as proof of concept in Story #2503, a comprensive sectioning off of Tapestry will force us to assess what parts of Tapestry are out of use and how the pieces fit together conceptually. The ideal will be a small set of "sections", where each one is optional.
The methodology is:
- Identify "modules" and assign config.yml keys
- Reference configuration when rendering partials and cells
- Reference configuration when authorizing in controllers
At each point we risk encountering questions of architecture because it will be evident that some reorganization of the code being done at the same time as adding these "sections" would make sense. Therefore this is a non-trivial but important story overall.