How highpolar-softwares/bakerydemo works
Project type and purpose
• This is a full-stack demonstration website built on Django + Wagtail CMS.
• Purpose: showcase Wagtail features (streamfields, custom page models, snippets, search) via multiple Django “apps” (base, blog, breads, locations, recipes, search).
• It includes a frontend (HTML/CSS/JS templates), a backend (Django/Wagtail), and a relational database for content and user data.
File structure
• Top-level config & devops:
• Dockerfile, docker-compose.yml, Procfile, Vagrantfile, GitHub workflows → containerized & CI/CD pipelines
• .env.example, requirements/ → dependency management
• Main codebase under bakerydemo/:
• bakerydemo/settings/ → environment‐specific settings (dev, prod, base)
• bakerydemo/api.py, urls.py, wsgi.py → entry points for HTTP/WSGI
• bakerydemo/static/, bakerydemo/templates/ → static assets & HTML templates for the frontend
• bakerydemo/base, blog, breads, locations, recipes, search → domain-specific Django apps
• Management and data:
• base/management/commands → custom CLI commands (load_initial_data, reset_demo, etc.)
• base/fixtures/bakerydemo.json → initial content dump
• Migration folders in each app → schema evolution
• CI/CD configs in .github/workflows & Travis → linting, Docker builds
README for additional insights
• Confirms a demo site for Wagtail, not production-grade
• Describes key features: custom content models, mixins, snippets, admin hooks, search integration (DB search fallback), contact form email backend
• Deployment instructions for various environments (Gitpod, Docker, Vagrant, virtualenv)