Skip to content

link the docs, storybook and blog from every page, start the blog, and show flux health in the telemetry band - #51

Open
dapperdivers wants to merge 3 commits into
masterfrom
site-links-and-blog
Open

dapperdivers wants to merge 3 commits into
masterfrom
site-links-and-blog

Conversation

@dapperdivers

@dapperdivers dapperdivers commented Nov 22, 2026 •

Copy link
Copy Markdown
Owner

Makes the rest of the site findable and adds GitOps health to the live cluster numbers.

Findability

  • Header: docs · components · blog next to the social icons (640px and up).
  • Footer: Docs · Components · Blog · Source on every page.
  • Terminal: docs, storybook, blog, source commands; cd docs / open components work too, and ls / help list them.
  • Docs site nav now links to the blog, Storybook and back to the main site (it linked to none of them).
  • All links come from one siteLinks list in portfolio.ts, rendered by a new props-only SiteLinks molecule (story, CSS, test).

Blog

  • /blog is served by Express from a mounted volume (BLOG_PATH, default /app/blog-static), so posts never go into git or the image. A publisher job writes the built site to that volume (cluster side, separate PR).
  • Any static generator works: clean URLs (/blog/post → post.html), the generator's 404.html if it has one, ETag revalidation for pages, immutable caching for hashed assets.
  • Before anything is published, /blog is a real 404 instead of falling through to the homepage as it used to.
  • Dotfiles and path traversal are refused (tested).

Flux health (pairs with dapperdivers/dapper-cluster#4951)

  • Fetches four new Kromgo badges: Kustomization and HelmRelease counts, plus waiting (dependency or rollout in progress) and failing (anything else not Ready).
  • The telemetry band shows a GitOps row under the version chips: counts plus all reconciled / N waiting on dependencies / N failing to reconcile. Failing wins over waiting.
  • The terminal gets flux get all and flux version, and status / neofetch gain a GitOps line.
  • Uptime now handles the 52m / 7h values the cluster PR produces, so the band no longer shows 0 days after a node roll.
  • Until the cluster PR is merged the new badges are missing, and the GitOps row and command just don't show; nothing is guessed.

Docs fixes

  • Two code samples were being run as Liquid: one raised a build warning, and ${{ secrets.SNYK_TOKEN }} rendered as a bare $. Both are wrapped in {% raw %}.

Checks

  • yarn lint 0 errors; yarn test 208/208 (includes a /blog route suite against the real Express app).
  • yarn typecheck: clean apart from 5 errors in untracked local mock files that aren't part of this branch.
  • Docs built in the Dockerfile's ruby:3.2-alpine image.
  • Header, footer and the GitOps row checked at desktop, 640px and phone widths.

…s tokens and components, no client javascript

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant