How ummitc/links works
Project type and purpose
• This is a single‐page, static, front-end landing site built with React + Vite (TypeScript).
• It serves as a minimalist “digital business card”—a Linktree-style personal page—hosted on GitHub Pages.
• CI/CD is handled via GitHub Actions; versioning by semantic-release.
File structure
• Top level:
• public/ → static assets and redirect rules
• src/ → React components (App.tsx, pages, components, hooks, styles)
• index.html, package.json, vite.config.ts, tsconfig*.json
• .github/workflows/ → CI/CD definitions
• No backend code; purely client-side.
• Build target (dist/) is generated by Vite, then deployed to GitHub Pages.
Core components
a. Developer workstation
• Code editor, local dev server (vite)
• Yarn to install/run
b. Source Code Repository (GitHub)
• Branches: dev, master
c. CI/CD (GitHub Actions)
• Workflows:
• preview.yml → runs dev preview
• semantic-release.yml → calculates version
• yarn.yaml → runs build & deploy to GitHub Pages
d. Static Site Generator / Build System
• Vite bundler + TypeScript compiler
• PostCSS/Tailwind CSS + DaisyUI
e. Hosting
• GitHub Pages – serves dist/ as static website
f. End User / Browser
• Fetches index.html + JS/CSS from GitHub Pages
• Renders SPA, navigates routes (Home, About, Blog, Gear, Projects)
Relationships & Data Flow
• Developer → push commit → GitHub repo
• GitHub Actions workflows (CI/CD) triggered by push
• Build job: Vite compiles / bundles / outputs to dist
• semantic-release tags new version → updates changelog, GitHub Releases
• Deployment job: dist folder → GitHub Pages
• End user browser → HTTP GET → GitHub Pages → serves files → React SPA initializes
Architectural patterns & design principles
• Component-based UI (React) with folder separation: pages vs. shared components
• Static site generation / SPA served as static assets
• GitOps / Git-driven CI/CD: Infrastructure (hosting) changes via code commits
• Conventional commits + semantic-release for automated versioning
Technologies & frameworks
• React + TypeScript + Vite
• Tailwind CSS + DaisyUI (CSS utility / component library)
• Yarn 4, Node.js
• GitHub Actions, semantic-release
• GitHub Pages
Essential elements to capture
• Separation of concerns: source code vs. build vs. hosting
• Data (file) flow from developer to end user
• CI/CD pipeline stages: build, version, deploy
• Client-side routing and component hierarchy (optional detail)