How harrsh-it/planora works
Project type and purpose
• This is a full-stack Django web application (“PartyHub”) for party and event planning.
• It provides user-facing pages (home, booking flow, dashboard), an admin panel, and manages models like PartyType, Service, EventPlan, Booking, Testimonial, and ContactMessage.
• It uses Tailwind CSS for styling and SQLite (development) as its database.
File structure
Top-level directories and files:
• config/ – Django settings, URL routing, WSGI entrypoint
• parties/ – core Django app with models.py, views.py, forms.py, admin.py, urls.py, migrations
• templates/ – Jinja-style HTML templates (base + parties/)
• static/ – compiled CSS/JS, images
• media/ – user-uploaded content (party type images, service images, testimonials)
• manage.py – Django CLI entrypoint
• requirements.txt & package.json – Python & Node/Tailwind dependencies
• db.sqlite3 – development database
Architectural patterns/pointers:
• MVC-style (Django’s MTV – Models, Templates, Views)
• Single monolithic service
• Admin interface auto-generated by Django
• Media and static file separation
README for additional insights
• Confirms Django stack, Tailwind CSS, SQLite (dev) / PostgreSQL (prod), Gunicorn (suggested), collectstatic for production, DEBUG toggle, ALLOWED_HOSTS, SECRET_KEY, etc.
• Describes auth flow (session-based), features (booking, dashboard), and deployment steps.