Move the Event Platform to a set of recipes

Problem/Motivation

Currently the Event Platform is a set of modules. While this approach has worked reasonably well for a number of camps, it does have a few limitations, because any configuration provided must be literal (for example, placing blocks using the theme name) or write a custom install hook.

Proposed resolution

Leverage the powerful and growing set of config actions available by converting the modules to a set of recipes. Work has already been completed to add into Drupal core config actions that will allow blocks to be placed into the site’s default theme, so the blocks can be placed into a custom theme. Conversion into recipes will mean, however, that the relatively few places where the project provides PHP, CSS, or Javascript code will need to become separate projects, and then pulled into the relevant recipe. The trade-off is that particularly for functional elements like the drag-and-drop interface to assign rooms and time slots, it could be made configurable (and so more broadly useful) and then configured by the recipe when needed.