How sushantbabu97/30-days-of-javascript works
Project type and purpose
• This is a purely static, multi-page educational website (“30 Days Of JavaScript”) with no server-side application logic.
• Its purpose is to host daily JavaScript lessons (Markdown + example HTML/JS code), plus translated editions (Spanish, Russian).
File structure
• Top-level folders:
• 01_Day_… through 30_Day_…: each holds a .md lesson, a “_starter_” subfolder with index.html + scripts + data + any images.
• index.html and readMe.md at root: landing page & site overview.
• data/, images/: shared assets (country data JSON, media assets).
• Spanish/, RU/: translated versions, mirroring the same layout.
• .gitignore suggests Git‐based deployment.
README insights
• No mention of a server or database: all content is static.
• Navigation is through relative links from day to day.
• Embedded learning assets (code samples, videos) are served locally in images/ or day folders.
a. Main components
• Developer workstation (editor, Git CLI, optional local live server).
• Version Control System (Git repository).
• CI/CD (optional build step if a static site generator is used, otherwise direct deploy).
• Static hosting service (e.g., GitHub Pages, Netlify, S3+CloudFront).
• CDN layer (caching HTML, JS, CSS, media).
• End users’ browsers.
• External services (PayPal donate button, Telegram link, social badges).
b. Relationships & interactions
1. Developer edits .md and .html / .js files → commits → pushes to Git remote.
2. (Optional) CI pipeline converts Markdown to HTML (if used), runs link checks.
3. Static host picks up the main branch, deploys files.
4. CDN caches and serves the static files.
5. Browser requests index.html or XX_Day…/index.html → CDN or origin returns HTML → browser pulls JS, CSS, data JSON, images.
6. Browser executes example code locally (no backend calls).
c. Architectural patterns & design principles
• Single‐page static hosting (multi‐page site structure).
• “Content as code”: lessons authored in Markdown and HTML, versioned in Git.
• Localization via parallel directory trees (Spanish/, RU/).
d. Key technologies
• Markdown for content (.md files).
• HTML, vanilla JavaScript (.js under each starter folder) for interactive code samples.
• Git for source control.
• Static hosting (GitHub Pages or equivalent).
• CDN (optional) to accelerate asset delivery.
• Clear labels: e.g., “Developer Workstation,” “Git Repo,” “CI/CD,” “Static Host,” “CDN,” “Browser.”
• Dev → Git push → CI → Deploy → Host → CDN → Browser request.
• Browser → Host for uncached assets.
• Green for hosting/CDN,
• Orange for runtime/browser,
• Grey for optional external services (PayPal, Telegram).