How integerous/goquality-dev-contents works
Project Type and Purpose
• This repository is not a web-app or library, but a curated collection of developer content (≈1,500 links down-selected to ≈450) organized into 16 topic folders. In effect, it’s the content source for goquality.dev, a static “high-quality dev content” site.
File Structure Analysis
• Top-level:
• LICENSE
• README.md (project overview & huge list of curated links)
• 고퀄리티 컨텐츠 모음/ (the “content” folder)
• Inside “고퀄리티 컨텐츠 모음/”: 16 numbered subfolders (“1. 개발 일반”, “2. 개발자 커리어”, … “16. 기타”), each with its own README.md to list links for that category.
• No “src”, “frontend” or “backend” code – all files are Markdown; presumably a static‐site generator (Hugo/Jekyll/etc.) converts these to HTML.
Architecture Components
a. Content Repository
• Markdown files in GitHub (your source of truth).
b. Static Site Generator (SSG)
• Hugo/Jekyll/Next.js Export: reads folder structure + frontmatter, renders pages.
c. CI/CD Pipeline
• GitHub Actions (or Netlify build hook) detects pushes to main, runs SSG, outputs /public or dist.
d. Hosting & CDN
• The generated static assets are deployed to a static host (GitHub Pages, Netlify, Vercel) and served via a CDN.
e. User’s Browser
• Requests goquality.dev, assets returned from CDN, page rendered with responsive HTML/CSS/JS.
Component Interactions
• Developer → (push) → GitHub repo
• GitHub Actions → (build) → Static HTML/CSS/JS
• Actions → (deploy) → Hosting platform (Netlify/Vercel/GH-Pages)
• CDN edges cache content
• End-user browser → CDN edge → content
Architectural Patterns & Principles
• Content-As-Code: Markdown + Git versioning
• Static-First: no dynamic backend; scale via CDN
• CI/CD: automated build & deploy on commits
• Folder-Driven Routing: folder names → URL structure (/1.-%EA%B0%9C%EB%B0%9C-%EC%9D%BC%EB%B0%98 → /category/dev-general)