Determine versioning strategy for EP2

[eaton]

The second edition of EP has been announced, and it sounds like there will be nontrivial changes to the list of skills and the way points are totaled after resleeving. It's almost certain that this will effect Eldrich Host, so figuring out the strategy for conversion/migration/etc would make sense.

I'm leaning towards:

• Turning eldrich.host as it currently stands into 1ed.eldrich.host, and locking down account creation
• Upgrading eldrich.host's codebase to work with 2ed rules
• Migrating 1ed data to the 2ed codebase

[eaton]

After kicking ideas around, I think this is definitely the best way to go. A lot of the code for individual components (field types, helper plugins, etc) will be kept with updates for EP2 rule changes. Logic that currently resides in the theming layer (or scattered haphazardly between modules) will be consolidated.

And — this is the biggie — a new module will be added to handle the detailed book content. I'm looking towards a Chapter/Section/Topic approach, with hierarchy handling stolen shamelessly from Book module. Two tags will be made available in Views — Table and Topic — that allow a given view to be defined as something that can be inserted into a book in different forms. Ephemera/Flavor Text, Example, and Media Items are other likely content types. (Media would be used for art, vector maps, and so on.)

Bootstrap will probably still be in use, but the new theme will make use of Drupal 8.4's layout plugins to handle both edit forms and node forms — hopefully that will also simplify the theme dramatically since it won't be carrying the weight of 100% of the layout in node templates. We'll see.