How saijogeorge/blog works
Project Type & Purpose
• This is a purely static, file-based personal portfolio site (“SaijoGeorge.github.io”) hosted on GitHub Pages.
• It aggregates dozens of self-contained micro-tools (each in its own directory), plus one Gatsby-based React app under json-ld-schema-generator.
File Structure Analysis
• Top-level: static HTML pages (index.html, contact.html, projects.html, etc.), global assets (css/, js/, images/).
• Many sibling directories (e.g. dummy-credit-card-generator/, price-to-hours-worked/, ai-art-styles/, etc.): each contains its own HTML, CSS, JS, fonts and images—completely self-contained micro front-ends.
• One subproject built with Gatsby/React: json-ld-schema-generator/ featuring typical Gatsby directories (src/, public/, .cache/, page-data, static assets, Workbox).
README Insights
• Confirms it’s a personal portfolio site bundling multiple static tools.
• No backend code or API definitions—no server-side components beyond GitHub Pages hosting.
a. Client Layer:
• Web Browser/User Agent
• Mobile/Tablet/Desktop
b. Delivery Layer:
• GitHub Pages (acts as a static file server + CDN)
• Optional CDN layer (e.g. Cloudflare) in front of GitHub Pages
c. Storage Layer:
• GitHub repository storing all static assets
• Build artifacts (Gatsby output under json-ld-schema-generator)
d. Build Pipeline (for Gatsby app only):
• Source (json-ld-schema-generator/src/) → Node.js/Gatsby CLI → Static HTML/CSS/JS → public/ → Deploy to Pages
e. Individual Micro-tool Modules:
• Each tool directory contains standalone assets that GitHub Pages serves directly—no runtime interactions between them.
Relationships & Data Flow
• Browser requests URL → DNS resolves to GitHub Pages CDN → CDN fetches static files from the repo → serves HTML/CSS/JS → browser renders.
• For Gatsby-based tool: build pipeline runs at deploy time; output is static, then delivered like other tools.
Architectural Patterns & Principles
• JAMstack: pre-built markup, served over CDN, decoupled from any server-side runtime.
• Micro-frontend style: each tool is an isolated static “app” folder.
• Single responsibility: directories grouped by project name, assets colocated.
• Cacheable assets: css/, js/, images, and hashed filenames for cache busting (e.g., in css-puns/).
Technologies & Frameworks
• GitHub Pages for hosting
• Vanilla HTML/CSS/JS for most tools
• Gatsby (React, GraphQL, Workbox) for the json-ld-schema-generator tool
• Build tools: Node.js, Webpack (for Gatsby), Babel, plugins for offline support