Site reinvention: ink & terracotta identity, walkthroughs, full manual - #21
Merged
Conversation
Recast the site's identity as a technical drawing: deep blueprint navy canvas with a fine cyan grid, cyan linework as the primary accent, and a single amber reserved for calls to action. Redefine the color tokens accordingly and drop the warm forge palette. - Bundle Space Grotesk and IBM Plex Mono via @fontsource (no CDN links) - Redraw the mark as a single-stroke squared meander (labyrinth) in cyan with an amber core; regenerate the favicon to match - Replace the icon set with bespoke linework icons in one stroke family - Update the document title and meta to the new positioning
Replace the v1 document-index landing (scaffolding compiler, canonical model, DAG workflows, adapters) with a single narrative that explains the paradigm and gets a visitor installed in minutes. - Hero: tagline, one-line install with copy, and a self-typing terminal transcript that honors prefers-reduced-motion - The thinking: the drift problem, the stance, and the five principles - How it works: the idea-to-ship lifecycle as a blueprint diagram that stacks vertically on mobile - Walkthroughs: two keyboard-navigable tabbed terminal stories, every command verified against the real binary and kit - Proof: the A/B benchmark as honest stat tiles with the cost caveat - Install: per-OS commands from the install scripts plus a 3-step start - Retheme the shared chrome and delete the dead v1 sections
Add /method — a designed, readable tour of the paradigm (principles with their rationale, the roles table, councils, gates, and token economy) that ends by pointing at the canonical kit/METHOD.md. Mount the existing markdown docs at /manual instead of /docs and retheme their prose and syntax highlighting to the blueprint palette (no purple in the code theme). Refresh the 404 page to match.
The v2 binary exposes only init, status, doctor, and update, but the SPA manual bundled all of docs/ — including the v1 guide, quickstart, and the golden-files page, which taught an invented command surface (build, sync, agent, prompt, workflow, validate) and the removed v1 compiler concepts (.daedalus workspace, canonical model, DAG workflows, build/sync). Delete the v1 pages so they no longer ship in dist or appear in the manual sidebar, drop their entries from the docs nav, retarget the installation and index cross-links to current pages, and remove the v1 disclosure blocks now that no v1 content remains.
Swap the site's central theme tokens from the dark blueprint (navy/cyan/ amber) to the light inventor's-notebook palette: technical-paper background, dark-ink text, and a single terracotta accent. Re-derive the ink ramp for light mode (paper surfaces to dark-ink text, all body text AA on paper), turn the cyan linework and amber CTA scales into AA-safe terracotta, and add a dedicated dark 'term' family for the pasted terminal snippets. Retune the grid to faint ink lines, glows to a warm wash, hairlines/shadows/selection/ focus to ink-on-paper, and the favicon/theme-color/color-scheme to light.
Point the window chrome, command pill, and transcript renderers at the new dark 'term' tokens so the animated hero terminal, walkthrough transcripts, and copyable commands stay as deep-ink blocks with paper-toned text — the signature dark-on-light contrast — instead of inverting to light.
Ink-on-paper prose with terracotta links, a paper-toned surface for inline code, and dark pasted code blocks whose highlight.js theme is retuned to light syntax on ink (paper-toned identifiers, warm keywords, sage strings).
Draw the labyrinth mark in ink so its terracotta core reads (the wrappers no longer tint the stroke), and key the walkthrough legend's verified/gate dots to their transcript colors — a paper-readable sage for green, terracotta for the gate — so the two dots stay distinct and match the copy.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The GitHub Pages site goes from a document index to a designed product experience, and the user manual grows from 2 pages to 13 verified chapters.
Landing (new identity: "the inventor's notebook" — ink & terracotta on technical paper):
Manual (13 chapters, example-rich):
Meta: README badges (release, downloads, CI, stars, Go, website); METHOD.md illustrative frontmatter completed (id + risk).
Verification
Three adversarial review passes (site build, content accuracy vs binary/scripts/goreleaser/RESULTS.md, contrast ratios).
npm run buildgreen with VITE_BASE=/Daedalus/; merging deploys via the existing pages.yml.