How mandya-engine/mmrt works
Summary / project type and purpose
• This repo is a static web site (multi-page HTML/CSS/JS) for an organization or event site (index.html, pages/*.html, assets/images, css/, js/). The README contains only a CI badge; there are deployment artifacts (Dockerfile, VERCEL_DEPLOYMENT_GUIDE.txt) and a GitHub Actions workflow. So this is a simple static frontend project with containerization/CI and intended hosting (Vercel or a container host).
Project type and purpose
• Type: Static multi-page website (frontend-only). No server-side code or DB found.
• Purpose: Presentational site for events/members/gallery/donate/contact (pages/about.html, pages/events.html, pages/gallery.html, pages/donate.html, pages/contact.html). Assets (images, PDFs, videos) delivered as static content.
File structure analysis (what each top-level piece maps to)
• index.html + pages/*.html — primary frontend entry points / routes.
• css/styles.css and styles.css — styling resources.
• js/main.js — client-side behaviour (small JS).
• assets/ — all images, PDFs, video files used by the site.
• Dockerfile — container image to serve the static site (likely via a simple static server like nginx, http-server, etc).
• .github/workflows/docker-build.yml — CI pipeline that builds (and probably tests/lints or publishes) the Docker image.
• VERCEL_DEPLOYMENT_GUIDE.txt — guides how to deploy to Vercel (indicates intended host option).
• .dockerignore, .DS_Store, Members.rtf, Events.rtf — repo maintenance / content files.
README insights
• Minimal README; only a build/test badge (GitHub Actions). So the main CI/automation is in .github/workflows. The architecture must be inferred from files — i.e., static content + CI + containerization and optional Vercel.
Elements to include (explicit checklist)
• Clear labels for each component (Repo, CI, Docker image, Hosting, CDN, Browser).
• Developer -> Repo (push)
• Repo -> CI (trigger build)
• CI -> Build artifact (Docker image or static bundle)
• Build artifact -> Registry/Hosting (push/publish)
• Hosting -> CDN -> Browser (serve)
• Browser -> Hosting (on cache miss)
• Code vs CI vs Hosting vs External services vs End-user
• index.html, pages/* => frontend entrypoints
• css/, styles.css => styles
• js/main.js => client logic
• assets/ => static assets
• Dockerfile => container packaging
• .github/workflows/docker-build.yml => CI pipeline
• VERCEL_DEPLOYMENT_GUIDE.txt => recommended hosting path
Extra recommendations (practical)
• Move large assets to object storage (S3) + CDN; show that as separate component.
• HTTPS/SSL termination at CDN.
• Automatic invalidation/purge in CDN from CI after deploy.
• Health monitoring and logs (e.g., Datadog, Sentry) for operations.
• Use an iterative approach: start with a one-page architecture, then add detail layers for build/deploy and runtime.
• Left: Developer / GitHub Repo (annotate files)
• Next: CI (GitHub Actions)
• Next: Build artifact (Docker image or static bundle) -> optional Container Registry
• Next: Hosting (Vercel or Container host running nginx)
• In front of Hosting: CDN (optional)
• Right-most: Browser (end user)
Closing / Offer