Spokes.wiki Search Graph Growth About

static-site-wiki

Log

Append-only history. Each entry: ## [YYYY-MM-DD] <op> | <title> where <op> is ingest, query, lint, or split. Query with grep "^## \[" log.md | tail -5.

[2026-05-30] split | spoke created from hub _inbox cluster (5 sources)

Spun out by the hub router (../HUB.md) when five Telegram-delivered sources formed a clear static-site-generator cluster, past the ≥3 threshold and fitting no existing spoke (webperf-wiki was the logged runner-up — adjacent at Core Web Vitals but narrower). Scaffolded from ../CLAUDE.template.md.

[2026-05-30] ingest | five static-site / web-publishing sources

Ingested together as the founding cohort:

[2026-05-30] ingest | Core Web Vitals: WordPress and Astro vs everyone else

Routed in by the hub. Added source core-web-vitals-wordpress-astro (SEJ, CrUX field data). Updated core-web-vitals (7-platform ranking + “page weight is not destiny”), astro (67%, 4th — independently corroborated, behind hosted builders), wordpress (49%, last of 7). Synthesis: partially resolved the neutral-benchmark question, refined the “Astro leads” claim, and flagged a cross-wiki contradiction with webperf-wiki (architecture vs. byte-budget minimalism).

[2026-05-31] lint | health check (URL-ingested sources, 11 pages)

Part of a hub-wide lint. Clean: no orphans, no broken links, ~7.3 links/page; @types good (ItemList for the awesome-lists, DefinedTerm/SoftwareApplication/WebPage elsewhere). Findings: (1) self-identified concept gap stands — Hugo, Next.js, Gatsby, Jekyll, Docusaurus live only in the static-site-generator table and deserve their own pages (the meta-framework-vs-SSG boundary question hangs on this); (2) Eleventy’s build-speed numbers are still self-reported — a neutral build benchmark would close that open question; (3) the page-weight vs. architecture contradiction with webperf-wiki is correctly flagged on both sides and needs a neutral tie-breaker, not a silent resolution; (4) note core-web-vitals is duplicated as a page in both this spoke and webperf-wiki — intentional (separate wikis) but keep the two consistent on re-ingest. No fixes applied.

[2026-05-31] ingest | 5 generator pages — Hugo, Next.js, Gatsby, Jekyll, Docusaurus

Follow-up to today’s lint, which flagged these as mentioned-but-pageless. Created hugo, Next.js, Gatsby, jekyll, docusaurus as Thing pages (SoftwareApplication, not source: true — the tools are referenced by our sources, not ingested). Each is grounded in jamstack-generators-list (star ranks), awesome-static-generators (use-case descriptions), and the static-site-generator table; background framing (GraphQL layer, single Go binary, GitHub Pages history, MDX/versioning) is explicitly marked as general knowledge, and Gatsby’s perceived decline is flagged as unsourced here (sources rank by cumulative stars, not trajectory). Wired inbound links by converting the bare names in the static-site-generator table, jamstack-generators-list, and awesome-static-generators into links. Updated index (SoftwareApplication group) and synthesis (resolved the “missing big names” open question; sharpened the build-only vs. React-meta-framework split — hugo/eleventy/jekyll vs. Next.js/Gatsby/docusaurus).

[2026-05-31] lint | re-check after 5-page add (11 → 16 pages)

Verified post-add health: no orphans, no broken links, full coverage. The new pages each have ≥1 inbound link (from the linked tables/lists) and link back into the concept/source graph. Remaining open items unchanged: trajectory/trend source (rising vs. declining tools), neutral Eleventy-vs-Hugo build benchmark, and the cross-wiki page-weight-vs-architecture tie-breaker.

[2026-06-03] curate | Removed React meta-frameworks (Next.js, Gatsby) — human directive “Remove React meta-frameworks” (scope: a)

Deleted the product pages wiki/nextjs.md and wiki/gatsby.md: React meta-frameworks are full-stack web frameworks, the web-framework side of the SSG-vs-framework boundary — out of scope for this SSG/Jamstack spoke. Confirmed scope with the human (a = Next.js + Gatsby only; Docusaurus kept as a React-based docs SSG). Rewired: removed both index entries; reworked the synthesis open question into a “Scope cut” note; de-linked all remaining [[nextjs]]/[[gatsby]] wikilinks to plain text across wiki pages + this log’s prior entries (they’re comparison mentions now, and log links are verifier-checked). Updated the CLAUDE.md domain header + scope note and the wikis.md registry (dropped Next.js/Gatsby; added an out-of-scope routing note). No raw/ touched. Clean rebuild + verify.

