How frontman-git/dev-event works
Project Type and Purpose
• This is a JAMstack-style, markdown-driven events listing website (“Dev-Event”) that aggregates developer events by month/year.
• All content lives as Markdown files (under end_event/, replay_event/, review/), and images/assets live under static/.
• The site is built and deployed as a static site (likely using a Static Site Generator such as Next.js or similar) and hosted on a CDN (Vercel).
File Structure Analysis
• Top-level:
• .gitignore, .all-contributorsrc, README.md – project metadata and contributor configuration.
• end_event/ – past event data, one Markdown file per month.
• replay_event/ & review/ – special pages for replays and reviews.
• static/ – banners, images, PPTX files used in content.
• No “src/” or “frontend/” directories because the generator is concealed; it’s purely content + config.
• Deployment probably orchestrated via Vercel’s Git integration (build hooks).
README Insights
• Shows badges linking to web app (https://dev-event.vercel.app/events) and mobile apps (Android/iOS) – the mobile apps are separate clients that consume the same underlying content or an API.
• Mentions Vercel, social links, sponsor banners: all static content.
Main Components
a. Content Repository (GitHub)
• Stores markdown (event data), static assets (/static), README, config.
b. CI/CD / Build Pipeline (Vercel)
• On push to main, triggers SSG build.
• Reads Markdown + assets, generates HTML/CSS/JS.
• Outputs published static files.
c. CDN / Static Hosting
• Serves static assets (HTML, images, CSS, JS) globally.
d. Web Client (Browser)
• User visits dev-event.vercel.app → static pages are delivered via CDN.
e. Mobile Clients (Android / iOS Apps)
• Could pull from the same static JSON or API endpoints hosted as serverless functions (if any), or directly scrape/consume a JSON data feed.
f. External Services
• GitHub for version control, Vercel for builds and hosting, any analytics or badge services.
Relationships & Data Flows
1. Developer pushes Markdown/asset change → GitHub repo.
2. Vercel webhook fires → CI/CD build → SSG reads content → outputs static files.
3. Generated static site is deployed to CDN.
4. Browser or Mobile App requests content → CDN returns static HTML/JSON/assets.
Architectural Patterns & Principles
• JAMstack (pre-build, serve via CDN)
• Content-as-Code (Markdown drives UI)
• CDN distribution for low latency and high availability
• CI/CD (push-to-deploy) via Vercel