Issue #1 is closed. WeRemember has a running Django server. Not exciting on the surface. But the decisions made here will affect every line of code that follows — so they're worth documenting. What I set up A minimal but intentional Django project structure: uv as package manager — fast, modern, handles virtualenv automatically Python 3.12 pinned via .python-version Split settings — base.py , development.py , production.py living in config/settings/ django-environ for environment variables with an APP_ prefix convention apps/ directory as a placeholder for future Django apps The decisions that matter Why uv instead of pip ? One tool for everything — dependencies, virtualenv, Python version. No more pip install , python -m venv , source .venv/bin/activate . Just uv add and you're done. Why split settings from day one? It costs almost nothing now and saves a painful refactor later. manage.py defaults to development , wsgi.py defaults to production .…