How jonmircha/jonmircha-website works
Project type and purpose
• This is a static content–driven website (personal blog, tutorial site, PWA) built with HTML templates, components, markdown imports, and a simple Node-based build pipeline.
• It exposes a library of articles (in _imports/blog), reusable HTML components (_imports/components), page templates (_imports/templates), static assets (CSS, JS, images), a service worker (sw.js) and a PWA manifest (manifest.json).
Key architectural components
a. Content source
• Markdown files under _imports/blog
• HTML fragments under _imports/components (header, footer, post, etc.)
• Page templates under _imports/templates
b. Build pipeline (Developer → Build tool → Output)
• Node.js scripts defined in package.json consume the imports and templates
• Generates final .html pages and copies assets to the output root
c. Hosting layer
• Static file server or CDN serving .html, CSS, JS, images, manifest, service worker
d. Client runtime (Browser)
• Requests pages, downloads assets
• Registers service worker for offline caching
• Reads manifest.json to enable PWA install
Relationships and data flow
• Developer edits markdown, HTML fragments, CSS/JS.
• Build tool merges templates with content → produces site files.
• Hosting serves files over HTTP/HTTPS.
• Browser → requests HTML/CSS/JS → user interacts; service worker caches assets.
Architectural patterns and principles
• Static Site Generation (SSG)
• Separation of concerns:
• Content (markdown) vs. Presentation (templates/styles) vs. Logic (build scripts, service worker)
• Progressive Web App: offline support via service worker, manifest for installability
• Related items (e.g., content folders vs. output files) with containers or shaded regions
• Technology stacks next to each component (e.g., “Node.js build script,” “Service Worker”)