A few thoughts to simplify set-up process for local dev

I'm running through the set-up instructions locally, and have a few thoughts, happy to try implementing some of these if they make sense:

• Consider adding the migrations files to source control rather than having 'makemigrations' as a command you're supposed to run? Long-term you'll want the migrations in source control once the tool is deployed.
• python3 manage.py migrate should probably be python3 manage.py migrate --run-sync-db
• Would y'all be open to using a tool like poetry or pipenv so that folks don't have to install python packages into their global python environment when developing locally? I've found that these tools also make it much easier to install minor updates to packages (e.g. security updates) easily too. I've used pipenv on many projects but it seems like the bigger python world seems to be favoring poetry these days.