Project / Agent & Engineering
Messiahub
This site: a sectioned static site in vanilla HTML/CSS + Node.js.
Markdown content, templates, and a zero-dependency build script; four content sections and a project archive share one design system.
Running
Overview Project overview
Messiahub is this site itself: a project and engineering-notes site maintained with vanilla HTML/CSS, Node.js, and Markdown.
Motivation Why it exists
The goal is a personal site with no heavyweight framework: long-term maintainable, with project records, engineering notes, and a small amount of writing in one place.
Architecture Key architecture
- Markdown with frontmatter under content/ is the single content source; templates/ provides page skeletons; build.mjs generates static HTML, the sitemap, and section theme variables.
- assets/ holds only hand-written CSS, a little JS, the favicon, and article images; no frontend framework, no runtime dependencies.
- server.mjs is a static file server with CSP, X-Content-Type-Options, Referrer-Policy and other security headers; deployment uses Cloudflare Tunnel.
- The project archive is maintained centrally in projects.mjs; URLs of the four content sections stay stable.
Capabilities Capabilities
- Four content sections, a project archive, and a full article index; Markdown posts with prev/next, reading time, tags, sitemap, and robots.
- Light/dark themes, keyboard-accessible mobile navigation, reduced-motion preferences, semantic HTML, and skip links.
- Draft flagging: posts marked draft: true stay out of public lists, counts, and the sitemap.
Limitations Known limitations
- No site search, CMS, comments, or English edition in the original scope — the English UI scaffolding arrived later (plan A).
- No database while content volume is small; articles and projects are maintained as files.
- Deployment and production release are separate steps; a successful build does not mean the site is live.
Validation Testing & validation
- npm run build generates the static site; npm run check verifies internal links, assets, and CSP inline risks; browser audits cover desktop and mobile breakpoints.
- Each upgrade records its baseline, changes, and verification results; production release requires separate approval.