[2026-06-09] ingest | +3 SSGs broadening the genre (VitePress, Zola, MkDocs) — daily-loop cron test

Daily loop picked this spoke (least-recently-grown: last ingest/split 2026-05-31). Added three in-scope, official-source build-time SSGs that extend the genre across language ecosystems and map it better for the standing “is SSG still one category?” question:

[2026-06-10] ingest | Netlify + headless CMS — all-spokes pass (the deploy substrate + content layer)

Two new pages completing the displacement pipeline from its missing sides. netlify (Organization/SoftwareApplication, url, Wikipedia) — the platform that coined jamstack (founded 2014; runs Jamstack Conf/Survey; $2B valuation 2021): git-based CD → SSG build → global CDN, deploy previews, serverless/edge functions. The “where SSG output runs” answer (vercel is the React-leaning cloud-wiki sibling; Netlify is framework-agnostic + named the architecture). headless-cms (DefinedTerm, url, Wikipedia) — back-end-only content-as-API (REST/GraphQL), decoupling content from presentation; pairs with SSGs at build time (git-based Decap/TinaCMS vs SaaS Contentful/Sanity). Together: the wordpress monolith → headless content + SSG build + Netlify CDN (each layer one job). Folded into synthesis (new 2026-06-10 section) + index (DefinedTerm + Organization/Platform). Border with cloud-wiki (Netlify/Vercel as hosts) noted, kept here as the Jamstack originator. No contradictions. 17 → 19 pages.

[2026-06-12] ingest | Astro Server Islands — docs.astro.build

All-spokes daily expansion. Added astro-server-islands (@type TechArticle) — Astro’s server:defer directive: a static, CDN-cacheable shell ships immediately, then personalized/dynamic server islands fetch on demand as HTML (little/no client JS), loading in parallel. The server-side complement to islands-architecture, directly engaging the “how much client JS rides along / where does dynamic content go” open question. Refines Astro’s spectrum: static shell → server islands (no-JS dynamic) → client islands (hydrated); evidence that static-first extends into per-request rendering without becoming a full SSR meta-framework. Wired to astro / islands-architecture; synthesis note added; index gains a TechArticle group. Caveat noted (needs a runtime adapter). 1 new page. Authoritative (official Astro docs).

[2026-06-16] ingest | static-site-publishing (umbrella node) — kind-coverage gap

Added the missing domain umbrella static-site-publishing (DefinedTerm, kind:domain) — flagged by the entity-gaps kind-coverage audit (5 kinded concepts, no domain node). Frames build-time pre-rendering as a publishing model across generator (static-site-generator) → architecture (jamstack/headless-cms) → delivery, vs the wordpress request-time CMS; links synthesis. No new sources (synthesis node). +1 page.

[2026-06-17] ingest | Astro Themes gallery — the SSG turnkey-template layer

Hub-routed from Telegram (astro.build/themes/1/). Clean single-spoke route — Astro is this spoke’s core. Added astro-themes (CollectionPage, source:true, T3 — Astro’s own marketing gallery, volatile counts; ~900 themes read off the 46-page pagination). New facet: the theme/template marketplace layer (free+paid, community-submitted, blog/portfolio/e-commerce/SaaS/docs/education, mostly on Astro 6). Gap-relevance: speaks to the displacement thesis from a new angle — the turnkey “pick-a-theme-and-go” path that bare SSGs lacked is filling in, an ecosystem-maturity signal (not a perf/architecture claim). Folded into astro (new Ecosystem section) and synthesis (turnkey-template-layer paragraph under the pipeline thread). Entity discovery: no new node — publisher is the Astro project, already anchored by astro (SoftwareApplication); the ~900 individual theme authors are low-signal, recorded as a community pool inline. Ran avoid-ai-writing (trimmed “ecosystem” density). +1 page.

[2026-06-17] ingest | Zen (Secd0g/zen) — folded into astro-themes as a worked example

Telegram source: an individual Astro blog theme on GitHub (1★, 47 commits, hobby project; Inter 17px/1.9, 700px measure, dark mode, sidebar TOC, Pagefind search; demo on Vercel; open source, personal use). Dedup/gap-relevance call: it’s a single instance of the turnkey-template layer already paged as astro-themes, advancing no new open question — so folded in as a concrete example (illustrating the typography-first blog corner + the “long tail of small opinionated themes” texture) rather than a standalone thin node for a 1★ repo. Added also: ref to the gallery page. No new page (static-site stays 22). Told the human, who can ask for a dedicated page if they want one. Ran avoid-ai-writing over the added prose.