@PhilipSargent this does beg the question: why use a fully-featured MCV framework if you are going to intentionally subvert its features? If the explicit goal is to reinvent every wheel then why
This even implements an HTMLField object - https://django-tinymce.readthedocs.io/en/latest/usage.html#the-htmlfield-model-field-type which it suggests can be used with the `django.contrib.flatpag
https://www.tiny.cloud/docs/integrations/django/ seems to have a simple enough implementation - the JS library can be used straight from their CDN if hosting it ourselves is too much to handle easily.
Thanks @PhilipSargent, that's really useful to know.
I wonder if there is a third TinyMCE django plugin/app that we might be able to bring in to take some of that maintenance work off our hands?
@PhilipSargent That's a reasonable concern - change for change's sake is not sufficiently justified. However, arbitrarily quoting blogs and books as a justification for inaction is somewhat
The models.caves.Entrance model already implements fields for easting and northing so this data is already extant. Providing it to the users on the front-end, however...