Harrison Liddiard
Harrison Liddiard
Each would have its own URL, probably taken from Sheet ID. Default sheet has ID 0.
Ideally we could restrict bot admins to perform actions relating to a specific pool only. This would require setting up a custom permission using Django's [permissions framework](https://docs.djangoproject.com/en/3.0/topics/auth/customizing/#custom-permissions), and it would...
...with separate pages for more detailed deployment/setup instructions, and a guide for admins. Would make it easier to onboard people.
The admin screenshots and the screenshots of how people are DM'd their match's intro are out of date.
Right now sorl-thumbnail uses Memcached and django-cacheops uses Redis. sorl-thumbnail appears to support Redis as a backend so it should probably be using that.
I.e. we're working on an update to a story that's not ready yet. We need a way to save ("commit") changes without updating the publics' view. This can either be...
`has_photo_request`, `has_graphic_request`, `has_illustration_request`. Will require db queries.
Create a web GUI for initial setup. Things to do: ## Required (for the CMS to function properly) - create an authors.Organization object to be this_organization (the primary organization which...
May require low-level (model-level) access to django-reversion because we want the ability to update a Version and set its description to "autosave".
Using django-hstore (https://github.com/djangonauts/django-hstore). Also look into django-rest-framework-hstore (https://github.com/djangonauts/django-rest-framework-hstore). If it's maintained reasonably well this will also give us serialization for free.