Repository navigation
[log] Review log — things Claude did that may want a later check #57
Description
Activity
Session log 2026-07-18 (content batch, commit 7fbbaab):
- ~20 new pages of prose written by Claude aiming for Rufus's voice per Voice: manifesto (and site prose) reads AI-y — restore Rufus's voice #58 — worth spot-checking a few (suggest: everywhere.md, markdown-websites.md, markdown-in-slack.md) to calibrate before more articles ship
- Fact-claims worth a skim: WhatsApp 2024 formatting additions; Confluence having removed markdown; Slack 'Format messages with markup' setting location; Discord subtext/masked-link details; Notion export behaviours — all believed-true from training data, not re-verified against current app versions
- Videos embedded via raw iframes — check they render on the live site (HTML support is on for this site, but confirm)
- Nav now 6 items — check it fits on mobile
Session log (voice work): legacy tutorial word-swaps made by lint fix (delve→dig, utilise→use, empower→help, 'It's important to note that'→'Note that') — semantics preserved but worth knowing they changed; manifesto.md wholesale replaced (previous AI-toned version is in git history if ever wanted); dash-density findings remain in ~8 earlier pages (whatsapp/discord/slack/chatgpt/notion spokes, why.md, videos, blogs stub) — will clean as those pages get touched.
Session log (autonomous round): (1) removed AI-chat residue from the live /markdown-database page (was in the source since its import — 'Around 750 words… Want to tweak anything?'); (2) basics.md heavily rewritten — original playbook intro paragraphs kept verbatim, but structure/examples changed and checkbox labels corrected; (3) word-level fixes in 2023 tutorials (edit-a-website-locally: 'It's important to note'→'Note', "let's dive in"→"let's get started"); (4) app-facts written from training knowledge, not verified against current apps: Telegram chat formatting per-platform details, Reddit old/new editor differences, GFM alerts list — spot-check if precision matters; (5) outreach email drafts impersonate no one but are written AS Rufus — must be personally reviewed before sending.
Session log (P2 + triage round): closed all 8 legacy issues (#1 #2 #6 #9 #10 #11 #12 #20) with individual closing notes — reversible, reopen any that shouldn't have died; residual items landed in inbox #45 including one decision for Rufus (portaljs-site cleanup/redirects). New guide fact-claims worth an eventual skim: average-webpage-lifespan claim (bookmarking), Obsidian Web Clipper URL, garden-history attribution (Caulfield/Appleton), pandoc command syntax, Leanpub markdown support.
Session log (meta round): (1) fixed
.claude/skill files being publicly served on the site — addedcontentExcludeto config.json covering .claude/, docs/, scripts/ and root meta files (belt for the existing publish:false braces); (2) created AGENTS.md (CLAUDE.md symlinked) — future AI sessions get orientation, the voice requirement, act-first workflow, conventions and pre-commit checks; worth a skim since it encodes how agents will behave here; (3) extracted scripts/link-check.py so both checks are one command each.Session log (coggle/roadmap round): roadmap.md uses Tailwind classes in raw HTML — rendering depends on Flowershow passing them through; verify the live page looks right (grid, borders) on desktop + mobile and in dark mode. docs/job-stories.md written by me from project history — JS1 especially is my reconstruction of Rufus's founding intent, worth his skim. Coggle distillation choices (what I called 'already covered' vs backlog) are judgment calls, recorded in docs/coggle-distilled.md.
Session log (visual roadmap round): experiment page is live but unlisted (contentHide) at /x-roadmap-experiment — verify rendering in browser incl. dark mode (SVG text uses currentColor; status colours are fixed hues chosen to work on both themes). Legend uses inline style spans. New issues #64 (canonical markdown texts) and #65 (/timeline) created from Rufus's dictation — scope is my interpretation.
Session log (big wave + critique): shipped blog (/blog + 2 posts), canon, timeline, pluggable-markdown, publish-markdown, landing-pages guide, glossary, git-rescue; roadmap visual promoted into /roadmap + navbar; #61/#64/#65 closed. Fact-claims worth a skim: timeline dates (setext/atx/CommonMark/GFM history — from my knowledge, corrections-welcome note is on the page); canon annotations; git-rescue GitHub Desktop menu labels; Telegram/glossary details as before. The critique (docs/reviews/) contains opinionated scores and priorities — they're my judgment, argue freely.
Session log (top-10 round): wrote tutorial 3 from outline (learn/index updated — check the collaboration steps match current GitHub UI labels); merged kb/google-docs+quirks and apple-notes+ipad-notes into markdown-in-* pages (old files deleted, redirects configured — old URLs now 307); enabled GitHub Discussions on the repo via API (reversible in repo settings); custom.css + footer + bylines change site appearance site-wide; playground.html contains a hand-written markdown renderer (subset — imperfect edge cases are by design, it's a teaching toy); /about states biographical claims about Rufus (OKF/CKAN lineage etc.) — worth his skim for accuracy.
Session log (comparison/badges/v0.2 round): notion-vs-markdown.md makes comparative product claims about Notion (real-time, permissions, API, export, pricing model) from my knowledge — worth Rufus's skim before launch since comparison pages attract pedants; badge SVGs hand-drawn (check rendering of ❤ glyph across platforms); v0.1 epic #46 closed with summary and v0.2 epic opened — reopen if closing was premature.
2026-08-02 — Stubbed #71 for stronger homepage branding via a memorable Markdown-character tai chi/qigong hero animation. Judgment call: kept the animation as the concrete starting point, while recording a possible HTML + Tailwind homepage rebuild and removal of the homepage sidebar/giscus as related scope that may become separate follow-up work. No prose or fact claims need review.
2026-08-02 — Specified and built the standalone Markdown tai chi motion study for #71. Judgment calls: centred living mark; source → compose → flow → release loop; Glyph body selected as the lead of three review modes; experiment kept under
docs/with no homepage integration. Visual/browser review covered desktop, 390px mobile, mode switching and playback; no console errors. Also fixed the link checker to ignore excludeddrafts/and made punctuation-only edits to clear three pre-existing dash-density findings. Full voice and link checks pass.2026-08-02 — Updated v0.2 epic #67 and the local v0.2 narrative plan from Rufus's status update: GA4 is live, giscus is installed, and the immediate queue is now Search Console → final checks → launch/distribution. Added a consolidated tickable launch checklist to #67. Existing uncommitted GA4 changes in
config.jsonanddocs/plans/v0.2.mdwere preserved and not committed by this session. Config JSON, voice lint, link check andgit diff --checkall pass.2026-08-02 — GA4 setup
- Created the The Way of Markdown GA4 property under the Flowershow Analytics account using Rufus's Datopian Chrome/Google login.
- Created the web stream for
https://wayofmarkdown.com; measurement IDG-HZH2GBB7K8; enhanced measurement left enabled. - Judgment calls: retained the account defaults (United States reporting country, Los Angeles time, USD); selected Jobs & Education, Small — 1–10 employees, and the traffic + engagement/retention objectives. All are editable in GA Admin.
- Added the ID to
config.json, updated the v0.2 narrative log, and pushed00ad8d8(launch: add GA4 analytics) tomain. - Verification: valid JSON; voice lint 72/72; link check 71/71; live homepage source loads the matching
googletagmanager.comscript and initializesG-HZH2GBB7K8. - Still worth checking later: GA Realtime ingestion was not independently observed yet; Google notes that data collection can take time to start.
- Published prose: none.
2026-08-02 Search Console session: verified the
wayofmarkdown.comdomain property in the Datopian Google account via a TXT record in Datopian Cloudflare, and submitted the sitemap. Judgment call: used manual DNS verification rather than granting Google one-click Cloudflare access. The sitemap is publicly reachable (HTTP 200, valid XML), but Search Console's immediate first-fetch status wasCouldn't fetch; leave the verification TXT record in place and recheck processing later.2026-08-02 — tai chi study v4 (issue #71). Local commits
cfa943c,4a059ac. Not pushed — the brief says not to push merely to review the animation, and this touches nothing published.Rufus's verdict on v3 was that it had no elegance, beauty or flowingness. Diagnosis and what I changed:
- Uniform-width polylines run through the joint list. That is a stick figure by construction, whatever the poses do. Replaced with tapered brush strokes (filled variable-width ribbons), one running unbroken from the sacrum over the crown.
- Poses hand-placed joint by joint, so limbs changed length mid-interpolation. Elbows and knees now come from two-bone IK; only the hand arcs, pelvis glide and foot swing are authored.
- The figure never took a step — it slid 850 units in one phrase. It now performs one step of Brush Knee and Push and repeats it, a stride at a time, twenty-two steps across the strip.
Judgment calls worth a second opinion:
- Forty-second crossing. Twenty-two steps at ~1.9s each. That is a natural tai chi tempo and I did not want to speed it up into something twitchy, but it is long for a hero loop. Nobody watches a loop for forty seconds — the bet is that a glance shows a figure mid-stride with ghosts behind it. Could be wrong.
- The phrase repeats on the same side rather than alternating left and right as the form proper does. Cheap to add, doubles the pose data, and is barely visible in strict profile. I chose not to.
- Both hands kept in separate bands of the body (upper at shoulder height, lower at the waist) rather than following the form exactly. In strict profile two hands at the same height read as a knot.
- Named form. I moved from Parting the Wild Horse's Mane to Brush Knee and Push because the latter is a genuinely travelling phrase, which the left-to-right brief needs. The brief says the exact phrase is not locked.
- On narrow screens the camera travels with the figure instead of shrinking the strip to fit. At 390px the whole strip would put the figure at ~35px, below the brief's 50–100px floor.
Prose to skim: the version 4 section of
docs/plans/2026-08-02-markdown-tai-chi-design.md, and the new log line indocs/plans/v0.2.md.Unverified claims: none factual. The tai chi terminology (Brush Knee and Push, bow stance, weight settling before the hands arrive) is my own reading of the references in the design note, not checked with anyone who practises.
Checks:
check-markdown-tai-chi.mjs,voice-lint.py,link-check.pyall pass. The movement half of the check script imports the prototype's own geometry and asserts bone lengths, floor contact and step-boundary continuity; I verified each assertion fires by deliberately breaking the prototype, after two first attempts at breaking it turned out to be no-ops.2026-08-08 — tai chi mark, finished (issue #71). Continues from the 2026-08-02 comment above. Commits
cfa943c..965bad8, all pushed.Where it ended up: the mark is the syntax figure — the one written in Markdown punctuation. It's on the homepage hero, in the navbar (as a static ink version), and in a press kit at
/press. Full file map and the asset-regeneration recipe are at the top ofdocs/plans/2026-08-02-markdown-tai-chi-design.md.Rufus's direction changed the work twice, both times for the better: drop the crossing for one movement in place (which also removed the step cycle that kept reading as walking), and go with syntax for the mark.
Judgment calls worth a second opinion:
- No animated navbar logo, against the option Rufus raised. Chrome motion is inescapable, it contradicts a mark whose quality is slow and settled, and 32px is well below the ~80px the syntax figure needs. Resolved as a responsive identity: animated syntax at hero size, static ink small. Also replaced Flowershow's default logo, which the navbar was still wearing.
- The robe was parked, not deleted, at
/tai-chi-robe.html. Rufus called it a bridge too far and he's right — the hem slides as one rigid shape and the rear leg disconnects. The file carries its own note on what would be needed. - Syntax version of the robe: tried and dropped in ten minutes. Rendered it as a probe rather than arguing. Outlines don't survive translation to sparse characters — the body's strokes are the body, the robe's are its boundary, and an outline made of gaps is mostly gaps.
- The homepage h1 is now "The Way of Markdown" alone, with "Own the source. Compose with anything." demoted to a lede. The
<title>is unchanged so search results are unaffected, but flagging it since SEO is the site's strategy. - Homepage layout overrides are scoped with
:has(.wom-hero)— no reserved sidebar padding, no TOC, hero breaks the 65ch reading measure. Other pages verified unaffected. If:has()is unsupported the duplicate title reappears; it degrades rather than breaking. - GIFs render on white, not transparent — GIF has one-bit transparency, which would leave hard edges on anti-aliased characters.
Things I got wrong, for the record: I shipped three regressions to the live homepage and fixed them in follow-ups — an invisible h1 (theme hides the first content h1), a green-on-green CTA label (content links take the accent colour, same green as the button), and the hero squeezed into a third of the page (16rem of padding reserved for an unused sidebar). All were theme-CSS collisions my local preview couldn't show. What worked was reproducing the live page against the real stylesheets and reading computed styles. I should have done that before the first push.
Also worth knowing: across the session five of my check-script break-tests turned out to be no-ops that passed — assertions that looked green and meant nothing until fixed. Every assertion in
scripts/check-tai-chi.mjshas now been verified by deliberately breaking the prototype.Unverified fact-claims: the tai chi terminology (An / press-and-push from Grasp Sparrow's Tail, bow stance, fixed-step vs moving-step push hands) is my own reading, not checked with anyone who practises. The human-proportion figures (7.5 heads, legs 47–50%, arms 36–38% of standing height) are standard figure-drawing conventions and are now asserted in the check.
Prose to skim:
press.md(public), the homepage hero copy inindex.md, and the "Where it landed" / "What this cost us" sections of the design note.Checks: prototype check, voice lint, link check all pass. Live URLs spot-checked after each deploy.
Homepage repair session (2026-08-08): rebuilt the complete homepage as a responsive HTML/Tailwind page with
layout: plain; centred the animated mark immediately below the title; retained all existing sections and destinations; removed the old 168-line hero/layout override block. Judgment call: kept a two-line scoped Flowershow compatibility rule because the theme hides the first content h1 even in the plain layout. Previewed via a temporary Flowershow site at 1440px and 390px. Voice/link/tai-chi/config checks pass. Prose worth a skim: none materially rewritten. Unverified fact-claims: none.Session: databases guide rename + pattern-page fixes
Judgment calls
- Renamed
markdown-databases.md→markdown-databases-guide.md(not-howto). Rufus first suggested-howto, butlearn/howtos/create-a-simple-catalog-of-anything.mdis the real step-by-step;-howtoon the guide-level page would collide. Addedconfig.jsonredirect/markdown-databases→/markdown-databases-guide. - Updated all inbound links: explore.md, index.md, markdown-based.md, roadmap.md (+regenerated SVG via roadmap-gen.py), scripts/roadmap-map.json, llms.txt.
markdown-database.md"An example": the SQL block previously read as a live demo ("You now have a movies database. Query it:"). Reframed — it's an illustration of what indexing the folder with MarkdownDB gives you, with an explicit "this isn't a live demo" line.- Added a "Seeing it without code" section to
markdown-database.mdreusingtable2.png(Obsidian Bases screenshot). Note: screenshot is HP characters, not the movies example on the page — labelled it honestly as "a handful of character files". - Colophon: removed raw
https://github.com/flowershow/markdowndb/issues/7URL → "Originally notes in the markdowndb project and elsewhere."
Prose worth a skim:
markdown-database.mdlines ~82–99 (new framing + screenshot section) and the new closing "Build one:" pointer.Open question from Rufus: whether guide + tutorial + pattern-essay is one page too many. Left all three; guide stays short and links out (his call). Portaljs post = the existing
learn/tutorial, already incorporated.Unverified: none.
- Renamed
2026-10-02 — brand and redesign brief, draft 1
Shipped:
docs/brand.mdand the brief artifact (https://claude.ai/artifact/Qq8iMaSEk3diuEihrcLhT6). Nothing on the live site changed.Judgment calls worth a look:
- Reframed the narrative positive on Rufus's note ("Markdown is a great format. What matters is what it lets you build, and that you own it afterwards."). The "nobody cares about markdown" line stays on
why.mdas it is; I did not touch published pages. - Recommended retiring green as the brand accent in favour of seal vermilion. Green survives only as the roadmap's "built" status. That is a real switch with costs (OG card, badges, roadmap); costed in the brief.
- Recommended all-mono prose (direction A) with an explicit fallback to a sans for prose. The fallback is a safety net, not a hedge: it is one CSS rule.
- Recommended "Own the source. Use any tool." over "Compose with anything". Rufus already said the second half is unsettled.
- Proposed that the Gemini hero video goes, replaced by an SVG push-hands animation built on the August tai chi code. The brief says so plainly; the video stays live until a replacement exists.
- Mood board references (The Monospace Web, iA Writer, Hundred Rabbits, Daring Fireball, sive.rs, CommonMark) are my picks; screenshots captured today and embedded in the brief.
Prose worth a skim: the brief's copy, and the narrative paragraph at the top of
docs/brand.md. Both internal, so no voice-lint run; both written to be read by Rufus, not published.Unverified claims: none that affect the site. Geist Mono is on Google Fonts (the brief renders in it, so verified by rendering).
- Reframed the narrative positive on Rufus's note ("Markdown is a great format. What matters is what it lets you build, and that you own it afterwards."). The "nobody cares about markdown" line stays on
2026-10-02, later — Draft 2 of the brand brief. Judgment calls: dropped the two-part tagline in favour of a single headline ("Markdown is eating the world", Rufus's line); recommended three of six directions and named a 5+1 hybrid as my pick; wrote a first-draft subline in Rufus's register that will need his edit; the SVG illustration and diagrams in the mocks are hour-long stand-ins. docs/brand.md rewritten around the story; draft 1 visual identity recorded as rejected with the lesson. Nothing published to the site.
2026-10-02, draft 3 of brand brief. Judgment calls: recommended a new brush-stroke
#mark over the tai chi figure (figure kept as site character, not deleted); wrote the subline and the 'Openness is the way' sign-off for Rufus to edit; Unix framing paragraph on the front page mock is mine. Front-page graphics are quick stand-ins. Factual claims in mock copy (Unix 'do one thing well' idea) are paraphrase, not quotes. Live site untouched.2026-10-02, visual round 2 (wom-b5o.2). Built three full front pages from direction 1, published side by side: https://claude.ai/artifact/VdK76NQDZHArvnn7fy9u8Q. Sources in
docs/brand/round-2/. Judgment calls: (1) A keeps the direction 1 hero untouched and adds the offer line under the headline; (2) B borrows only direction 4's type scale and ASCII picture, no yellow, no Bricolage; (3) C treats the page as index.md, which is my idea and unproven. Mock copy includes honest-limit claims ("real-time editing is still a step behind", "comments need a plugin") that are placeholders, not checked. Nothing public changed.2026-10-02, brand visual direction decided (wom-b5o.2 closed). Four rounds in one day. Round 2 (variants of direction 1) was too narrow; reset to a mood board and a reference gallery (Rufus's verdicts in
docs/brand/refs/review-2026-10-02.md); round 3 built three feels from different references; he chose option 2's layout (Devouring Details) with option 3's drawings (Sketchplanations), then three tweak passes. Spec now indocs/brand.md'Design direction' with open questions; mock https://claude.ai/artifact/PiAxmgGNG5Prsn1GhV4VMm (front page, Replacing Notion guide, design-basis page). Judgment calls worth a skim: (1) all sketches are code-generated (sketches.py), so the style is reproducible, which Rufus's 'no hand-drawn' rule needs; (2) orange#ff5a00replaces blue in the UI, blue retired; (3) 'Leave Notion' reworded to 'A markdown Notion' / 'Replacing Notion' on his note; (4) the honest-limits copy in mocks is placeholder. Nothing public changed. Seven todo beads filed under wom-b5o. Reference research also logged to ~/src/rufuspollock/ux-patterns (committed, not pushed).2026-10-03 session: new design live (round 5).
Judgment calls to skim:
- Homepage CTAs kept from the old page (Start the roadmap / Markdown in 10 minutes) rather than the mock's Replace Notion button.
- Tai chi video and the "Own the source. Compose with anything." line are off the homepage (frontmatter title still uses the line, for SEO). Video still on /press.
- Homepage contents list maps to real pages: Build (7 guides + all guides), Learn (basics, playground, roadmap, tutorials, every app, onboarding, reference), Why (why, manifesto, database pattern, Notion vs markdown, timeline, videos).
- Logo + favicon: brush # seal, a placeholder until the logo thread (docs/plans/2026-10-03-logo-brief.md).
- Removed the lessflowery theme (Way Into AI runs on the default theme).
Unverified: phone width (headless Chrome can't go below ~500px); dark mode not checked.
Known gaps: code-block syntax colours are off-palette; nav links unchanged.2026-10-03 (later): blog post + changelog for the new look.
Prose to skim (first person, your byline): https://wayofmarkdown.com/blog/2026-10-03-finding-a-look
Fact-claims to check:
- "took two days" (brand track 2026-10-02 to 03)
- "a short tai chi video I'd made with Gemini"
- "how do you find a look for a thing is a question I get asked" (invented framing, cut if untrue)
- Way Into AI linked as wayintoai.com
Also: author pages added (people/rufus, people/elisapaka = Elisa Paka, co-author of the tutorials); roadmap redrawn (map mode, animated); iso version backed up in docs/brand/diagrams/.
2026-10-03: nav and changelog. Nav is now four dropdowns, Use / Learn / Why / About (matches the homepage contents, whose first column is renamed Build → Use). Roadmap moved under Learn (still the homepage CTA); Explore renamed Site index under About; "Markdown in apps" → Apps. Changelog published at /changelog (Flowershow's built-in changelog layout), under About rather than top-level until there are more entries. Footer reorganised to the same four groups.
Nav, later: Roadmap promoted as the one top-level link (orange, after the four menus). Changelog not promoted (one entry). Blog and changelog kept separate: changelog = short dated notes for every notable change (and the cross-project convention); blog = the few that deserve a story; entries link to posts. Menus restyled as markdown lists (+/− trigger, '- ' items).
2026-10-07: markdown log section
- Judgment call: new
/logssection (flat<List>, one dated file per item) for lightweight ecosystem news/refs, modelled on wayintoai logs but simpler. Separate from/changelog, which stays site news. Nav: Why → Markdown log. - First entry: Google Docs opens .md natively. Official announcement + help page as primary source; Chandu Thota's thread quoted for the AI angle.
- Prose worth a skim: the 'Why it matters' paragraph is written in first person as Rufus.
- Unverified: haven't tested frontmatter/wikilinks/footnotes handling in Docs (entry says so).
- Pre-existing voice-lint failures (dash density) in kb/follow-builders.md and manifesto.md, not touched.
- Judgment call: new
Running log of autonomous actions worth a later skim. Convention: Claude appends a comment per work session; check items whenever convenient; nothing here is blocking.
Initial entries (2026-07-18):
index.md(landing),why.md,manifesto.md(distilled from your VISION/draft/BLURB),docs/naming.mdsense-check,docs/vision.md(distillation of your dictated vision).publish: falseassumption — used on README + docs/ to keep them off the live site; verification is v0.1: Live-site QA — publish:false + visual pass #49. If Flowershow ignores it, internal docs are temporarily public (low stakes, but noting).learn/introduction.md,docs/INBOX.md(migrated to [inbox] Ideas, links and loose TODOs #45).github.md→kb/github-tips.md; 2023 design/skeleton docs kept (moved todocs/) rather than deleted; tutorial-2 screenshots recovered from flowershow repo history commit024bbb3c; Apple Notes note got a cross-ref to the iPad note.