How khairulhasanrakib/fall-fest works
Project type and purpose
• From the file tree and the lone README title “Fall-Fest,” we see a Python-based web application (Bill-Ads) that uses Flask (app.py, config.py, models.py, forms.py, templates/, static/) alongside a small static site (normal/).
• The purpose is to serve dynamic ad-posting pages (login, register, verify) backed by an SQLite database (instance/users.db), plus a set of static landing pages in “normal.”
File structure
• Top-level directories:
• .github/workflows – CI pipeline using a Jekyll-Docker action (likely for docs or deployment).
• Bill-Ads – the Flask app:
– config.py, app.py – application setup and entry point
– models.py – ORM definitions
– forms.py – WTForms definitions
– templates/ – Jinja2 views for login, register, verify
– static/ – CSS, images, JS assets
– instance/ – environment-specific data (SQLite DB, .env)
• normal – purely static HTML/CSS site
README
• The README only gives the project title. No further architectural hints, so we rely on the file layout and Flask conventions.
Detailed capture of essential components
• Routes (app.py)
• Config loader (config.py + .env)
• Models (models.py)
• Forms (forms.py)
• Template renderer (templates/)
• Static assets served directly from “static/.”
• How GitHub Actions file (jekyll-docker.yml) triggers on push, builds docs/site, and pushes to a hosting service (if used).
1. User Layer (Browser)
2. Presentation Layer
– Static Pages (normal/)
– Dynamic Pages (Flask + Jinja2)
3. Business Logic Layer (Forms, Models, Routes)
4. Data Layer (SQLite)
5. DevOps/CI Layer (GitHub → Jekyll Docker → Deployment)