How hoanguyen2805/trac_nghiem_js works
Project type and purpose
• This is *not* a full-stack app or a microservice system. It’s a *static content repository* of advanced JavaScript multiple-choice questions in Markdown, with translations maintained in parallel folders (each language has its own README_xx-YY.md). Its primary purpose is to host educational Q&A on GitHub (and mirror/link from Instagram).
File structure
• Top-level: a single README.md (the Vietnamese version).
• Underneath (mentioned in the README): language subdirectories like ar-AR/, de-DE/, zh-CN/ each containing their localized README.
• No src/, no frontend/, no backend/ code—pure content.
• No build scripts or config files in the provided tree; presumably served via GitHub’s Markdown renderer or a simple static-site generator (SSG) like Jekyll or Hugo.
README
• Shows the question list, code snippets, answers, and “other languages” links pointing to subdirectories.
• No mention of runtime components, databases, or servers—just Markdown content and translation folders.
Main components
a. Content layer
• Markdown files (one per language)
• Translations organized under language subfolders
b. Build/deployment layer
• (Optional) Static-site generator (e.g. Jekyll/Hugo/Next.js-SSG) or direct GitHub-Pages renderer
• CI/CD or GitHub Actions: on push → build → deploy
c. Hosting layer
• GitHub Pages (or Netlify/Vercel)
• CDN (GitHub’s global mirror or your own CDN)
d. Delivery layer
• End users: Browser clients reading the site
• Instagram: Author posts questions → drives traffic via links to GitHub site
• Author edits → Git commit → GitHub repo
• Push triggers SSG (if any) → static assets
• Assets deployed to hosting/CDN → served to end users’ browsers
Architectural patterns and principles
• Static-site pattern: content in Markdown → prebuilt → served as static HTML
• Multilingual structure: one folder per locale, same file hierarchy under each
• Content-driven: all logic lives in the SSG or markdown renderer
• CI/CD integration: automated builds on every commit
Technologies and libraries
• Markdown (content)
• SSG (optional): Jekyll/Hugo/Eleventy/Next.js SSG
• GitHub Pages or similar static host
• GitHub Actions for build/deploy (if used)
• Instagram as an external marketing channel