How inshivank/blog works
Project type and purpose
• This is a minimal static site “BLOG” consisting of two HTML files (index.html, private.html) and a README.md linking to the live GH‐Pages URL.
• Its purpose is to serve a simple blog via GitHub Pages or any static‐hosting CDN.
File structure
• Top level:
• index.html – public landing page
• private.html – private or member‐only content
• README.md – project description and live link
• No backend code, no build scripts, no asset folders (CSS/JS/images would be added similarly if present).
README for additional insights
• The README merely points to the published blog URL
• Implies hosting on GitHub Pages or an equivalent static site host
Components
a. Main components
• User’s Web Browser
• CDN / GitHub Pages (static site host)
• Git repository (source of truth)
b. Relationships & interactions
• Browser sends HTTP(S) requests → CDN/GH-Pages
• CDN fetches index.html or private.html from the Git repository’s build output
• (If private content is protected) CDN / Auth service verifies credentials → serves private.html
c. Architectural patterns/design principles
• Static‐site architecture (no server logic, purely client‐delivered HTML)
• CDN caching for performance
• (Optional future extension) add a client‐side routing or SPA framework, in which case you’d separate static assets (JS/CSS)
d. Key technologies
• HTML5 pages
• GitHub Pages or any static‐hosting/CDN
• (Optionally) OAuth or basic‐auth provider if private.html needs real protection
• (Optionally) Google Analytics or similar
Key points to capture
• The lack of a dynamic backend–it’s purely static content
• The flow from authoring (Git push) to deployment (GitHub Pages rebuild) to delivery (CDN serve)
• Optional extension points (build tools, auth, analytics) clearly marked