How juna1013/3m2-shikousai-marugame works
Project Type and Purpose
• This is a static, single-page promotional website built for the “3M2 丸亀クレープ” class circle at a school festival.
• There is no backend service or database—just HTML, CSS (Tailwind), JavaScript (jQuery), and static hosting on Vercel.
File Structure Analysis
• Top-level files only:
• index.html – the single page entry point
• index.js – custom jQuery scripts
• README.md – project overview and stack
• LICENSE – open-source licensing
• No server code, no configuration files for builds or package managers, indicating a pure static site.
README Insights
• Tech stack: HTML, TailwindCSS, jQuery, Vercel
• Hosted on Vercel, so CI/CD and static asset serving are offloaded to that platform.
Main Components
a. User’s Browser (Client)
• Renders HTML/CSS, executes index.js (jQuery)
b. Vercel Hosting Platform
• Acts as a Git-integrated CI/CD provider and global CDN
c. GitHub Repository
• Source of truth; pushes trigger Vercel builds
d. Static Assets
• index.html, index.js, TailwindCSS (either via CDN link or generated CSS file)
e. External Dependencies
• jQuery from CDN (if used that way)
• Any analytics or third-party widgets (if added)
Relationships & Data Flow
• Developer pushes to GitHub → Vercel build pipeline → deploy to global CDN
• End user → HTTP(S) request to Vercel CDN → serves index.html, CSS, JS
• Browser loads index.html → pulls in TailwindCSS and jQuery → runs index.js logic
Architectural Patterns & Principles
• “Static-First” architecture: no server-side rendering or API layer
• CDN distribution for low latency and high availability
• Infrastructure as code via Vercel configuration (implicit)