Proposal: make mural structure configurable

[MoralCode]

Been playing around with the mural creation part of the admin page (honestly the UI isnt as bad as i assumed it would be based on last week's R+D meeting)

that said being required to enter a year made me realize there should be some way to configure TunnelVision so that it could be compatible with a variety of other usecases.

Essentially I think there should be a way to specify the series of fields that make up a "mural" using some base set of standard building blocks (like an image uploader, number picker, short and long text inputs, etc) each configurable with options like being able to mark them optional.

What i have in mind is somehting similar to how DecapCMS works. That said this is probably a LOT of work and i worry about this WILDLY overcomplicating the DB structure, so id settle for just abstracting it so it can be overridden easily with a new file so that any changes made to the data used in other usecases dont cause conflicts when trying to stay in sync with upstream.

[wilsonmcdade]

As it is, most fields won't appear if you leave them blank (notes, location, remarks (coming soon)). Year is required atm but I'm sure you could find a use for an integer field? It also doesn't seem to me like a huge deal to omit that from your implementation.

The fields not appearing might be aligned with your usecase.

As we discussed privately, my goal with tunnelvision is to make it a digital asset management system following some standard for art description metadata. (In the short term) the only configurable fields we'd be adding would be following that goal.