Corpus story lab

This is a lab. Everything on this page is experimental and subject to change: the thresholds, the groupings, the charts themselves, and which of them survive at all. Views get added, reworked and deleted. Numbers here describe this archive on the day it was built and will shift as writing is added. Nothing here is a finding.

A working gallery, sorted into three. Everything here asks a question of the same archive, but not everything earned the same standing. Selected holds the three views I would defend to a reader. How to distrust this holds the ones whose real job is to show where the others are weakest. Workbench is uncurated and stays folded away: interesting to make, not yet worth anyone's time to read.

The semantic model suggests which texts resemble one another, although many were already deliberately cross-linked; the interpretation still belongs to the writer.[10]

ASelected

Three views that say something this archive alone could say. Each names specific entries rather than describing the corpus in aggregate, and each reads without a paragraph of method first.

1.0Ideas that came back

8 echoes after 3+ years · 44 near links

Question: which ideas followed me between jobs, technologies and years? Time finally earns the horizontal axis. The tall arcs are the returns: non-companion pairs separated by at least three years, so an arc is a recurrence rather than two versions of the same recent piece. Some are deliberate callbacks; others are uncited echoes.[1]

The faint mat along the axis is everything closer together than that. Those are not returns and are not the argument; they are there because where they bunch up is a period when a lot of related writing happened at once. Read the height as time between two entries, never as strength.

Long-distance semantic echoes through the writing archive Entries run chronologically from 2013 to 2026. 8 tall curves connect related pairs separated by at least three years; a lower, fainter mat of 44 curves connects related pairs closer together in time, and bunches where a period produced several related entries. Career chapters appear beneath the baseline as context, not causes. Migrating to Zurb Panini 2.0 to Moving from Panini to Eleventy, 2.4 years apart, similarity 0.6 Your browser utility wants to be a floating palette to PDF-A-go-slim: a browser-based PDF optimizer, 0 years apart, similarity 0.6 EMBL-EBI Day: Visual Framework 2.0 outreach to Something new for 2022, 2.5 years apart, similarity 0.61 Making PDFs more viewable to Your browser utility wants to be a floating palette, 0.5 years apart, similarity 0.61 Individualism is the flavor AI chatbots can't stomach to Improving AI chatbots with an editorial handbook from your best content, 0.3 years apart, similarity 0.61 Plenty to learn from Fedora's approach to AI code to Why 'reviewed' should be a protected verb, 0.5 years apart, similarity 0.61 The power of the pause: How planning beats prompt tuning to The practitioner's guide to planning digital transformation (Parts 3-4), 0.4 years apart, similarity 0.61 The ladder was always context to The right answer has to be woven, 0 years apart, similarity 0.61 Let AI worry about the code, you worry about the work to CADI: a prescriptive path for slop-free AI in content work, 0.1 years apart, similarity 0.61 It's been 3.5 years to A fresh coat of paint and making information actionable for 24 years, 1.3 years apart, similarity 0.62 AI coding tools turned my once-a-year hobby project into a daily habit to Four gears of AI-assisted development: from coding to context, 0.1 years apart, similarity 0.62 Thoughtful AI integration beats bolted-on Clippy to Comprehension debt, when AI-generated code outpaces human understanding, 0.5 years apart, similarity 0.62 The power of the pause: How planning beats prompt tuning to Large projects need large communicating, 0.2 years apart, similarity 0.63 The power of the pause: How planning beats prompt tuning to Let AI worry about the code, you worry about the work, 0.6 years apart, similarity 0.63 Digital transformation for complex organizations (Parts 1-2) to Content architecture: the delivery problem, 0.2 years apart, similarity 0.63 Better corporate design through information architecture to Fluid IA to enable user discovery, prepare for change, 0.1 years apart, similarity 0.64 Faster scientific websites through reusability to EMBL-EBI Day: Visual Framework 2.0 outreach, 0.8 years apart, similarity 0.64 Thoughtful AI integration beats bolted-on Clippy to Four gears of AI-assisted development: from coding to context, 0.5 years apart, similarity 0.64 Integrating Eleventy with gulp, upstream JS to Fractal and Eleventy: Getting static sites closer to the design system, 0.1 years apart, similarity 0.66 Comprehension debt, when AI-generated code outpaces human understanding to Four gears of AI-assisted development: from coding to context, 0 years apart, similarity 0.66 Developers are becoming context technical writers for AI to Four gears of AI-assisted development: from coding to context, 0.5 years apart, similarity 0.66 The power of the pause: How planning beats prompt tuning to CADI: a prescriptive path for slop-free AI in content work, 0.7 years apart, similarity 0.68 Content architecture: the delivery problem to The right answer has to be woven, 0 years apart, similarity 0.68 The ladder was always context to Four gears of AI-assisted development: from coding to context, 0 years apart, similarity 0.68 Developers are becoming context technical writers for AI to The right answer has to be woven, 0.5 years apart, similarity 0.69 Four gears of AI-assisted development: from coding to context to Let AI worry about the code, you worry about the work, 0 years apart, similarity 0.69 Go-go-go … I missed EmbedPDF to PDF-A-go-slim: a browser-based PDF optimizer, 0.4 years apart, similarity 0.7 Thoughtful AI integration beats bolted-on Clippy to CADI: a prescriptive path for slop-free AI in content work, 0.7 years apart, similarity 0.7 Developers are becoming context technical writers for AI to Why context engineering was always the job, 0.5 years apart, similarity 0.7 Improving AI chatbots with an editorial handbook from your best content to CADI: a prescriptive path for slop-free AI in content work, 0.5 years apart, similarity 0.7 Context engineering beats prompt tricks for AI agents to The right answer has to be woven, 0.5 years apart, similarity 0.71 Building a component library adopted across 50+ scientific properties to Decoupling content from platforms across 80 properties, 1.1 years apart, similarity 0.71 EMBL-EBI Day: Visual Framework 2.0 outreach to Enabling a more dynamic EMBL online, 2.5 years apart, similarity 0.73 The ladder was always context to Why context engineering was always the job, 0 years apart, similarity 0.74 Making PDFs more viewable to PDF-A-go-slim: a browser-based PDF optimizer, 0.5 years apart, similarity 0.75 Developers are becoming context technical writers for AI to Context engineering beats prompt tricks for AI agents, 0 years apart, similarity 0.75 Site search without a search service to Semantic search on a static site, no API keys required, 0 years apart, similarity 0.76 Context engineering beats prompt tricks for AI agents to Why context engineering was always the job, 0.5 years apart, similarity 0.77 Thoughtful AI integration beats bolted-on Clippy to Improving AI chatbots with an editorial handbook from your best content, 0.3 years apart, similarity 0.8 Why context engineering was always the job to The right answer has to be woven, 0 years apart, similarity 0.81 Making PDFs more viewable to Go-go-go … I missed EmbedPDF, 0.1 years apart, similarity 0.82 Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon to NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT, 0.1 years apart, similarity 0.84 Digital transformation for complex organizations (Parts 1-2) to The practitioner's guide to planning digital transformation (Parts 3-4), 0 years apart, similarity 0.85 Measuring success beyond the page view to How to measure impact when analytics lie, 0.1 years apart, similarity 0.89 Better corporate design through information architecture to Content architecture: the delivery problem, 8.7 years, similarity 0.62 What if: A web font for data to A data font, from the inside out, 8.1 years, similarity 0.83 A new site for little reason to A simpler, faster site: moving to pure Eleventy v3, 8.1 years, similarity 0.64 Introducing the Content-Action Model for Web Systems to Digital transformation for complex organizations (Parts 1-2), 8 years, similarity 0.61 Fractal and Eleventy: Getting static sites closer to the design system to A simpler, faster site: moving to pure Eleventy v3, 5.8 years, similarity 0.68 Moving from Panini to Eleventy to A simpler, faster site: moving to pure Eleventy v3, 5.1 years, similarity 0.72 Better corporate design through information architecture to EMBL.org: Empowering users to navigate a large scientific organization, 4.1 years, similarity 0.6 Faster scientific websites through reusability to Enabling a more dynamic EMBL online, 3.3 years, similarity 0.63 2013-03-21 — Cutting down on Postfix spam relaying 2013-06-12 — Muliple IPs on an Ubuntu EC2 VPC? Yes, please! 2013-12-08 — A model for better content, better readers, better journalism 2014-04-07 — UX success story: Doubling conversion rates, sales 2015-01-28 — How to install Lyra the graphical visualization environment 2017-07-23 — Better corporate design through information architecture 2017-07-25 — A new site for little reason 2017-09-13 — Fluid IA to enable user discovery, prepare for change 2017-10-06 — Five highlights from EuroIA 2017 2017-10-27 — 8 Video conferencing tips, dos, don'ts 2017-11-12 — Comparing IBM Plex and Fira Sans 2018-01-22 — The Content-Action Model origin story 2018-01-22 — Introducing the Content-Action Model for Web Systems 2018-02-07 — UX, discovery, analysis + the CAM 2018-02-10 — Migrating to Zurb Panini 2.0 2018-03-19 — What if: A web font for data 2018-03-29 — Inside the Content-Action Model 2018-09-12 — Faster scientific websites through reusability 2019-06-27 — EMBL-EBI Day: Visual Framework 2.0 outreach 2019-10-21 — Integrating Eleventy with gulp, upstream JS 2019-11-12 — Fractal and Eleventy: Getting static sites closer to the design system 2019-11-18 — Building your first page with the Visual Framework 2.0 2020-02-08 — Publishing since the 2000s 2020-07-13 — Moving from Panini to Eleventy 2020-11-11 — Lerna monorepos with fewer tags 2020-12-12 — Using Nunjucks templates with React 2021-08-30 — EMBL.org: Empowering users to navigate a large scientific organization 2021-12-21 — Enabling a more dynamic EMBL online 2021-12-23 — Something new for 2022 2025-05-08 — It's been 3.5 years 2025-07-10 — Drupal delayed by Azure MySQL 2025-08-11 — Making PDFs more viewable 2025-08-31 — A simpler, faster site: moving to pure Eleventy v3 2025-09-04 — Recursion: it's fonts all the way down 2025-09-05 — Go-go-go … I missed EmbedPDF 2025-09-06 — Exposing HTML: The No-JS nudist CSS toggle 2025-09-07 — Predictable, token-based filenames with Eleventy Image 2025-09-12 — Sacrificing knowledge in the name of data 2025-09-14 — Individualism is the flavor AI chatbots can't stomach 2025-09-19 — A stop-gap Drupal module to kill Word Junk in CKEditor 5 2025-09-19 — Thoughtful AI integration beats bolted-on Clippy 2025-09-23 — The power of the pause: How planning beats prompt tuning 2025-09-27 — Embracing px and rem for CSS 2025-09-29 — Developers are becoming context technical writers for AI 2025-10-03 — Context engineering beats prompt tricks for AI agents 2025-10-13 — It's true, short disruptions costs lots of time 2025-10-13 — Output: An HTML-native tag once again saves JS befuddling 2025-10-28 — Introducing a "Work" section 2025-11-04 — Plenty to learn from Fedora's approach to AI code 2025-11-07 — Why AI can't be debugged like traditional software 2025-12-03 — Making sense of Microsoft's many AI Copilots 2025-12-03 — Measuring success beyond the page view 2025-12-04 — Large projects need large communicating 2025-12-05 — Digest videos into sketchnotes through AI 2025-12-26 — URLs are the state management you should use 2026-01-15 — How to measure impact when analytics lie 2026-01-24 — VR Productivity finally almost surpasses physical displays 2026-01-30 — Digital transformation for complex organizations (Parts 1-2) 2026-02-05 — The practitioner's guide to planning digital transformation (Parts 3-4) 2026-02-16 — Your browser utility wants to be a floating palette 2026-02-16 — PDF-A-go-slim: a browser-based PDF optimizer 2026-02-20 — Feedback buttons without JavaScript, using a 1990s web pattern 2026-02-22 — Two-way communication beats another shipped feature 2026-02-25 — Collaborate on any webpage with a bookmarklet and URL state 2026-02-28 — Site search without a search service 2026-03-02 — Semantic search on a static site, no API keys required 2026-03-03 — Blog art that belongs 2026-03-04 — AI coding tools turned my once-a-year hobby project into a daily habit 2026-03-05 — 11ty is dead, long live Build Awesome 2026-03-27 — Content architecture: the delivery problem 2026-03-28 — Comprehension debt, when AI-generated code outpaces human understanding 2026-03-29 — The ladder was always context 2026-03-30 — Why context engineering was always the job 2026-04-04 — Go schema-first and skeleton loading stops being a problem 2026-04-05 — Four gears of AI-assisted development: from coding to context 2026-04-07 — The right answer has to be woven 2026-04-08 — EmDash won't beat WordPress. Drupal just needs to wait 2026-04-08 — How to write one skill for both Claude Code and GitHub Copilot CLI 2026-04-20 — Let AI worry about the code, you worry about the work 2026-04-23 — Why 'reviewed' should be a protected verb 2026-04-29 — Stop converting SVG text to outlines 2026-05-03 — Eye-tracking heatmaps in your browser, no lab needed 2026-05-06 — My daily routine assumes the internet survives the disaster 2026-05-09 — Building a virtual garage for hobby projects 2026-05-12 — A data font, from the inside out 2026-06-09 — CADI: a prescriptive path for slop-free AI in content work 2026-06-15 — 13 words to turn a rumor into AI fact 2026-06-26 — Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon 2026-08-08 — A fresh coat of paint and making information actionable for 24 years 2026-08-09 — We act like startups but skip their hard-won lessons 2026-08-10 — NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT 2026-08-12 — From the roof, eclipse day 2026 2026-10-05 — Sunrise and the Siebengebirge 2026-10-19 — Rehabilitating Johnny Castaway for the browser 2026-10-24 — When one person leaves, a team leaves with them 2025-12-21 — Improving AI chatbots with an editorial handbook from your best content 2025-11-08 — Creating warm, dappled light with CSS and SVG 2014-06-30 — Scaling Drupal e-commerce for 150,000 satellite-connected customers 2019-11-12 — Building a component library adopted across 50+ scientific properties 2021-08-30 — Untangling an 80-link footer into scannable navigation 2020-12-21 — Decoupling content from platforms across 80 properties 2025-08-17 — Reclaiming three weeks of editorial time every month 2025-12-21 — Turning vague content guidelines into measurable AI-ready standards 2025-10-18 — Making disaster economics compelling for global policymakers 2025-07-01 — Recovering platform performance after a cloud migration failure 2026-10-21 — One shared truth for Storybook and Figma 2026-04-22 — Designing analytics infrastructure that measures audience quality, not just traffic 2026-04-20 — Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge
Career bands locate the writing in time; they do not claim that an employer caused a theme.
  1. Better corporate design through information architecture Content architecture: the delivery problem 2017 → 2026 · 8.7 years
  2. What if: A web font for data A data font, from the inside out 2018 → 2026 · 8.1 years
  3. A new site for little reason A simpler, faster site: moving to pure Eleventy v3 2017 → 2025 · 8.1 years
  4. Introducing the Content-Action Model for Web Systems Digital transformation for complex organizations (Parts 1-2) 2018 → 2026 · 8 years

2.0Biographies of a few ideas

Semantically assembled trails

Question: how did a concern change as it moved from a small technical problem to an organizational argument? Each broad lens starts with a few editorial anchors, then passage similarity chooses the entries. A per-year cap keeps a recent publishing burst from swallowing the history; the names and interpretation remain editorial.[7][8]

Information action

Content that exists to make something happen: first for people deciding what to do, later for machines acting on their behalf. Similarity ≥ 0.57.

  1. 2018 The Content-Action Model origin story 0.89
  2. 2018 Introducing the Content-Action Model for Web Systems 0.93
  3. 2018 Inside the Content-Action Model 0.873
  4. 2026 Why context engineering was always the job 0.659

Content as infrastructure

Content models, information architecture and platforms treated as organizational infrastructure. Similarity ≥ 0.68.

  1. 2017 Better corporate design through information architecture 0.818
  2. 2018 Introducing the Content-Action Model for Web Systems 0.814
  3. 2019 Building a component library adopted across 50+ scientific properties 0.718
  4. 2020 Decoupling content from platforms across 80 properties 0.848
  5. 2026 Content architecture: the delivery problem 0.89

Typography and data

Type choices, data fonts and the work of keeping text legible, portable and meaningful. Similarity ≥ 0.5.

  1. 2017 Comparing IBM Plex and Fira Sans 0.579
  2. 2018 What if: A web font for data 0.952
  3. 2026 Stop converting SVG text to outlines 0.501
  4. 2026 A data font, from the inside out 0.952

Rebuilding and preserving a personal site

The publishing stack keeps changing; the longer project is keeping the archive together. Similarity ≥ 0.6.

  1. 2017 A new site for little reason 0.742
  2. 2019 Building a component library adopted across 50+ scientific properties 0.624
  3. 2020 Moving from Panini to Eleventy 0.79
  4. 2025 A simpler, faster site: moving to pure Eleventy v3 0.886
  5. 2026 A fresh coat of paint and making information actionable for 24 years 0.67

Reusable systems at organizational scale

Components begin as technical reuse and become a way to coordinate institutions. Similarity ≥ 0.58.

  1. 2017 Better corporate design through information architecture 0.638
  2. 2018 Faster scientific websites through reusability 0.854
  3. 2019 EMBL-EBI Day: Visual Framework 2.0 outreach 0.888
  4. 2019 Building a component library adopted across 50+ scientific properties 0.85
  5. 2020 Decoupling content from platforms across 80 properties 0.72
  6. 2021 Enabling a more dynamic EMBL online 0.848
  7. 2025 A simpler, faster site: moving to pure Eleventy v3 0.681

3.0When subjects entered the archive

24 recurring topics · 102 entries

Question: when did each subject first appear, and did it become a continuing practice, a short burst or a later return? Each line is a trailing 6-month publication count, ordered by the topic's first appearance. Like Kevin Marks's The Joy of Sparks, the offset, overlapping lines turn small time series into a shared terrain.[12] Every topic is normalized to its own peak, so height compares timing and shape within a row, never volume between rows; the right-hand number is the actual entry total.

Publication activity by recurring primary topic 24 topic sparklines run from 2013 to 2026 and are ordered by first appearance. Each shows a trailing six-month count normalized to its own peak; exact post dates are marked with dots and actual totals appear at right. cloud infrastructure — 3 entries from 2013-03-21 to 2026-05-09; peak 2 in a trailing six-month window ending 2013-06 2013-03-21 — Cutting down on Postfix spam relaying2013-06-12 — Muliple IPs on an Ubuntu EC2 VPC? Yes, please!2026-05-09 — Building a virtual garage for hobby projects cloud infrastructure 3 content strategy — 6 entries from 2013-12-08 to 2025-12-21; peak 4 in a trailing six-month window ending 2018-03 2013-12-08 — A model for better content, better readers, better journalism2018-01-22 — The Content-Action Model origin story2018-01-22 — Introducing the Content-Action Model for Web Systems2018-02-07 — UX, discovery, analysis + the CAM2018-03-29 — Inside the Content-Action Model2025-12-21 — Turning vague content guidelines into measurable AI-ready standards content strategy 6 Drupal — 5 entries from 2014-06-30 to 2026-04-08; peak 3 in a trailing six-month window ending 2025-09 2014-06-30 — Scaling Drupal e-commerce for 150,000 satellite-connected customers2025-07-01 — Recovering platform performance after a cloud migration failure2025-07-10 — Drupal delayed by Azure MySQL2025-09-19 — A stop-gap Drupal module to kill Word Junk in CKEditor 52026-04-08 — EmDash won't beat WordPress. Drupal just needs to wait Drupal 5 data visualization — 2 entries from 2015-01-28 to 2025-10-18; peak 1 in a trailing six-month window ending 2015-01 2015-01-28 — How to install Lyra the graphical visualization environment2025-10-18 — Making disaster economics compelling for global policymakers data visualization 2 information architecture — 5 entries from 2017-07-23 to 2021-08-30; peak 3 in a trailing six-month window ending 2017-10 2017-07-23 — Better corporate design through information architecture2017-09-13 — Fluid IA to enable user discovery, prepare for change2017-10-06 — Five highlights from EuroIA 20172021-08-30 — EMBL.org: Empowering users to navigate a large scientific organization2021-08-30 — Untangling an 80-link footer into scannable navigation information architecture 5 career reflection — 6 entries from 2017-07-25 to 2026-08-08; peak 2 in a trailing six-month window ending 2025-10 2017-07-25 — A new site for little reason2020-02-08 — Publishing since the 2000s2021-12-23 — Something new for 20222025-05-08 — It's been 3.5 years2025-10-28 — Introducing a "Work" section2026-08-08 — A fresh coat of paint and making information actionable for 24 years career reflection 6 productivity — 3 entries from 2017-10-27 to 2026-01-24; peak 2 in a trailing six-month window ending 2026-01 2017-10-27 — 8 Video conferencing tips, dos, don'ts2025-10-13 — It's true, short disruptions costs lots of time2026-01-24 — VR Productivity finally almost surpasses physical displays productivity 3 typography — 5 entries from 2017-11-12 to 2026-05-12; peak 2 in a trailing six-month window ending 2018-03 2017-11-12 — Comparing IBM Plex and Fira Sans2018-03-19 — What if: A web font for data2025-09-04 — Recursion: it's fonts all the way down2026-04-29 — Stop converting SVG text to outlines2026-05-12 — A data font, from the inside out typography 5 design systems — 3 entries from 2018-09-12 to 2026-10-21; peak 1 in a trailing six-month window ending 2018-09 2018-09-12 — Faster scientific websites through reusability2021-12-21 — Enabling a more dynamic EMBL online2026-10-21 — One shared truth for Storybook and Figma design systems 3 Visual Framework — 3 entries from 2019-06-27 to 2019-11-18; peak 3 in a trailing six-month window ending 2019-11 2019-06-27 — EMBL-EBI Day: Visual Framework 2.0 outreach2019-11-12 — Building a component library adopted across 50+ scientific properties2019-11-18 — Building your first page with the Visual Framework 2.0 Visual Framework 3 Eleventy — 6 entries from 2019-10-21 to 2026-03-05; peak 2 in a trailing six-month window ending 2019-11 2019-10-21 — Integrating Eleventy with gulp, upstream JS2019-11-12 — Fractal and Eleventy: Getting static sites closer to the design system2020-07-13 — Moving from Panini to Eleventy2025-08-31 — A simpler, faster site: moving to pure Eleventy v32025-09-07 — Predictable, token-based filenames with Eleventy Image2026-03-05 — 11ty is dead, long live Build Awesome Eleventy 6 content architecture — 3 entries from 2020-12-21 to 2026-04-04; peak 2 in a trailing six-month window ending 2026-04 2020-12-21 — Decoupling content from platforms across 80 properties2026-03-27 — Content architecture: the delivery problem2026-04-04 — Go schema-first and skeleton loading stops being a problem content architecture 3 PDF — 3 entries from 2025-08-11 to 2026-02-16; peak 2 in a trailing six-month window ending 2025-09 2025-08-11 — Making PDFs more viewable2025-09-05 — Go-go-go … I missed EmbedPDF2026-02-16 — PDF-A-go-slim: a browser-based PDF optimizer PDF 3 CSS — 3 entries from 2025-09-06 to 2025-11-08; peak 3 in a trailing six-month window ending 2025-11 2025-09-06 — Exposing HTML: The No-JS nudist CSS toggle2025-09-27 — Embracing px and rem for CSS2025-11-08 — Creating warm, dappled light with CSS and SVG CSS 3 AI — 20 entries from 2025-09-12 to 2026-10-24; peak 12 in a trailing six-month window ending 2026-04 2025-09-12 — Sacrificing knowledge in the name of data2025-09-14 — Individualism is the flavor AI chatbots can't stomach2025-09-19 — Thoughtful AI integration beats bolted-on Clippy2025-09-23 — The power of the pause: How planning beats prompt tuning2025-09-29 — Developers are becoming context technical writers for AI2025-11-04 — Plenty to learn from Fedora's approach to AI code2025-11-07 — Why AI can't be debugged like traditional software2025-12-03 — Making sense of Microsoft's many AI Copilots2025-12-05 — Digest videos into sketchnotes through AI2025-12-21 — Improving AI chatbots with an editorial handbook from your best content2026-03-03 — Blog art that belongs2026-03-04 — AI coding tools turned my once-a-year hobby project into a daily habit2026-03-28 — Comprehension debt, when AI-generated code outpaces human understanding2026-04-05 — Four gears of AI-assisted development: from coding to context2026-04-08 — How to write one skill for both Claude Code and GitHub Copilot CLI2026-04-20 — Let AI worry about the code, you worry about the work2026-04-23 — Why 'reviewed' should be a protected verb2026-06-09 — CADI: a prescriptive path for slop-free AI in content work2026-06-15 — 13 words to turn a rumor into AI fact2026-10-24 — When one person leaves, a team leaves with them AI 20 context engineering — 3 entries from 2025-10-03 to 2026-04-07; peak 2 in a trailing six-month window ending 2026-03 2025-10-03 — Context engineering beats prompt tricks for AI agents2026-03-30 — Why context engineering was always the job2026-04-07 — The right answer has to be woven context engineering 3 web development — 4 entries from 2025-10-13 to 2026-02-25; peak 4 in a trailing six-month window ending 2026-02 2025-10-13 — Output: An HTML-native tag once again saves JS befuddling2025-12-26 — URLs are the state management you should use2026-02-20 — Feedback buttons without JavaScript, using a 1990s web pattern2026-02-25 — Collaborate on any webpage with a bookmarklet and URL state web development 4 analytics — 4 entries from 2025-12-03 to 2026-04-22; peak 4 in a trailing six-month window ending 2026-04 2025-12-03 — Measuring success beyond the page view2026-01-15 — How to measure impact when analytics lie2026-04-20 — Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge2026-04-22 — Designing analytics infrastructure that measures audience quality, not just traffic analytics 4 project management — 2 entries from 2025-12-04 to 2026-02-22; peak 2 in a trailing six-month window ending 2026-02 2025-12-04 — Large projects need large communicating2026-02-22 — Two-way communication beats another shipped feature project management 2 digital transformation — 3 entries from 2026-01-30 to 2026-05-06; peak 3 in a trailing six-month window ending 2026-05 2026-01-30 — Digital transformation for complex organizations (Parts 1-2)2026-02-05 — The practitioner's guide to planning digital transformation (Parts 3-4)2026-05-06 — My daily routine assumes the internet survives the disaster digital transformation 3 retro computing — 4 entries from 2026-02-16 to 2026-10-19; peak 3 in a trailing six-month window ending 2026-10 2026-02-16 — Your browser utility wants to be a floating palette2026-06-26 — Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon2026-08-10 — NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT2026-10-19 — Rehabilitating Johnny Castaway for the browser retro computing 4 search — 2 entries from 2026-02-28 to 2026-03-02; peak 2 in a trailing six-month window ending 2026-03 2026-02-28 — Site search without a search service2026-03-02 — Semantic search on a static site, no API keys required search 2 software engineering — 2 entries from 2026-03-29 to 2026-08-09; peak 2 in a trailing six-month window ending 2026-08 2026-03-29 — The ladder was always context2026-08-09 — We act like startups but skip their hard-won lessons software engineering 2 photography — 2 entries from 2026-08-12 to 2026-10-05; peak 2 in a trailing six-month window ending 2026-10 2026-08-12 — From the roof, eclipse day 20262026-10-05 — Sunrise and the Siebengebirge photography 2
Hover a line or focus its label to read its span and peak. Topics with a single entry are omitted.

BHow to distrust this

These are instruments, not exhibits. Their value is that they undercut the three above: they show how much of the apparent network is recency, where the thresholds were set, and which comparisons are confounded. Read them as the caveats made visible.

4.0Is this really a long-term network?

All 71 displayed semantic links

Question: how much of the apparent network is recurrence, and how much is a recent burst describing the same work? Most links sit near zero years. The rare points on the right are the better raw material for a story about ideas returning.

Semantic similarity by years between linked entries Most of the sixty-six pairs are less than one year apart. Filled points cross a career boundary; open points do not. Faded points are likely article and impact-story companions. Better corporate design through information architecture + Fluid IA to enable user discovery, prepare for change: 0.1 years, similarity 0.64 Better corporate design through information architecture + Content architecture: the delivery problem: 8.7 years, similarity 0.62 Better corporate design through information architecture + EMBL.org: Empowering users to navigate a large scientific organization: 4.1 years, similarity 0.6 A new site for little reason + A simpler, faster site: moving to pure Eleventy v3: 8.1 years, similarity 0.64 The Content-Action Model origin story + Introducing the Content-Action Model for Web Systems: 0 years, similarity 0.9 The Content-Action Model origin story + Inside the Content-Action Model: 0.2 years, similarity 0.77 The Content-Action Model origin story + UX, discovery, analysis + the CAM: 0 years, similarity 0.77 Introducing the Content-Action Model for Web Systems + UX, discovery, analysis + the CAM: 0 years, similarity 0.84 Introducing the Content-Action Model for Web Systems + Inside the Content-Action Model: 0.2 years, similarity 0.81 UX, discovery, analysis + the CAM + Inside the Content-Action Model: 0.1 years, similarity 0.72 Migrating to Zurb Panini 2.0 + Moving from Panini to Eleventy: 2.4 years, similarity 0.6 What if: A web font for data + A data font, from the inside out: 8.1 years, similarity 0.83 Faster scientific websites through reusability + Building a component library adopted across 50+ scientific properties: 1.2 years, similarity 0.68 Faster scientific websites through reusability + EMBL-EBI Day: Visual Framework 2.0 outreach: 0.8 years, similarity 0.64 Faster scientific websites through reusability + Enabling a more dynamic EMBL online: 3.3 years, similarity 0.63 EMBL-EBI Day: Visual Framework 2.0 outreach + Enabling a more dynamic EMBL online: 2.5 years, similarity 0.73 EMBL-EBI Day: Visual Framework 2.0 outreach + Building a component library adopted across 50+ scientific properties: 0.4 years, similarity 0.69 Integrating Eleventy with gulp, upstream JS + Fractal and Eleventy: Getting static sites closer to the design system: 0.1 years, similarity 0.66 Fractal and Eleventy: Getting static sites closer to the design system + A simpler, faster site: moving to pure Eleventy v3: 5.8 years, similarity 0.68 Moving from Panini to Eleventy + A simpler, faster site: moving to pure Eleventy v3: 5.1 years, similarity 0.72 EMBL.org: Empowering users to navigate a large scientific organization + Untangling an 80-link footer into scannable navigation: 0 years, similarity 0.86 Decoupling content from platforms across 80 properties + Enabling a more dynamic EMBL online: 1 years, similarity 0.67 EMBL-EBI Day: Visual Framework 2.0 outreach + Something new for 2022: 2.5 years, similarity 0.61 It's been 3.5 years + A fresh coat of paint and making information actionable for 24 years: 1.3 years, similarity 0.62 Recovering platform performance after a cloud migration failure + Drupal delayed by Azure MySQL: 0 years, similarity 0.78 Making PDFs more viewable + Go-go-go … I missed EmbedPDF: 0.1 years, similarity 0.82 Making PDFs more viewable + PDF-A-go-slim: a browser-based PDF optimizer: 0.5 years, similarity 0.75 Making PDFs more viewable + Your browser utility wants to be a floating palette: 0.5 years, similarity 0.61 Go-go-go … I missed EmbedPDF + PDF-A-go-slim: a browser-based PDF optimizer: 0.4 years, similarity 0.7 Individualism is the flavor AI chatbots can't stomach + Improving AI chatbots with an editorial handbook from your best content: 0.3 years, similarity 0.61 Thoughtful AI integration beats bolted-on Clippy + Improving AI chatbots with an editorial handbook from your best content: 0.3 years, similarity 0.8 Thoughtful AI integration beats bolted-on Clippy + CADI: a prescriptive path for slop-free AI in content work: 0.7 years, similarity 0.7 Thoughtful AI integration beats bolted-on Clippy + Four gears of AI-assisted development: from coding to context: 0.5 years, similarity 0.64 The power of the pause: How planning beats prompt tuning + CADI: a prescriptive path for slop-free AI in content work: 0.7 years, similarity 0.68 The power of the pause: How planning beats prompt tuning + Large projects need large communicating: 0.2 years, similarity 0.63 The power of the pause: How planning beats prompt tuning + Let AI worry about the code, you worry about the work: 0.6 years, similarity 0.63 Developers are becoming context technical writers for AI + Context engineering beats prompt tricks for AI agents: 0 years, similarity 0.75 Developers are becoming context technical writers for AI + Why context engineering was always the job: 0.5 years, similarity 0.7 Developers are becoming context technical writers for AI + The right answer has to be woven: 0.5 years, similarity 0.69 Context engineering beats prompt tricks for AI agents + Why context engineering was always the job: 0.5 years, similarity 0.77 Context engineering beats prompt tricks for AI agents + The right answer has to be woven: 0.5 years, similarity 0.71 Plenty to learn from Fedora's approach to AI code + Why 'reviewed' should be a protected verb: 0.5 years, similarity 0.61 Measuring success beyond the page view + How to measure impact when analytics lie: 0.1 years, similarity 0.89 Measuring success beyond the page view + Designing analytics infrastructure that measures audience quality, not just traffic: 0.4 years, similarity 0.83 How to measure impact when analytics lie + Designing analytics infrastructure that measures audience quality, not just traffic: 0.3 years, similarity 0.9 Digital transformation for complex organizations (Parts 1-2) + The practitioner's guide to planning digital transformation (Parts 3-4): 0 years, similarity 0.85 Digital transformation for complex organizations (Parts 1-2) + Content architecture: the delivery problem: 0.2 years, similarity 0.63 Introducing the Content-Action Model for Web Systems + Digital transformation for complex organizations (Parts 1-2): 8 years, similarity 0.61 The power of the pause: How planning beats prompt tuning + The practitioner's guide to planning digital transformation (Parts 3-4): 0.4 years, similarity 0.61 Your browser utility wants to be a floating palette + PDF-A-go-slim: a browser-based PDF optimizer: 0 years, similarity 0.6 Site search without a search service + Semantic search on a static site, no API keys required: 0 years, similarity 0.76 AI coding tools turned my once-a-year hobby project into a daily habit + Four gears of AI-assisted development: from coding to context: 0.1 years, similarity 0.62 Decoupling content from platforms across 80 properties + Content architecture: the delivery problem: 5.3 years, similarity 0.73 Content architecture: the delivery problem + The right answer has to be woven: 0 years, similarity 0.68 Building a component library adopted across 50+ scientific properties + Content architecture: the delivery problem: 6.4 years, similarity 0.66 Comprehension debt, when AI-generated code outpaces human understanding + Four gears of AI-assisted development: from coding to context: 0 years, similarity 0.66 Thoughtful AI integration beats bolted-on Clippy + Comprehension debt, when AI-generated code outpaces human understanding: 0.5 years, similarity 0.62 The ladder was always context + Why context engineering was always the job: 0 years, similarity 0.74 The ladder was always context + Four gears of AI-assisted development: from coding to context: 0 years, similarity 0.68 The ladder was always context + The right answer has to be woven: 0 years, similarity 0.61 Why context engineering was always the job + The right answer has to be woven: 0 years, similarity 0.81 Four gears of AI-assisted development: from coding to context + Let AI worry about the code, you worry about the work: 0 years, similarity 0.69 Developers are becoming context technical writers for AI + Four gears of AI-assisted development: from coding to context: 0.5 years, similarity 0.66 Let AI worry about the code, you worry about the work + CADI: a prescriptive path for slop-free AI in content work: 0.1 years, similarity 0.61 Making disaster economics compelling for global policymakers + My daily routine assumes the internet survives the disaster: 0.5 years, similarity 0.65 Improving AI chatbots with an editorial handbook from your best content + CADI: a prescriptive path for slop-free AI in content work: 0.5 years, similarity 0.7 Turning vague content guidelines into measurable AI-ready standards + CADI: a prescriptive path for slop-free AI in content work: 0.5 years, similarity 0.7 Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon + NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT: 0.1 years, similarity 0.84 Improving AI chatbots with an editorial handbook from your best content + Turning vague content guidelines into measurable AI-ready standards: 0 years, similarity 0.73 Building a component library adopted across 50+ scientific properties + Decoupling content from platforms across 80 properties: 1.1 years, similarity 0.71 Turning vague content guidelines into measurable AI-ready standards + The right answer has to be woven: 0.3 years, similarity 0.6
Horizontal position is elapsed time; vertical position is model similarity. Filled marks cross a career boundary. Faded marks are likely companion pieces.

5.0Passages the map averaged away

818 chunks from 108 entries

Question: which small echoes disappear when the semantic search index is averaged into one vector per entry? These candidates span at least three years, have no displayed map edge, and contain one passage pair that is substantially closer than the two entries overall. The snippets are prompts for close reading, not proof that the ideas are related.

  1. 2017 Better corporate design through information architecture

    Read "The EMBL Triangle Key: From brand structure to information architecture" Part 3: Implementation # UPDATE 2017-09-13: [We've been working on implementing this model, read the

    0.621 passage 0.565 whole entry
    2020 Decoupling content from platforms across 80 properties

    …d data, VF components provided consistent presentation Syndicated elements : Syndication wasn't limited to content — structural and navigational elements could be shared too: Global footer :

    3 years apart · no direct source link found
  2. 2018 Migrating to Zurb Panini 2.0

    It doesn't seem naming with dots are allowed in partials anymore, so I've called the file criticalmincss.html I also had a page called rss.xml that was ignored by Panini.

    0.617 passage 0.523 whole entry
    2025 A simpler, faster site: moving to pure Eleventy v3

    …s (net −7,183 lines, excluding yarn.lock ) across 190 files — and 127 fewer files (140 deleted, 14 added) PR #12 . Build and tooling Switched to Eleventy v3. Dropped Gulp and Fractal.

    7 years apart · linked directly in the writing
  3. 2020 Decoupling content from platforms across 80 properties

    …with — worked in any platform Instant organization-wide updates : contentHub menu structure update propagated to all 80+ properties automatically (no

    0.608 passage 0.524 whole entry
    2025 Reclaiming three weeks of editorial time every month

    The per-editor average: 50 minutes saved per week. Nearly an hour per person reclaimed for strategic content work instead of fighting the CMS. Why did this actually work?

    5 years apart · no direct source link found
  4. 2020 Publishing since the 2000s

    But in print publishing and online, technology changes have been tremendous — so much so you'd think it was the change.

    0.593 passage 0.437 whole entry
    2026 Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon

    …esktop publishing: Quark 4 on Mac OS 7, PostScript ads that could lock the whole system, the peculiar texture of cooperative multitasking.

    6 years apart · linked directly in the writing
  5. 2026 The right answer has to be woven

    Software engineering. Evans published DDD in 2003, arguing that the hard problem of software is shared understanding of the domain, not the code.

    0.592 passage 0.518 whole entry
    2020 Decoupling content from platforms across 80 properties

    # The key architectural insight: decouple authoring from display, then make integration trivial .

    6 years apart · no direct source link found
  6. 2014 Scaling Drupal e-commerce for 150,000 satellite-connected customers

    Reduced typical page loads from 10-15 origin requests to 1-2 Anonymous traffic : 80%+ served from Varnish cache, sub-second page loads for public content Authenticated workflows : Optimized database

    0.589 passage 0.533 whole entry
    2025 Recovering platform performance after a cloud migration failure

    The database migration was flagged early as high-impact/high-risk, which allowed careful transition planning. We committed to a predictable 3-week release cadence with scope control.

    11 years apart · linked directly in the writing
  7. 2020 Decoupling content from platforms across 80 properties

    …shed once to contentHub, content appeared everywhere automatically Reduced content lag : EMBL.org homepage freshness improved from 3-5 day lag (manual curation) to real-time (automated aggregation)

    0.582 passage 0.449 whole entry
    2025 Recovering platform performance after a cloud migration failure

    Caching strategy became comprehensive. Page cache, render cache, CDN layers. Cache warming for cold paths to prevent the timeout pattern. Tuned image pipelines for Core Web Vitals.

    5 years apart · no direct source link found
  8. 2018 What if: A web font for data

    4. Ink traps # Bringing ink traps to the digital world could help for small text on HiDPI (retina) screens . See the Pen A data font: Ink traps by Ken Hawkins ( @khawkins98 ) on CodePen .

    0.58 passage 0.483 whole entry
    2026 Stop converting SVG text to outlines

    Runs entirely in the browser, nothing uploaded. Converting SVG text to outlines makes it invisible to assistive tech, search, translation, and LLMs.

    8 years apart · no direct source link found

The latest full-build index contains 934 chunks from 164 searchable pages. The corpus map uses 818 chunks belonging to the 108 writing entries shown here.

6.0Themes read against career chapters

Color: post count · percentage: chapter share

Question: which subjects appear in the public writing from each chapter? Darker cells mean more posts on a shared scale, so four posts always read as more than two. The percentage says how prominent that topic was within its chapter. This is context, not a claim of correlation or organizational influence.[2]

Primary topicDRS 6 taggedEMBL-EBI 12 taggedEMBL 15 taggedUNDRR 75 tagged
AI 2000%00%00%2027%
career reflection 600%18%213%34%
content strategy 6117%433%00%11%
Eleventy 600%00%320%34%
Drupal 5117%00%00%45%
information architecture 500%325%213%00%
typography 500%217%00%34%
analytics 400%00%00%45%
retro computing 400%00%00%45%
web development 400%00%00%45%

CWorkbench

Four views kept for stewing, folded away because none of them currently earns a reader's attention. Two show pairs I deliberately cross-linked, so the model discovered nothing; one is a ranking every blog could produce; one is the best-looking thing on the page and needs three hundred words to explain what its angle and radius mean. Nothing here is deleted — a view that cannot be read today may be readable after another year of writing.

Open the workbench — four uncurated views

7.0From argument to evidence

13 article ↔ impact-story pairs

Question: where does the blog turn practice into an argument, and where does the work section give that argument receipts? These are often two accounts of the same work, so the interest is in genre and perspective, not independent discovery.

Connections between articles and impact stories Articles run chronologically along the upper line and impact stories along the lower line. Curves join semantically related entries written in the two genres. writing work How to measure impact when analytics lie ↔ Designing analytics infrastructure that measures audience quality, not just traffic, similarity 0.9EMBL.org: Empowering users to navigate a large scientific organization ↔ Untangling an 80-link footer into scannable navigation, similarity 0.86Measuring success beyond the page view ↔ Designing analytics infrastructure that measures audience quality, not just traffic, similarity 0.83Drupal delayed by Azure MySQL ↔ Recovering platform performance after a cloud migration failure, similarity 0.78Content architecture: the delivery problem ↔ Decoupling content from platforms across 80 properties, similarity 0.73Improving AI chatbots with an editorial handbook from your best content ↔ Turning vague content guidelines into measurable AI-ready standards, similarity 0.73CADI: a prescriptive path for slop-free AI in content work ↔ Turning vague content guidelines into measurable AI-ready standards, similarity 0.7EMBL-EBI Day: Visual Framework 2.0 outreach ↔ Building a component library adopted across 50+ scientific properties, similarity 0.69Faster scientific websites through reusability ↔ Building a component library adopted across 50+ scientific properties, similarity 0.68Enabling a more dynamic EMBL online ↔ Decoupling content from platforms across 80 properties, similarity 0.67Content architecture: the delivery problem ↔ Building a component library adopted across 50+ scientific properties, similarity 0.66My daily routine assumes the internet survives the disaster ↔ Making disaster economics compelling for global policymakers, similarity 0.65The right answer has to be woven ↔ Turning vague content guidelines into measurable AI-ready standards, similarity 0.6 How to measure impact when analytics lie Designing analytics infrastructure that measures audience quality, not just traffic EMBL.org: Empowering users to navigate a large scientific organization Untangling an 80-link footer into scannable navigation Measuring success beyond the page view Designing analytics infrastructure that measures audience quality, not just traffic Drupal delayed by Azure MySQL Recovering platform performance after a cloud migration failure Content architecture: the delivery problem Decoupling content from platforms across 80 properties Improving AI chatbots with an editorial handbook from your best content Turning vague content guidelines into measurable AI-ready standards CADI: a prescriptive path for slop-free AI in content work Turning vague content guidelines into measurable AI-ready standards EMBL-EBI Day: Visual Framework 2.0 outreach Building a component library adopted across 50+ scientific properties Faster scientific websites through reusability Building a component library adopted across 50+ scientific properties Enabling a more dynamic EMBL online Decoupling content from platforms across 80 properties Content architecture: the delivery problem Building a component library adopted across 50+ scientific properties My daily routine assumes the internet survives the disaster Making disaster economics compelling for global policymakers The right answer has to be woven Turning vague content guidelines into measurable AI-ready standards
Circles are articles; diamonds are impact stories. Repeated marks show that one entry can be paired with several accounts.

8.0When themes became active

Each row scaled to its own peak year

Question: did a theme persist, arrive in a burst, or return after an absence? This is closer to a score than a river: every year stays aligned, including the quiet ones, and each row states its total.[2][5]

Topic20132014201520162017201820192020202120222023202420252026
AI 202013: 0 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 0 entries2018: 0 entries2019: 0 entries2020: 0 entries2021: 0 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 10 entries2026: 10 entries
career reflection 62013: 0 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 1 entries2018: 0 entries2019: 0 entries2020: 1 entries2021: 1 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 2 entries2026: 1 entries
content strategy 62013: 1 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 0 entries2018: 4 entries2019: 0 entries2020: 0 entries2021: 0 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 1 entries2026: 0 entries
Eleventy 62013: 0 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 0 entries2018: 0 entries2019: 2 entries2020: 1 entries2021: 0 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 2 entries2026: 1 entries
Drupal 52013: 0 entries2014: 1 entries2015: 0 entries2016: 0 entries2017: 0 entries2018: 0 entries2019: 0 entries2020: 0 entries2021: 0 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 3 entries2026: 1 entries
information architecture 52013: 0 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 3 entries2018: 0 entries2019: 0 entries2020: 0 entries2021: 2 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 0 entries2026: 0 entries
typography 52013: 0 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 1 entries2018: 1 entries2019: 0 entries2020: 0 entries2021: 0 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 1 entries2026: 2 entries
analytics 42013: 0 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 0 entries2018: 0 entries2019: 0 entries2020: 0 entries2021: 0 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 1 entries2026: 3 entries
retro computing 42013: 0 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 0 entries2018: 0 entries2019: 0 entries2020: 0 entries2021: 0 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 0 entries2026: 4 entries
web development 42013: 0 entries2014: 0 entries2015: 0 entries2016: 0 entries2017: 0 entries2018: 0 entries2019: 0 entries2020: 0 entries2021: 0 entries2022: 0 entries2023: 0 entries2024: 0 entries2025: 2 entries2026: 2 entries

9.0The web behind the writing

813 links · 298 hosts

Question: which parts of the wider web does this archive repeatedly use as evidence, infrastructure or cultural context? Ranking by distinct entries prevents one reference-heavy article from winning merely because it links to the same host many times. Raw link counts remain visible.

  1. github.com 31 entries · 153 links
  2. flickr.com 22 entries · 24 links
  3. en.wikipedia.org 19 entries · 29 links
  4. huggingface.co 10 entries · 19 links
  5. twitter.com 9 entries · 26 links
  6. khawkins98.github.io 7 entries · 20 links
  7. web.archive.org 7 entries · 13 links
  8. arxiv.org 6 entries · 21 links
  9. blogs.embl.org 6 entries · 12 links
  10. ebi.ac.uk 6 entries · 9 links
  11. embl.org 6 entries · 7 links
  12. loras.dev 6 entries · 6 links
  13. stable.visual-framework.dev 5 entries · 7 links
  14. medium.com 5 entries · 5 links
  15. visual-framework.github.io 4 entries · 18 links
Ranked by the number of entries containing each host. Image credits and project links are included because they are part of the published article.

Address endings across career chapters

Each host counts once per entry. Darker cells mean more entry–host mentions on a shared scale; percentages show the mix within that chapter. An address ending is not an institutional identity: GitHub is still a .com, and .org does not guarantee nonprofit status.

Address endingDRSEMBL-EBIEMBLUNDRR
.com / .co.*770%3750%2539%15547%
.org / .org.*00%1419%1523%7322%
.edu / .ac.*110%68%23%52%
.gov / .go.*00%23%12%52%
.dev / .io / .ai / .app00%34%1523%4012%
other country-code110%811%23%247%
other suffixes110%45%46%278%

10.0Topic families and two kinds of connection

244 authored · 614 semantic · 121 both

Question: does the model connect subjects in the same way I deliberately connected them? In both diagrams, angle is an editorially assigned topic family. Radius is cross-family reach within that panel: more cross-family connections pull an entry closer to the centre. Curves bundle through an inner family anchor, borrowing the radial tree's visual grammar without claiming ancestry.[11] The semantic panel deliberately replaces the public map's whole-entry averages and three-neighbour cap with passage-pair matches at 0.45, expanding 71 displayed pairs to 614. Gold paths touch the AI family; heavier semantic paths have support in multiple distinct passages.

Radius is cross-family reach. More connections pull a post towards the centre; zero-connected posts remain at the edge. Both panels use the same square-root 0–94 scale so low counts remain distinguishable.

Authored cross-links

Authored cross-links arranged by topic family and year One hundred entries are grouped around the circle by curated topic family. Entries with more cross-family connections in this panel sit nearer the centre. Curves show 244 authored cross-links. Cutting down on Postfix spam relaying ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Muliple IPs on an Ubuntu EC2 VPC? Yes, please! ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link A model for better content, better readers, better journalism ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link UX success story: Doubling conversion rates, sales ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link How to install Lyra the graphical visualization environment ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Better corporate design through information architecture ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link A new site for little reason ↔ Migrating to Zurb Panini 2.0, 1 authored link A new site for little reason ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Fluid IA to enable user discovery, prepare for change ↔ Better corporate design through information architecture, 1 authored link Fluid IA to enable user discovery, prepare for change ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Five highlights from EuroIA 2017 ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link 8 Video conferencing tips, dos, don'ts ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Comparing IBM Plex and Fira Sans ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link The Content-Action Model origin story ↔ Introducing the Content-Action Model for Web Systems, 6 authored links The Content-Action Model origin story ↔ UX, discovery, analysis + the CAM, 2 authored links The Content-Action Model origin story ↔ Inside the Content-Action Model, 2 authored links The Content-Action Model origin story ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Introducing the Content-Action Model for Web Systems ↔ UX, discovery, analysis + the CAM, 6 authored links Introducing the Content-Action Model for Web Systems ↔ Inside the Content-Action Model, 5 authored links Introducing the Content-Action Model for Web Systems ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link UX, discovery, analysis + the CAM ↔ Inside the Content-Action Model, 2 authored links UX, discovery, analysis + the CAM ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Migrating to Zurb Panini 2.0 ↔ A simpler, faster site: moving to pure Eleventy v3, 2 authored links Migrating to Zurb Panini 2.0 ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link What if: A web font for data ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Inside the Content-Action Model ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Faster scientific websites through reusability ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link EMBL-EBI Day: Visual Framework 2.0 outreach ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Integrating Eleventy with gulp, upstream JS ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Fractal and Eleventy: Getting static sites closer to the design system ↔ Integrating Eleventy with gulp, upstream JS, 2 authored links Fractal and Eleventy: Getting static sites closer to the design system ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Building your first page with the Visual Framework 2.0 ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Publishing since the 2000s ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Moving from Panini to Eleventy ↔ Migrating to Zurb Panini 2.0, 1 authored link Moving from Panini to Eleventy ↔ A simpler, faster site: moving to pure Eleventy v3, 2 authored links Moving from Panini to Eleventy ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Lerna monorepos with fewer tags ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Using Nunjucks templates with React ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link EMBL.org: Empowering users to navigate a large scientific organization ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Enabling a more dynamic EMBL online ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link It's been 3.5 years ↔ Something new for 2022, 1 authored link It's been 3.5 years ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Drupal delayed by Azure MySQL ↔ Recovering platform performance after a cloud migration failure, 2 authored links Drupal delayed by Azure MySQL ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Making PDFs more viewable ↔ PDF-A-go-slim: a browser-based PDF optimizer, 3 authored links Making PDFs more viewable ↔ Your browser utility wants to be a floating palette, 1 authored link Making PDFs more viewable ↔ Go-go-go … I missed EmbedPDF, 2 authored links Making PDFs more viewable ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link A simpler, faster site: moving to pure Eleventy v3 ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Recursion: it's fonts all the way down ↔ A simpler, faster site: moving to pure Eleventy v3, 1 authored link Go-go-go … I missed EmbedPDF ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Exposing HTML: The No-JS nudist CSS toggle ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 3 authored links Predictable, token-based filenames with Eleventy Image ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Sacrificing knowledge in the name of data ↔ Individualism is the flavor AI chatbots can't stomach, 2 authored links Sacrificing knowledge in the name of data ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Individualism is the flavor AI chatbots can't stomach ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link A stop-gap Drupal module to kill Word Junk in CKEditor 5 ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Thoughtful AI integration beats bolted-on Clippy ↔ Improving AI chatbots with an editorial handbook from your best content, 1 authored link Thoughtful AI integration beats bolted-on Clippy ↔ CADI: a prescriptive path for slop-free AI in content work, 3 authored links Thoughtful AI integration beats bolted-on Clippy ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link The power of the pause: How planning beats prompt tuning ↔ Sacrificing knowledge in the name of data, 1 authored link The power of the pause: How planning beats prompt tuning ↔ Thoughtful AI integration beats bolted-on Clippy, 1 authored link The power of the pause: How planning beats prompt tuning ↔ CADI: a prescriptive path for slop-free AI in content work, 3 authored links The power of the pause: How planning beats prompt tuning ↔ Improving AI chatbots with an editorial handbook from your best content, 1 authored link The power of the pause: How planning beats prompt tuning ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Embracing px and rem for CSS ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Developers are becoming context technical writers for AI ↔ The power of the pause: How planning beats prompt tuning, 1 authored link Developers are becoming context technical writers for AI ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Context engineering beats prompt tricks for AI agents ↔ The power of the pause: How planning beats prompt tuning, 1 authored link Context engineering beats prompt tricks for AI agents ↔ Thoughtful AI integration beats bolted-on Clippy, 1 authored link Context engineering beats prompt tricks for AI agents ↔ Developers are becoming context technical writers for AI, 1 authored link Context engineering beats prompt tricks for AI agents ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link It's true, short disruptions costs lots of time ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Output: An HTML-native tag once again saves JS befuddling ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Introducing a "Work" section ↔ Recovering platform performance after a cloud migration failure, 1 authored link Introducing a "Work" section ↔ Reclaiming three weeks of editorial time every month, 1 authored link Introducing a "Work" section ↔ Making disaster economics compelling for global policymakers, 1 authored link Introducing a "Work" section ↔ Building a component library adopted across 50+ scientific properties, 1 authored link Introducing a "Work" section ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Plenty to learn from Fedora's approach to AI code ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Why AI can't be debugged like traditional software ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Making sense of Microsoft's many AI Copilots ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Measuring success beyond the page view ↔ Individualism is the flavor AI chatbots can't stomach, 1 authored link Measuring success beyond the page view ↔ How to measure impact when analytics lie, 2 authored links Measuring success beyond the page view ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 2 authored links Large projects need large communicating ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Digest videos into sketchnotes through AI ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link URLs are the state management you should use ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 4 authored links How to measure impact when analytics lie ↔ Individualism is the flavor AI chatbots can't stomach, 1 authored link How to measure impact when analytics lie ↔ Sacrificing knowledge in the name of data, 1 authored link How to measure impact when analytics lie ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 2 authored links VR Productivity finally almost surpasses physical displays ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Digital transformation for complex organizations (Parts 1-2) ↔ Introducing the Content-Action Model for Web Systems, 3 authored links Digital transformation for complex organizations (Parts 1-2) ↔ Measuring success beyond the page view, 1 authored link Digital transformation for complex organizations (Parts 1-2) ↔ Individualism is the flavor AI chatbots can't stomach, 1 authored link Digital transformation for complex organizations (Parts 1-2) ↔ Building a component library adopted across 50+ scientific properties, 2 authored links Digital transformation for complex organizations (Parts 1-2) ↔ Making disaster economics compelling for global policymakers, 2 authored links Digital transformation for complex organizations (Parts 1-2) ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 3 authored links Digital transformation for complex organizations (Parts 1-2) ↔ Reclaiming three weeks of editorial time every month, 1 authored link Digital transformation for complex organizations (Parts 1-2) ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Introducing the Content-Action Model for Web Systems, 1 authored link The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Your browser utility wants to be a floating palette ↔ PDF-A-go-slim: a browser-based PDF optimizer, 3 authored links Your browser utility wants to be a floating palette ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 2 authored links PDF-A-go-slim: a browser-based PDF optimizer ↔ Go-go-go … I missed EmbedPDF, 1 authored link PDF-A-go-slim: a browser-based PDF optimizer ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Two-way communication beats another shipped feature ↔ Reclaiming three weeks of editorial time every month, 1 authored link Two-way communication beats another shipped feature ↔ The power of the pause: How planning beats prompt tuning, 1 authored link Two-way communication beats another shipped feature ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Collaborate on any webpage with a bookmarklet and URL state ↔ URLs are the state management you should use, 2 authored links Collaborate on any webpage with a bookmarklet and URL state ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 2 authored links Collaborate on any webpage with a bookmarklet and URL state ↔ PDF-A-go-slim: a browser-based PDF optimizer, 1 authored link Collaborate on any webpage with a bookmarklet and URL state ↔ Two-way communication beats another shipped feature, 1 authored link Site search without a search service ↔ Semantic search on a static site, no API keys required, 4 authored links Site search without a search service ↔ A simpler, faster site: moving to pure Eleventy v3, 1 authored link Site search without a search service ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Semantic search on a static site, no API keys required ↔ Collaborate on any webpage with a bookmarklet and URL state, 1 authored link Semantic search on a static site, no API keys required ↔ A simpler, faster site: moving to pure Eleventy v3, 1 authored link Semantic search on a static site, no API keys required ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Blog art that belongs ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link AI coding tools turned my once-a-year hobby project into a daily habit ↔ Site search without a search service, 1 authored link AI coding tools turned my once-a-year hobby project into a daily habit ↔ Semantic search on a static site, no API keys required, 1 authored link AI coding tools turned my once-a-year hobby project into a daily habit ↔ Blog art that belongs, 1 authored link AI coding tools turned my once-a-year hobby project into a daily habit ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link 11ty is dead, long live Build Awesome ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Content architecture: the delivery problem ↔ Introducing the Content-Action Model for Web Systems, 1 authored link Content architecture: the delivery problem ↔ Building a component library adopted across 50+ scientific properties, 2 authored links Content architecture: the delivery problem ↔ Better corporate design through information architecture, 1 authored link Content architecture: the delivery problem ↔ Digital transformation for complex organizations (Parts 1-2), 2 authored links Content architecture: the delivery problem ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Comprehension debt, when AI-generated code outpaces human understanding ↔ The power of the pause: How planning beats prompt tuning, 1 authored link Comprehension debt, when AI-generated code outpaces human understanding ↔ AI coding tools turned my once-a-year hobby project into a daily habit, 1 authored link Comprehension debt, when AI-generated code outpaces human understanding ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link The ladder was always context ↔ The power of the pause: How planning beats prompt tuning, 2 authored links The ladder was always context ↔ Developers are becoming context technical writers for AI, 2 authored links The ladder was always context ↔ Comprehension debt, when AI-generated code outpaces human understanding, 3 authored links The ladder was always context ↔ Context engineering beats prompt tricks for AI agents, 1 authored link The ladder was always context ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Why context engineering was always the job ↔ The ladder was always context, 3 authored links Why context engineering was always the job ↔ Comprehension debt, when AI-generated code outpaces human understanding, 3 authored links Why context engineering was always the job ↔ Developers are becoming context technical writers for AI, 2 authored links Why context engineering was always the job ↔ Context engineering beats prompt tricks for AI agents, 2 authored links Why context engineering was always the job ↔ The power of the pause: How planning beats prompt tuning, 3 authored links Why context engineering was always the job ↔ A model for better content, better readers, better journalism, 1 authored link Why context engineering was always the job ↔ Introducing the Content-Action Model for Web Systems, 1 authored link Why context engineering was always the job ↔ Individualism is the flavor AI chatbots can't stomach, 1 authored link Why context engineering was always the job ↔ Content architecture: the delivery problem, 2 authored links Why context engineering was always the job ↔ The right answer has to be woven, 3 authored links Why context engineering was always the job ↔ Thoughtful AI integration beats bolted-on Clippy, 1 authored link Why context engineering was always the job ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Go schema-first and skeleton loading stops being a problem ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Four gears of AI-assisted development: from coding to context ↔ Individualism is the flavor AI chatbots can't stomach, 1 authored link Four gears of AI-assisted development: from coding to context ↔ Thoughtful AI integration beats bolted-on Clippy, 1 authored link Four gears of AI-assisted development: from coding to context ↔ AI coding tools turned my once-a-year hobby project into a daily habit, 2 authored links Four gears of AI-assisted development: from coding to context ↔ Comprehension debt, when AI-generated code outpaces human understanding, 2 authored links Four gears of AI-assisted development: from coding to context ↔ Plenty to learn from Fedora's approach to AI code, 1 authored link Four gears of AI-assisted development: from coding to context ↔ Developers are becoming context technical writers for AI, 3 authored links Four gears of AI-assisted development: from coding to context ↔ The power of the pause: How planning beats prompt tuning, 2 authored links Four gears of AI-assisted development: from coding to context ↔ Improving AI chatbots with an editorial handbook from your best content, 1 authored link Four gears of AI-assisted development: from coding to context ↔ The ladder was always context, 2 authored links Four gears of AI-assisted development: from coding to context ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link The right answer has to be woven ↔ Context engineering beats prompt tricks for AI agents, 2 authored links The right answer has to be woven ↔ Developers are becoming context technical writers for AI, 2 authored links The right answer has to be woven ↔ Content architecture: the delivery problem, 1 authored link The right answer has to be woven ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link EmDash won't beat WordPress. Drupal just needs to wait ↔ Content architecture: the delivery problem, 1 authored link EmDash won't beat WordPress. Drupal just needs to wait ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link How to write one skill for both Claude Code and GitHub Copilot CLI ↔ Four gears of AI-assisted development: from coding to context, 1 authored link How to write one skill for both Claude Code and GitHub Copilot CLI ↔ Why context engineering was always the job, 1 authored link How to write one skill for both Claude Code and GitHub Copilot CLI ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Let AI worry about the code, you worry about the work ↔ Four gears of AI-assisted development: from coding to context, 1 authored link Let AI worry about the code, you worry about the work ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 2 authored links Let AI worry about the code, you worry about the work ↔ Why context engineering was always the job, 1 authored link Let AI worry about the code, you worry about the work ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Why 'reviewed' should be a protected verb ↔ Plenty to learn from Fedora's approach to AI code, 1 authored link Why 'reviewed' should be a protected verb ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Stop converting SVG text to outlines ↔ Your browser utility wants to be a floating palette, 1 authored link Stop converting SVG text to outlines ↔ Collaborate on any webpage with a bookmarklet and URL state, 1 authored link Stop converting SVG text to outlines ↔ PDF-A-go-slim: a browser-based PDF optimizer, 1 authored link Stop converting SVG text to outlines ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Eye-tracking heatmaps in your browser, no lab needed ↔ Stop converting SVG text to outlines, 2 authored links Eye-tracking heatmaps in your browser, no lab needed ↔ PDF-A-go-slim: a browser-based PDF optimizer, 1 authored link Eye-tracking heatmaps in your browser, no lab needed ↔ Your browser utility wants to be a floating palette, 1 authored link Eye-tracking heatmaps in your browser, no lab needed ↔ Semantic search on a static site, no API keys required, 1 authored link Eye-tracking heatmaps in your browser, no lab needed ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link My daily routine assumes the internet survives the disaster ↔ Making disaster economics compelling for global policymakers, 1 authored link My daily routine assumes the internet survives the disaster ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Building a virtual garage for hobby projects ↔ Collaborate on any webpage with a bookmarklet and URL state, 1 authored link Building a virtual garage for hobby projects ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link A data font, from the inside out ↔ What if: A web font for data, 3 authored links A data font, from the inside out ↔ Comparing IBM Plex and Fira Sans, 1 authored link A data font, from the inside out ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link CADI: a prescriptive path for slop-free AI in content work ↔ Improving AI chatbots with an editorial handbook from your best content, 5 authored links CADI: a prescriptive path for slop-free AI in content work ↔ Turning vague content guidelines into measurable AI-ready standards, 1 authored link CADI: a prescriptive path for slop-free AI in content work ↔ Why 'reviewed' should be a protected verb, 1 authored link CADI: a prescriptive path for slop-free AI in content work ↔ Why context engineering was always the job, 1 authored link CADI: a prescriptive path for slop-free AI in content work ↔ Four gears of AI-assisted development: from coding to context, 1 authored link CADI: a prescriptive path for slop-free AI in content work ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link 13 words to turn a rumor into AI fact ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon ↔ Publishing since the 2000s, 1 authored link Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon ↔ Your browser utility wants to be a floating palette, 1 authored link Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon ↔ Let AI worry about the code, you worry about the work, 1 authored link Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link A fresh coat of paint and making information actionable for 24 years ↔ What if: A web font for data, 1 authored link We act like startups but skip their hard-won lessons ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT ↔ Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon, 2 authored links NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT ↔ Let AI worry about the code, you worry about the work, 1 authored link NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link From the roof, eclipse day 2026 ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Sunrise and the Siebengebirge ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Rehabilitating Johnny Castaway for the browser ↔ NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT, 1 authored link Rehabilitating Johnny Castaway for the browser ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link When one person leaves, a team leaves with them ↔ The power of the pause: How planning beats prompt tuning, 1 authored link When one person leaves, a team leaves with them ↔ Developers are becoming context technical writers for AI, 1 authored link When one person leaves, a team leaves with them ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Improving AI chatbots with an editorial handbook from your best content ↔ Turning vague content guidelines into measurable AI-ready standards, 2 authored links Improving AI chatbots with an editorial handbook from your best content ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Creating warm, dappled light with CSS and SVG ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Scaling Drupal e-commerce for 150,000 satellite-connected customers ↔ UX success story: Doubling conversion rates, sales, 2 authored links Scaling Drupal e-commerce for 150,000 satellite-connected customers ↔ Recovering platform performance after a cloud migration failure, 2 authored links Scaling Drupal e-commerce for 150,000 satellite-connected customers ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Building a component library adopted across 50+ scientific properties ↔ Fractal and Eleventy: Getting static sites closer to the design system, 1 authored link Building a component library adopted across 50+ scientific properties ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Untangling an 80-link footer into scannable navigation ↔ EMBL.org: Empowering users to navigate a large scientific organization, 1 authored link Untangling an 80-link footer into scannable navigation ↔ Building a component library adopted across 50+ scientific properties, 1 authored link Untangling an 80-link footer into scannable navigation ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Decoupling content from platforms across 80 properties ↔ Building a component library adopted across 50+ scientific properties, 2 authored links Decoupling content from platforms across 80 properties ↔ Enabling a more dynamic EMBL online, 1 authored link Decoupling content from platforms across 80 properties ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Reclaiming three weeks of editorial time every month ↔ Recovering platform performance after a cloud migration failure, 3 authored links Reclaiming three weeks of editorial time every month ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Turning vague content guidelines into measurable AI-ready standards ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Making disaster economics compelling for global policymakers ↔ Recovering platform performance after a cloud migration failure, 2 authored links Making disaster economics compelling for global policymakers ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Recovering platform performance after a cloud migration failure ↔ Thoughtful AI integration beats bolted-on Clippy, 1 authored link Recovering platform performance after a cloud migration failure ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link One shared truth for Storybook and Figma ↔ Content architecture: the delivery problem, 1 authored link One shared truth for Storybook and Figma ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 1 authored link One shared truth for Storybook and Figma ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Designing analytics infrastructure that measures audience quality, not just traffic ↔ How to measure impact when analytics lie, 2 authored links Designing analytics infrastructure that measures audience quality, not just traffic ↔ Measuring success beyond the page view, 1 authored link Designing analytics infrastructure that measures audience quality, not just traffic ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 1 authored link Designing analytics infrastructure that measures audience quality, not just traffic ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 authored link 2013-03-21 — Cutting down on Postfix spam relaying — cloud infrastructure in Platforms — 1 cross-family connection in this panel 2013-06-12 — Muliple IPs on an Ubuntu EC2 VPC? Yes, please! — cloud infrastructure in Platforms — 1 cross-family connection in this panel 2013-12-08 — A model for better content, better readers, better journalism — content strategy in Content — 2 cross-family connections in this panel 2014-04-07 — UX success story: Doubling conversion rates, sales — UX design in IA / UX — 2 cross-family connections in this panel 2015-01-28 — How to install Lyra the graphical visualization environment — data visualization in Evidence — 1 cross-family connection in this panel 2017-07-23 — Better corporate design through information architecture — information architecture in IA / UX — 2 cross-family connections in this panel 2017-07-25 — A new site for little reason — career reflection in Personal — 2 cross-family connections in this panel 2017-09-13 — Fluid IA to enable user discovery, prepare for change — information architecture in IA / UX — 1 cross-family connection in this panel 2017-10-06 — Five highlights from EuroIA 2017 — information architecture in IA / UX — 1 cross-family connection in this panel 2017-10-27 — 8 Video conferencing tips, dos, don'ts — productivity in Transformation — 1 cross-family connection in this panel 2017-11-12 — Comparing IBM Plex and Fira Sans — typography in Typography — 1 cross-family connection in this panel 2018-01-22 — The Content-Action Model origin story — content strategy in Content — 1 cross-family connection in this panel 2018-01-22 — Introducing the Content-Action Model for Web Systems — content strategy in Content — 4 cross-family connections in this panel 2018-02-07 — UX, discovery, analysis + the CAM — content strategy in Content — 1 cross-family connection in this panel 2018-02-10 — Migrating to Zurb Panini 2.0 — static sites in Publishing — 1 cross-family connection in this panel 2018-03-19 — What if: A web font for data — typography in Typography — 2 cross-family connections in this panel 2018-03-29 — Inside the Content-Action Model — content strategy in Content — 1 cross-family connection in this panel 2018-09-12 — Faster scientific websites through reusability — design systems in Design systems — 1 cross-family connection in this panel 2019-06-27 — EMBL-EBI Day: Visual Framework 2.0 outreach — Visual Framework in Design systems — 1 cross-family connection in this panel 2019-10-21 — Integrating Eleventy with gulp, upstream JS — Eleventy in Publishing — 0 cross-family connections in this panel 2019-11-12 — Fractal and Eleventy: Getting static sites closer to the design system — Eleventy in Publishing — 1 cross-family connection in this panel 2019-11-18 — Building your first page with the Visual Framework 2.0 — Visual Framework in Design systems — 1 cross-family connection in this panel 2020-02-08 — Publishing since the 2000s — career reflection in Personal — 1 cross-family connection in this panel 2020-07-13 — Moving from Panini to Eleventy — Eleventy in Publishing — 0 cross-family connections in this panel 2020-11-11 — Lerna monorepos with fewer tags — developer tools in Making — 1 cross-family connection in this panel 2020-12-12 — Using Nunjucks templates with React — JavaScript in Making — 1 cross-family connection in this panel 2021-08-30 — EMBL.org: Empowering users to navigate a large scientific organization — information architecture in IA / UX — 1 cross-family connection in this panel 2021-12-21 — Enabling a more dynamic EMBL online — design systems in Design systems — 2 cross-family connections in this panel 2021-12-23 — Something new for 2022 — career reflection in Personal — 0 cross-family connections in this panel 2025-05-08 — It's been 3.5 years — career reflection in Personal — 1 cross-family connection in this panel 2025-07-10 — Drupal delayed by Azure MySQL — Drupal in Platforms — 1 cross-family connection in this panel 2025-08-11 — Making PDFs more viewable — PDF in Making — 2 cross-family connections in this panel 2025-08-31 — A simpler, faster site: moving to pure Eleventy v3 — Eleventy in Publishing — 3 cross-family connections in this panel 2025-09-04 — Recursion: it's fonts all the way down — typography in Typography — 1 cross-family connection in this panel 2025-09-05 — Go-go-go … I missed EmbedPDF — PDF in Making — 1 cross-family connection in this panel 2025-09-06 — Exposing HTML: The No-JS nudist CSS toggle — CSS in Design systems — 1 cross-family connection in this panel 2025-09-07 — Predictable, token-based filenames with Eleventy Image — Eleventy in Publishing — 0 cross-family connections in this panel 2025-09-12 — Sacrificing knowledge in the name of data — AI in AI — 2 cross-family connections in this panel 2025-09-14 — Individualism is the flavor AI chatbots can't stomach — AI in AI — 4 cross-family connections in this panel 2025-09-19 — A stop-gap Drupal module to kill Word Junk in CKEditor 5 — Drupal in Platforms — 1 cross-family connection in this panel 2025-09-19 — Thoughtful AI integration beats bolted-on Clippy — AI in AI — 2 cross-family connections in this panel 2025-09-23 — The power of the pause: How planning beats prompt tuning — AI in AI — 3 cross-family connections in this panel 2025-09-27 — Embracing px and rem for CSS — CSS in Design systems — 1 cross-family connection in this panel 2025-09-29 — Developers are becoming context technical writers for AI — AI in AI — 2 cross-family connections in this panel 2025-10-03 — Context engineering beats prompt tricks for AI agents — context engineering in AI — 2 cross-family connections in this panel 2025-10-13 — It's true, short disruptions costs lots of time — productivity in Transformation — 1 cross-family connection in this panel 2025-10-13 — Output: An HTML-native tag once again saves JS befuddling — web development in Publishing — 0 cross-family connections in this panel 2025-10-28 — Introducing a "Work" section — career reflection in Personal — 5 cross-family connections in this panel 2025-11-04 — Plenty to learn from Fedora's approach to AI code — AI in AI — 1 cross-family connection in this panel 2025-11-07 — Why AI can't be debugged like traditional software — AI in AI — 1 cross-family connection in this panel 2025-12-03 — Making sense of Microsoft's many AI Copilots — AI in AI — 1 cross-family connection in this panel 2025-12-03 — Measuring success beyond the page view — analytics in Evidence — 3 cross-family connections in this panel 2025-12-04 — Large projects need large communicating — project management in Transformation — 1 cross-family connection in this panel 2025-12-05 — Digest videos into sketchnotes through AI — AI in AI — 1 cross-family connection in this panel 2025-12-26 — URLs are the state management you should use — web development in Publishing — 0 cross-family connections in this panel 2026-01-15 — How to measure impact when analytics lie — analytics in Evidence — 3 cross-family connections in this panel 2026-01-24 — VR Productivity finally almost surpasses physical displays — productivity in Transformation — 1 cross-family connection in this panel 2026-01-30 — Digital transformation for complex organizations (Parts 1-2) — digital transformation in Transformation — 8 cross-family connections in this panel 2026-02-05 — The practitioner's guide to planning digital transformation (Parts 3-4) — digital transformation in Transformation — 2 cross-family connections in this panel 2026-02-16 — Your browser utility wants to be a floating palette — retro computing in Personal — 5 cross-family connections in this panel 2026-02-16 — PDF-A-go-slim: a browser-based PDF optimizer — PDF in Making — 4 cross-family connections in this panel 2026-02-20 — Feedback buttons without JavaScript, using a 1990s web pattern — web development in Publishing — 94 cross-family connections in this panel 2026-02-22 — Two-way communication beats another shipped feature — project management in Transformation — 4 cross-family connections in this panel 2026-02-25 — Collaborate on any webpage with a bookmarklet and URL state — web development in Publishing — 5 cross-family connections in this panel 2026-02-28 — Site search without a search service — search in Evidence — 3 cross-family connections in this panel 2026-03-02 — Semantic search on a static site, no API keys required — search in Evidence — 5 cross-family connections in this panel 2026-03-03 — Blog art that belongs — AI in AI — 1 cross-family connection in this panel 2026-03-04 — AI coding tools turned my once-a-year hobby project into a daily habit — AI in AI — 3 cross-family connections in this panel 2026-03-05 — 11ty is dead, long live Build Awesome — Eleventy in Publishing — 0 cross-family connections in this panel 2026-03-27 — Content architecture: the delivery problem — content architecture in Content — 8 cross-family connections in this panel 2026-03-28 — Comprehension debt, when AI-generated code outpaces human understanding — AI in AI — 2 cross-family connections in this panel 2026-03-29 — The ladder was always context — software engineering in Making — 7 cross-family connections in this panel 2026-03-30 — Why context engineering was always the job — context engineering in AI — 5 cross-family connections in this panel 2026-04-04 — Go schema-first and skeleton loading stops being a problem — content architecture in Content — 1 cross-family connection in this panel 2026-04-05 — Four gears of AI-assisted development: from coding to context — AI in AI — 2 cross-family connections in this panel 2026-04-07 — The right answer has to be woven — context engineering in AI — 2 cross-family connections in this panel 2026-04-08 — EmDash won't beat WordPress. Drupal just needs to wait — Drupal in Platforms — 2 cross-family connections in this panel 2026-04-08 — How to write one skill for both Claude Code and GitHub Copilot CLI — AI in AI — 1 cross-family connection in this panel 2026-04-20 — Let AI worry about the code, you worry about the work — AI in AI — 4 cross-family connections in this panel 2026-04-23 — Why 'reviewed' should be a protected verb — AI in AI — 1 cross-family connection in this panel 2026-04-29 — Stop converting SVG text to outlines — typography in Typography — 5 cross-family connections in this panel 2026-05-03 — Eye-tracking heatmaps in your browser, no lab needed — open source in Making — 4 cross-family connections in this panel 2026-05-06 — My daily routine assumes the internet survives the disaster — digital transformation in Transformation — 2 cross-family connections in this panel 2026-05-09 — Building a virtual garage for hobby projects — cloud infrastructure in Platforms — 2 cross-family connections in this panel 2026-05-12 — A data font, from the inside out — typography in Typography — 1 cross-family connection in this panel 2026-06-09 — CADI: a prescriptive path for slop-free AI in content work — AI in AI — 2 cross-family connections in this panel 2026-06-15 — 13 words to turn a rumor into AI fact — AI in AI — 1 cross-family connection in this panel 2026-06-26 — Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon — retro computing in Personal — 2 cross-family connections in this panel 2026-08-08 — A fresh coat of paint and making information actionable for 24 years — career reflection in Personal — 1 cross-family connection in this panel 2026-08-09 — We act like startups but skip their hard-won lessons — software engineering in Making — 1 cross-family connection in this panel 2026-08-10 — NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT — retro computing in Personal — 2 cross-family connections in this panel 2026-08-12 — From the roof, eclipse day 2026 — photography in Other — 1 cross-family connection in this panel 2026-10-05 — Sunrise and the Siebengebirge — photography in Other — 1 cross-family connection in this panel 2026-10-19 — Rehabilitating Johnny Castaway for the browser — retro computing in Personal — 1 cross-family connection in this panel 2026-10-24 — When one person leaves, a team leaves with them — AI in AI — 1 cross-family connection in this panel 2025-12-21 — Improving AI chatbots with an editorial handbook from your best content — AI in AI — 2 cross-family connections in this panel 2025-11-08 — Creating warm, dappled light with CSS and SVG — CSS in Design systems — 1 cross-family connection in this panel 2014-06-30 — Scaling Drupal e-commerce for 150,000 satellite-connected customers — Drupal in Platforms — 2 cross-family connections in this panel 2019-11-12 — Building a component library adopted across 50+ scientific properties — Visual Framework in Design systems — 7 cross-family connections in this panel 2021-08-30 — Untangling an 80-link footer into scannable navigation — information architecture in IA / UX — 2 cross-family connections in this panel 2020-12-21 — Decoupling content from platforms across 80 properties — content architecture in Content — 3 cross-family connections in this panel 2025-08-17 — Reclaiming three weeks of editorial time every month — editorial workflow in Content — 5 cross-family connections in this panel 2025-12-21 — Turning vague content guidelines into measurable AI-ready standards — content strategy in Content — 3 cross-family connections in this panel 2025-10-18 — Making disaster economics compelling for global policymakers — data visualization in Evidence — 5 cross-family connections in this panel 2025-07-01 — Recovering platform performance after a cloud migration failure — Drupal in Platforms — 5 cross-family connections in this panel 2026-10-21 — One shared truth for Storybook and Figma — design systems in Design systems — 3 cross-family connections in this panel 2026-04-22 — Designing analytics infrastructure that measures audience quality, not just traffic — analytics in Evidence — 1 cross-family connection in this panel 2026-04-20 — Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge — analytics in Evidence — 3 cross-family connections in this panel AI — 23 entriesAIContent — 10 entriesContentIA / UX — 6 entriesIA / UXPublishing — 11 entriesPublishingDesign systems — 9 entriesDesign systemsTypography — 5 entriesTypographyPlatforms — 8 entriesPlatformsEvidence — 8 entriesEvidenceTransformation — 8 entriesTransformationMaking — 8 entriesMakingPersonal — 10 entriesPersonalOther — 2 entriesOther
244 pairs; 159 cross a topic-family boundary.

Passage-supported neighbours

Passage-supported neighbours arranged by topic family and year One hundred entries are grouped around the circle by curated topic family. Entries with more cross-family connections in this panel sit nearer the centre. Curves show 614 passage-supported neighbours. A model for better content, better readers, better journalism ↔ Publishing since the 2000s, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.516 A model for better content, better readers, better journalism ↔ Individualism is the flavor AI chatbots can't stomach, 1 matching passage pair across at least 1 passage on each side, best similarity 0.517 A model for better content, better readers, better journalism ↔ Digital transformation for complex organizations (Parts 1-2), 4 matching passage pairs across at least 2 passages on each side, best similarity 0.531 A model for better content, better readers, better journalism ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 1 matching passage pair across at least 1 passage on each side, best similarity 0.491 A model for better content, better readers, better journalism ↔ Content architecture: the delivery problem, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.532 A model for better content, better readers, better journalism ↔ CADI: a prescriptive path for slop-free AI in content work, 1 matching passage pair across at least 1 passage on each side, best similarity 0.467 A model for better content, better readers, better journalism ↔ 13 words to turn a rumor into AI fact, 1 matching passage pair across at least 1 passage on each side, best similarity 0.451 A model for better content, better readers, better journalism ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.496 A model for better content, better readers, better journalism ↔ Reclaiming three weeks of editorial time every month, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.479 UX success story: Doubling conversion rates, sales ↔ Individualism is the flavor AI chatbots can't stomach, 1 matching passage pair across at least 1 passage on each side, best similarity 0.481 UX success story: Doubling conversion rates, sales ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 13 matching passage pairs across at least 3 passages on each side, best similarity 0.585 Better corporate design through information architecture ↔ Fluid IA to enable user discovery, prepare for change, 9 matching passage pairs across at least 3 passages on each side, best similarity 0.614 Better corporate design through information architecture ↔ Five highlights from EuroIA 2017, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.524 Better corporate design through information architecture ↔ Introducing the Content-Action Model for Web Systems, 12 matching passage pairs across at least 3 passages on each side, best similarity 0.586 Better corporate design through information architecture ↔ Something new for 2022, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.562 Better corporate design through information architecture ↔ A simpler, faster site: moving to pure Eleventy v3, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.475 Better corporate design through information architecture ↔ Digital transformation for complex organizations (Parts 1-2), 14 matching passage pairs across at least 3 passages on each side, best similarity 0.568 Better corporate design through information architecture ↔ Content architecture: the delivery problem, 40 matching passage pairs across at least 3 passages on each side, best similarity 0.664 Better corporate design through information architecture ↔ The right answer has to be woven, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.508 Better corporate design through information architecture ↔ A fresh coat of paint and making information actionable for 24 years, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.497 Better corporate design through information architecture ↔ Building a component library adopted across 50+ scientific properties, 14 matching passage pairs across at least 3 passages on each side, best similarity 0.617 Better corporate design through information architecture ↔ Untangling an 80-link footer into scannable navigation, 19 matching passage pairs across at least 3 passages on each side, best similarity 0.571 Better corporate design through information architecture ↔ Decoupling content from platforms across 80 properties, 25 matching passage pairs across at least 3 passages on each side, best similarity 0.621 Better corporate design through information architecture ↔ One shared truth for Storybook and Figma, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.456 A new site for little reason ↔ Migrating to Zurb Panini 2.0, 1 matching passage pair across at least 1 passage on each side, best similarity 0.461 A new site for little reason ↔ Moving from Panini to Eleventy, 1 matching passage pair across at least 1 passage on each side, best similarity 0.488 A new site for little reason ↔ It's been 3.5 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.527 A new site for little reason ↔ A simpler, faster site: moving to pure Eleventy v3, 1 matching passage pair across at least 1 passage on each side, best similarity 0.561 A new site for little reason ↔ EmDash won't beat WordPress. Drupal just needs to wait, 1 matching passage pair across at least 1 passage on each side, best similarity 0.474 A new site for little reason ↔ Building a component library adopted across 50+ scientific properties, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.509 A new site for little reason ↔ Recovering platform performance after a cloud migration failure, 1 matching passage pair across at least 1 passage on each side, best similarity 0.483 Fluid IA to enable user discovery, prepare for change ↔ Five highlights from EuroIA 2017, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.504 Fluid IA to enable user discovery, prepare for change ↔ Introducing the Content-Action Model for Web Systems, 7 matching passage pairs across at least 2 passages on each side, best similarity 0.555 Fluid IA to enable user discovery, prepare for change ↔ Inside the Content-Action Model, 1 matching passage pair across at least 1 passage on each side, best similarity 0.462 Fluid IA to enable user discovery, prepare for change ↔ A simpler, faster site: moving to pure Eleventy v3, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.457 Fluid IA to enable user discovery, prepare for change ↔ Large projects need large communicating, 1 matching passage pair across at least 1 passage on each side, best similarity 0.465 Fluid IA to enable user discovery, prepare for change ↔ Digital transformation for complex organizations (Parts 1-2), 9 matching passage pairs across at least 3 passages on each side, best similarity 0.5 Fluid IA to enable user discovery, prepare for change ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 1 matching passage pair across at least 1 passage on each side, best similarity 0.466 Fluid IA to enable user discovery, prepare for change ↔ Content architecture: the delivery problem, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.541 Fluid IA to enable user discovery, prepare for change ↔ Why context engineering was always the job, 1 matching passage pair across at least 1 passage on each side, best similarity 0.485 Fluid IA to enable user discovery, prepare for change ↔ The right answer has to be woven, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.52 Fluid IA to enable user discovery, prepare for change ↔ CADI: a prescriptive path for slop-free AI in content work, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.484 Fluid IA to enable user discovery, prepare for change ↔ A fresh coat of paint and making information actionable for 24 years, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.453 Fluid IA to enable user discovery, prepare for change ↔ Building a component library adopted across 50+ scientific properties, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.564 Fluid IA to enable user discovery, prepare for change ↔ Untangling an 80-link footer into scannable navigation, 13 matching passage pairs across at least 3 passages on each side, best similarity 0.569 Fluid IA to enable user discovery, prepare for change ↔ Decoupling content from platforms across 80 properties, 9 matching passage pairs across at least 3 passages on each side, best similarity 0.566 Fluid IA to enable user discovery, prepare for change ↔ Turning vague content guidelines into measurable AI-ready standards, 1 matching passage pair across at least 1 passage on each side, best similarity 0.485 Five highlights from EuroIA 2017 ↔ Introducing the Content-Action Model for Web Systems, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.56 Five highlights from EuroIA 2017 ↔ Something new for 2022, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.51 Five highlights from EuroIA 2017 ↔ It's been 3.5 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.496 Five highlights from EuroIA 2017 ↔ Digital transformation for complex organizations (Parts 1-2), 12 matching passage pairs across at least 3 passages on each side, best similarity 0.5 Five highlights from EuroIA 2017 ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 2 matching passage pairs across at least 1 passage on each side, best similarity 0.458 Five highlights from EuroIA 2017 ↔ Content architecture: the delivery problem, 14 matching passage pairs across at least 3 passages on each side, best similarity 0.535 Five highlights from EuroIA 2017 ↔ The ladder was always context, 1 matching passage pair across at least 1 passage on each side, best similarity 0.46 Five highlights from EuroIA 2017 ↔ Why context engineering was always the job, 12 matching passage pairs across at least 3 passages on each side, best similarity 0.529 Five highlights from EuroIA 2017 ↔ Four gears of AI-assisted development: from coding to context, 1 matching passage pair across at least 1 passage on each side, best similarity 0.48 Five highlights from EuroIA 2017 ↔ The right answer has to be woven, 13 matching passage pairs across at least 2 passages on each side, best similarity 0.562 Five highlights from EuroIA 2017 ↔ EmDash won't beat WordPress. Drupal just needs to wait, 1 matching passage pair across at least 1 passage on each side, best similarity 0.483 Five highlights from EuroIA 2017 ↔ CADI: a prescriptive path for slop-free AI in content work, 5 matching passage pairs across at least 3 passages on each side, best similarity 0.489 Five highlights from EuroIA 2017 ↔ Building a component library adopted across 50+ scientific properties, 11 matching passage pairs across at least 3 passages on each side, best similarity 0.516 Five highlights from EuroIA 2017 ↔ Reclaiming three weeks of editorial time every month, 1 matching passage pair across at least 1 passage on each side, best similarity 0.469 Five highlights from EuroIA 2017 ↔ One shared truth for Storybook and Figma, 1 matching passage pair across at least 1 passage on each side, best similarity 0.48 8 Video conferencing tips, dos, don'ts ↔ Introducing the Content-Action Model for Web Systems, 1 matching passage pair across at least 1 passage on each side, best similarity 0.478 8 Video conferencing tips, dos, don'ts ↔ UX, discovery, analysis + the CAM, 1 matching passage pair across at least 1 passage on each side, best similarity 0.473 8 Video conferencing tips, dos, don'ts ↔ VR Productivity finally almost surpasses physical displays, 6 matching passage pairs across at least 3 passages on each side, best similarity 0.487 Comparing IBM Plex and Fira Sans ↔ What if: A web font for data, 11 matching passage pairs across at least 3 passages on each side, best similarity 0.546 Comparing IBM Plex and Fira Sans ↔ A data font, from the inside out, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.568 The Content-Action Model origin story ↔ Introducing the Content-Action Model for Web Systems, 21 matching passage pairs across at least 2 passages on each side, best similarity 0.821 The Content-Action Model origin story ↔ UX, discovery, analysis + the CAM, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.754 The Content-Action Model origin story ↔ Inside the Content-Action Model, 8 matching passage pairs across at least 2 passages on each side, best similarity 0.705 The Content-Action Model origin story ↔ A simpler, faster site: moving to pure Eleventy v3, 1 matching passage pair across at least 1 passage on each side, best similarity 0.458 The Content-Action Model origin story ↔ Digital transformation for complex organizations (Parts 1-2), 8 matching passage pairs across at least 2 passages on each side, best similarity 0.525 The Content-Action Model origin story ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 2 matching passage pairs across at least 1 passage on each side, best similarity 0.472 The Content-Action Model origin story ↔ Content architecture: the delivery problem, 24 matching passage pairs across at least 2 passages on each side, best similarity 0.55 The Content-Action Model origin story ↔ Why context engineering was always the job, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.469 The Content-Action Model origin story ↔ The right answer has to be woven, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.472 The Content-Action Model origin story ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.454 The Content-Action Model origin story ↔ Decoupling content from platforms across 80 properties, 7 matching passage pairs across at least 1 passage on each side, best similarity 0.481 The Content-Action Model origin story ↔ Turning vague content guidelines into measurable AI-ready standards, 1 matching passage pair across at least 1 passage on each side, best similarity 0.493 The Content-Action Model origin story ↔ Recovering platform performance after a cloud migration failure, 1 matching passage pair across at least 1 passage on each side, best similarity 0.457 The Content-Action Model origin story ↔ One shared truth for Storybook and Figma, 1 matching passage pair across at least 1 passage on each side, best similarity 0.51 Introducing the Content-Action Model for Web Systems ↔ UX, discovery, analysis + the CAM, 27 matching passage pairs across at least 3 passages on each side, best similarity 0.788 Introducing the Content-Action Model for Web Systems ↔ Inside the Content-Action Model, 44 matching passage pairs across at least 4 passages on each side, best similarity 0.727 Introducing the Content-Action Model for Web Systems ↔ Something new for 2022, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.483 Introducing the Content-Action Model for Web Systems ↔ It's been 3.5 years, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.5 Introducing the Content-Action Model for Web Systems ↔ A simpler, faster site: moving to pure Eleventy v3, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.492 Introducing the Content-Action Model for Web Systems ↔ Individualism is the flavor AI chatbots can't stomach, 6 matching passage pairs across at least 4 passages on each side, best similarity 0.484 Introducing the Content-Action Model for Web Systems ↔ Measuring success beyond the page view, 8 matching passage pairs across at least 2 passages on each side, best similarity 0.515 Introducing the Content-Action Model for Web Systems ↔ How to measure impact when analytics lie, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.504 Introducing the Content-Action Model for Web Systems ↔ Digital transformation for complex organizations (Parts 1-2), 56 matching passage pairs across at least 11 passages on each side, best similarity 0.604 Introducing the Content-Action Model for Web Systems ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 28 matching passage pairs across at least 9 passages on each side, best similarity 0.59 Introducing the Content-Action Model for Web Systems ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 8 matching passage pairs across at least 3 passages on each side, best similarity 0.517 Introducing the Content-Action Model for Web Systems ↔ Collaborate on any webpage with a bookmarklet and URL state, 1 matching passage pair across at least 1 passage on each side, best similarity 0.473 Introducing the Content-Action Model for Web Systems ↔ Semantic search on a static site, no API keys required, 1 matching passage pair across at least 1 passage on each side, best similarity 0.471 Introducing the Content-Action Model for Web Systems ↔ Content architecture: the delivery problem, 107 matching passage pairs across at least 11 passages on each side, best similarity 0.584 Introducing the Content-Action Model for Web Systems ↔ Why context engineering was always the job, 8 matching passage pairs across at least 2 passages on each side, best similarity 0.53 Introducing the Content-Action Model for Web Systems ↔ The right answer has to be woven, 11 matching passage pairs across at least 6 passages on each side, best similarity 0.523 Introducing the Content-Action Model for Web Systems ↔ CADI: a prescriptive path for slop-free AI in content work, 11 matching passage pairs across at least 5 passages on each side, best similarity 0.496 Introducing the Content-Action Model for Web Systems ↔ 13 words to turn a rumor into AI fact, 1 matching passage pair across at least 1 passage on each side, best similarity 0.462 Introducing the Content-Action Model for Web Systems ↔ A fresh coat of paint and making information actionable for 24 years, 8 matching passage pairs across at least 3 passages on each side, best similarity 0.524 Introducing the Content-Action Model for Web Systems ↔ Improving AI chatbots with an editorial handbook from your best content, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.467 Introducing the Content-Action Model for Web Systems ↔ Building a component library adopted across 50+ scientific properties, 9 matching passage pairs across at least 2 passages on each side, best similarity 0.547 Introducing the Content-Action Model for Web Systems ↔ Untangling an 80-link footer into scannable navigation, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.523 Introducing the Content-Action Model for Web Systems ↔ Decoupling content from platforms across 80 properties, 30 matching passage pairs across at least 8 passages on each side, best similarity 0.569 Introducing the Content-Action Model for Web Systems ↔ Turning vague content guidelines into measurable AI-ready standards, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.504 Introducing the Content-Action Model for Web Systems ↔ Making disaster economics compelling for global policymakers, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.495 Introducing the Content-Action Model for Web Systems ↔ Recovering platform performance after a cloud migration failure, 1 matching passage pair across at least 1 passage on each side, best similarity 0.456 Introducing the Content-Action Model for Web Systems ↔ One shared truth for Storybook and Figma, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.465 Introducing the Content-Action Model for Web Systems ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 8 matching passage pairs across at least 3 passages on each side, best similarity 0.501 UX, discovery, analysis + the CAM ↔ Inside the Content-Action Model, 8 matching passage pairs across at least 2 passages on each side, best similarity 0.797 UX, discovery, analysis + the CAM ↔ Individualism is the flavor AI chatbots can't stomach, 1 matching passage pair across at least 1 passage on each side, best similarity 0.485 UX, discovery, analysis + the CAM ↔ Measuring success beyond the page view, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.457 UX, discovery, analysis + the CAM ↔ How to measure impact when analytics lie, 1 matching passage pair across at least 1 passage on each side, best similarity 0.484 UX, discovery, analysis + the CAM ↔ Digital transformation for complex organizations (Parts 1-2), 4 matching passage pairs across at least 2 passages on each side, best similarity 0.494 UX, discovery, analysis + the CAM ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 2 matching passage pairs across at least 1 passage on each side, best similarity 0.465 UX, discovery, analysis + the CAM ↔ Content architecture: the delivery problem, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.491 UX, discovery, analysis + the CAM ↔ The right answer has to be woven, 1 matching passage pair across at least 1 passage on each side, best similarity 0.457 UX, discovery, analysis + the CAM ↔ CADI: a prescriptive path for slop-free AI in content work, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.481 UX, discovery, analysis + the CAM ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.484 UX, discovery, analysis + the CAM ↔ Turning vague content guidelines into measurable AI-ready standards, 1 matching passage pair across at least 1 passage on each side, best similarity 0.463 UX, discovery, analysis + the CAM ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 1 matching passage pair across at least 1 passage on each side, best similarity 0.46 Migrating to Zurb Panini 2.0 ↔ Integrating Eleventy with gulp, upstream JS, 8 matching passage pairs across at least 2 passages on each side, best similarity 0.554 Migrating to Zurb Panini 2.0 ↔ Fractal and Eleventy: Getting static sites closer to the design system, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.469 Migrating to Zurb Panini 2.0 ↔ Moving from Panini to Eleventy, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.499 Migrating to Zurb Panini 2.0 ↔ Lerna monorepos with fewer tags, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.552 Migrating to Zurb Panini 2.0 ↔ Using Nunjucks templates with React, 1 matching passage pair across at least 1 passage on each side, best similarity 0.453 Migrating to Zurb Panini 2.0 ↔ A simpler, faster site: moving to pure Eleventy v3, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.617 Migrating to Zurb Panini 2.0 ↔ Building a virtual garage for hobby projects, 1 matching passage pair across at least 1 passage on each side, best similarity 0.484 What if: A web font for data ↔ Recursion: it's fonts all the way down, 1 matching passage pair across at least 1 passage on each side, best similarity 0.48 What if: A web font for data ↔ Stop converting SVG text to outlines, 10 matching passage pairs across at least 2 passages on each side, best similarity 0.58 What if: A web font for data ↔ A data font, from the inside out, 23 matching passage pairs across at least 3 passages on each side, best similarity 0.777 What if: A web font for data ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.465 Inside the Content-Action Model ↔ Sacrificing knowledge in the name of data, 1 matching passage pair across at least 1 passage on each side, best similarity 0.466 Inside the Content-Action Model ↔ Thoughtful AI integration beats bolted-on Clippy, 1 matching passage pair across at least 1 passage on each side, best similarity 0.45 Inside the Content-Action Model ↔ Measuring success beyond the page view, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.497 Inside the Content-Action Model ↔ How to measure impact when analytics lie, 1 matching passage pair across at least 1 passage on each side, best similarity 0.501 Inside the Content-Action Model ↔ Digital transformation for complex organizations (Parts 1-2), 12 matching passage pairs across at least 4 passages on each side, best similarity 0.517 Inside the Content-Action Model ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 10 matching passage pairs across at least 3 passages on each side, best similarity 0.521 Inside the Content-Action Model ↔ Semantic search on a static site, no API keys required, 1 matching passage pair across at least 1 passage on each side, best similarity 0.46 Inside the Content-Action Model ↔ Content architecture: the delivery problem, 32 matching passage pairs across at least 4 passages on each side, best similarity 0.547 Inside the Content-Action Model ↔ Why context engineering was always the job, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.54 Inside the Content-Action Model ↔ The right answer has to be woven, 19 matching passage pairs across at least 4 passages on each side, best similarity 0.586 Inside the Content-Action Model ↔ Let AI worry about the code, you worry about the work, 1 matching passage pair across at least 1 passage on each side, best similarity 0.471 Inside the Content-Action Model ↔ CADI: a prescriptive path for slop-free AI in content work, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.462 Inside the Content-Action Model ↔ A fresh coat of paint and making information actionable for 24 years, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.511 Inside the Content-Action Model ↔ When one person leaves, a team leaves with them, 1 matching passage pair across at least 1 passage on each side, best similarity 0.457 Inside the Content-Action Model ↔ Improving AI chatbots with an editorial handbook from your best content, 8 matching passage pairs across at least 1 passage on each side, best similarity 0.491 Inside the Content-Action Model ↔ Decoupling content from platforms across 80 properties, 10 matching passage pairs across at least 2 passages on each side, best similarity 0.515 Inside the Content-Action Model ↔ Turning vague content guidelines into measurable AI-ready standards, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.531 Inside the Content-Action Model ↔ Making disaster economics compelling for global policymakers, 1 matching passage pair across at least 1 passage on each side, best similarity 0.464 Inside the Content-Action Model ↔ One shared truth for Storybook and Figma, 1 matching passage pair across at least 1 passage on each side, best similarity 0.472 Inside the Content-Action Model ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.48 Integrating Eleventy with gulp, upstream JS ↔ Fractal and Eleventy: Getting static sites closer to the design system, 25 matching passage pairs across at least 5 passages on each side, best similarity 0.809 Integrating Eleventy with gulp, upstream JS ↔ Using Nunjucks templates with React, 10 matching passage pairs across at least 2 passages on each side, best similarity 0.641 Integrating Eleventy with gulp, upstream JS ↔ A simpler, faster site: moving to pure Eleventy v3, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.475 Integrating Eleventy with gulp, upstream JS ↔ Predictable, token-based filenames with Eleventy Image, 1 matching passage pair across at least 1 passage on each side, best similarity 0.493 Integrating Eleventy with gulp, upstream JS ↔ Building a component library adopted across 50+ scientific properties, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.536 Fractal and Eleventy: Getting static sites closer to the design system ↔ Using Nunjucks templates with React, 13 matching passage pairs across at least 4 passages on each side, best similarity 0.612 Fractal and Eleventy: Getting static sites closer to the design system ↔ A simpler, faster site: moving to pure Eleventy v3, 9 matching passage pairs across at least 2 passages on each side, best similarity 0.605 Fractal and Eleventy: Getting static sites closer to the design system ↔ Building a component library adopted across 50+ scientific properties, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.703 Fractal and Eleventy: Getting static sites closer to the design system ↔ Untangling an 80-link footer into scannable navigation, 1 matching passage pair across at least 1 passage on each side, best similarity 0.47 Building your first page with the Visual Framework 2.0 ↔ Publishing since the 2000s, 1 matching passage pair across at least 1 passage on each side, best similarity 0.458 Building your first page with the Visual Framework 2.0 ↔ Moving from Panini to Eleventy, 1 matching passage pair across at least 1 passage on each side, best similarity 0.481 Building your first page with the Visual Framework 2.0 ↔ Exposing HTML: The No-JS nudist CSS toggle, 1 matching passage pair across at least 1 passage on each side, best similarity 0.454 Building your first page with the Visual Framework 2.0 ↔ Content architecture: the delivery problem, 1 matching passage pair across at least 1 passage on each side, best similarity 0.454 Building your first page with the Visual Framework 2.0 ↔ Building a component library adopted across 50+ scientific properties, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.483 Publishing since the 2000s ↔ It's been 3.5 years, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.464 Publishing since the 2000s ↔ Making PDFs more viewable, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.493 Publishing since the 2000s ↔ A simpler, faster site: moving to pure Eleventy v3, 1 matching passage pair across at least 1 passage on each side, best similarity 0.525 Publishing since the 2000s ↔ Introducing a "Work" section, 1 matching passage pair across at least 1 passage on each side, best similarity 0.473 Publishing since the 2000s ↔ Digital transformation for complex organizations (Parts 1-2), 11 matching passage pairs across at least 4 passages on each side, best similarity 0.545 Publishing since the 2000s ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 8 matching passage pairs across at least 4 passages on each side, best similarity 0.505 Publishing since the 2000s ↔ Your browser utility wants to be a floating palette, 1 matching passage pair across at least 1 passage on each side, best similarity 0.474 Publishing since the 2000s ↔ PDF-A-go-slim: a browser-based PDF optimizer, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.47 Publishing since the 2000s ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 matching passage pair across at least 1 passage on each side, best similarity 0.494 Publishing since the 2000s ↔ Content architecture: the delivery problem, 10 matching passage pairs across at least 3 passages on each side, best similarity 0.527 Publishing since the 2000s ↔ EmDash won't beat WordPress. Drupal just needs to wait, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.464 Publishing since the 2000s ↔ Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon, 8 matching passage pairs across at least 2 passages on each side, best similarity 0.593 Publishing since the 2000s ↔ A fresh coat of paint and making information actionable for 24 years, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.506 Publishing since the 2000s ↔ NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT, 1 matching passage pair across at least 1 passage on each side, best similarity 0.45 Publishing since the 2000s ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.471 Publishing since the 2000s ↔ Building a component library adopted across 50+ scientific properties, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.517 Publishing since the 2000s ↔ Decoupling content from platforms across 80 properties, 9 matching passage pairs across at least 3 passages on each side, best similarity 0.524 Publishing since the 2000s ↔ Reclaiming three weeks of editorial time every month, 15 matching passage pairs across at least 4 passages on each side, best similarity 0.582 Publishing since the 2000s ↔ Making disaster economics compelling for global policymakers, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.467 Publishing since the 2000s ↔ Recovering platform performance after a cloud migration failure, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.502 Moving from Panini to Eleventy ↔ Something new for 2022, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.46 Moving from Panini to Eleventy ↔ A simpler, faster site: moving to pure Eleventy v3, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.682 Lerna monorepos with fewer tags ↔ Predictable, token-based filenames with Eleventy Image, 1 matching passage pair across at least 1 passage on each side, best similarity 0.474 Lerna monorepos with fewer tags ↔ Improving AI chatbots with an editorial handbook from your best content, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.529 Using Nunjucks templates with React ↔ Building a component library adopted across 50+ scientific properties, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.565 Something new for 2022 ↔ It's been 3.5 years, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.516 Something new for 2022 ↔ A simpler, faster site: moving to pure Eleventy v3, 1 matching passage pair across at least 1 passage on each side, best similarity 0.579 Something new for 2022 ↔ Introducing a "Work" section, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.533 Something new for 2022 ↔ Digital transformation for complex organizations (Parts 1-2), 3 matching passage pairs across at least 2 passages on each side, best similarity 0.483 Something new for 2022 ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 5 matching passage pairs across at least 3 passages on each side, best similarity 0.515 Something new for 2022 ↔ Content architecture: the delivery problem, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.556 Something new for 2022 ↔ EmDash won't beat WordPress. Drupal just needs to wait, 1 matching passage pair across at least 1 passage on each side, best similarity 0.497 Something new for 2022 ↔ Building a component library adopted across 50+ scientific properties, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.601 It's been 3.5 years ↔ Drupal delayed by Azure MySQL, 1 matching passage pair across at least 1 passage on each side, best similarity 0.452 It's been 3.5 years ↔ A simpler, faster site: moving to pure Eleventy v3, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.597 It's been 3.5 years ↔ Introducing a "Work" section, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.484 It's been 3.5 years ↔ Digital transformation for complex organizations (Parts 1-2), 4 matching passage pairs across at least 2 passages on each side, best similarity 0.49 It's been 3.5 years ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 3 matching passage pairs across at least 1 passage on each side, best similarity 0.482 It's been 3.5 years ↔ Blog art that belongs, 1 matching passage pair across at least 1 passage on each side, best similarity 0.52 It's been 3.5 years ↔ Content architecture: the delivery problem, 1 matching passage pair across at least 1 passage on each side, best similarity 0.463 It's been 3.5 years ↔ EmDash won't beat WordPress. Drupal just needs to wait, 1 matching passage pair across at least 1 passage on each side, best similarity 0.48 It's been 3.5 years ↔ A fresh coat of paint and making information actionable for 24 years, 7 matching passage pairs across at least 1 passage on each side, best similarity 0.595 It's been 3.5 years ↔ Building a component library adopted across 50+ scientific properties, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.468 It's been 3.5 years ↔ Decoupling content from platforms across 80 properties, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.471 It's been 3.5 years ↔ Reclaiming three weeks of editorial time every month, 1 matching passage pair across at least 1 passage on each side, best similarity 0.464 It's been 3.5 years ↔ Recovering platform performance after a cloud migration failure, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.482 Drupal delayed by Azure MySQL ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 5 matching passage pairs across at least 3 passages on each side, best similarity 0.499 Drupal delayed by Azure MySQL ↔ Recovering platform performance after a cloud migration failure, 45 matching passage pairs across at least 6 passages on each side, best similarity 0.749 Making PDFs more viewable ↔ Go-go-go … I missed EmbedPDF, 24 matching passage pairs across at least 3 passages on each side, best similarity 0.754 Making PDFs more viewable ↔ Digital transformation for complex organizations (Parts 1-2), 1 matching passage pair across at least 1 passage on each side, best similarity 0.463 Making PDFs more viewable ↔ Your browser utility wants to be a floating palette, 31 matching passage pairs across at least 7 passages on each side, best similarity 0.565 Making PDFs more viewable ↔ PDF-A-go-slim: a browser-based PDF optimizer, 44 matching passage pairs across at least 7 passages on each side, best similarity 0.674 Making PDFs more viewable ↔ Collaborate on any webpage with a bookmarklet and URL state, 10 matching passage pairs across at least 3 passages on each side, best similarity 0.572 Making PDFs more viewable ↔ Stop converting SVG text to outlines, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.558 Making PDFs more viewable ↔ Untangling an 80-link footer into scannable navigation, 1 matching passage pair across at least 1 passage on each side, best similarity 0.483 Making PDFs more viewable ↔ Making disaster economics compelling for global policymakers, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.462 A simpler, faster site: moving to pure Eleventy v3 ↔ Introducing a "Work" section, 1 matching passage pair across at least 1 passage on each side, best similarity 0.458 A simpler, faster site: moving to pure Eleventy v3 ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 matching passage pair across at least 1 passage on each side, best similarity 0.451 A simpler, faster site: moving to pure Eleventy v3 ↔ Site search without a search service, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.492 A simpler, faster site: moving to pure Eleventy v3 ↔ Semantic search on a static site, no API keys required, 1 matching passage pair across at least 1 passage on each side, best similarity 0.459 A simpler, faster site: moving to pure Eleventy v3 ↔ 11ty is dead, long live Build Awesome, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.512 A simpler, faster site: moving to pure Eleventy v3 ↔ Content architecture: the delivery problem, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.56 A simpler, faster site: moving to pure Eleventy v3 ↔ EmDash won't beat WordPress. Drupal just needs to wait, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.485 A simpler, faster site: moving to pure Eleventy v3 ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.457 A simpler, faster site: moving to pure Eleventy v3 ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 1 matching passage pair across at least 1 passage on each side, best similarity 0.493 A simpler, faster site: moving to pure Eleventy v3 ↔ Building a component library adopted across 50+ scientific properties, 9 matching passage pairs across at least 2 passages on each side, best similarity 0.622 A simpler, faster site: moving to pure Eleventy v3 ↔ Untangling an 80-link footer into scannable navigation, 8 matching passage pairs across at least 2 passages on each side, best similarity 0.564 A simpler, faster site: moving to pure Eleventy v3 ↔ Decoupling content from platforms across 80 properties, 11 matching passage pairs across at least 1 passage on each side, best similarity 0.529 A simpler, faster site: moving to pure Eleventy v3 ↔ Making disaster economics compelling for global policymakers, 1 matching passage pair across at least 1 passage on each side, best similarity 0.472 A simpler, faster site: moving to pure Eleventy v3 ↔ Recovering platform performance after a cloud migration failure, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.528 Go-go-go … I missed EmbedPDF ↔ Your browser utility wants to be a floating palette, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.484 Go-go-go … I missed EmbedPDF ↔ PDF-A-go-slim: a browser-based PDF optimizer, 19 matching passage pairs across at least 3 passages on each side, best similarity 0.701 Go-go-go … I missed EmbedPDF ↔ Collaborate on any webpage with a bookmarklet and URL state, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.516 Go-go-go … I missed EmbedPDF ↔ Stop converting SVG text to outlines, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.479 Exposing HTML: The No-JS nudist CSS toggle ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.575 Sacrificing knowledge in the name of data ↔ Digital transformation for complex organizations (Parts 1-2), 1 matching passage pair across at least 1 passage on each side, best similarity 0.475 Sacrificing knowledge in the name of data ↔ Content architecture: the delivery problem, 1 matching passage pair across at least 1 passage on each side, best similarity 0.499 Sacrificing knowledge in the name of data ↔ Comprehension debt, when AI-generated code outpaces human understanding, 1 matching passage pair across at least 1 passage on each side, best similarity 0.478 Sacrificing knowledge in the name of data ↔ Why context engineering was always the job, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.538 Sacrificing knowledge in the name of data ↔ The right answer has to be woven, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.495 Sacrificing knowledge in the name of data ↔ 13 words to turn a rumor into AI fact, 1 matching passage pair across at least 1 passage on each side, best similarity 0.48 Sacrificing knowledge in the name of data ↔ A fresh coat of paint and making information actionable for 24 years, 5 matching passage pairs across at least 1 passage on each side, best similarity 0.474 Sacrificing knowledge in the name of data ↔ Turning vague content guidelines into measurable AI-ready standards, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.502 Sacrificing knowledge in the name of data ↔ One shared truth for Storybook and Figma, 1 matching passage pair across at least 1 passage on each side, best similarity 0.492 Individualism is the flavor AI chatbots can't stomach ↔ Thoughtful AI integration beats bolted-on Clippy, 9 matching passage pairs across at least 2 passages on each side, best similarity 0.53 Individualism is the flavor AI chatbots can't stomach ↔ Plenty to learn from Fedora's approach to AI code, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.487 Individualism is the flavor AI chatbots can't stomach ↔ Making sense of Microsoft's many AI Copilots, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.469 Individualism is the flavor AI chatbots can't stomach ↔ Measuring success beyond the page view, 13 matching passage pairs across at least 4 passages on each side, best similarity 0.512 Individualism is the flavor AI chatbots can't stomach ↔ How to measure impact when analytics lie, 19 matching passage pairs across at least 6 passages on each side, best similarity 0.62 Individualism is the flavor AI chatbots can't stomach ↔ Digital transformation for complex organizations (Parts 1-2), 21 matching passage pairs across at least 7 passages on each side, best similarity 0.61 Individualism is the flavor AI chatbots can't stomach ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 1 matching passage pair across at least 1 passage on each side, best similarity 0.452 Individualism is the flavor AI chatbots can't stomach ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 5 matching passage pairs across at least 3 passages on each side, best similarity 0.512 Individualism is the flavor AI chatbots can't stomach ↔ Content architecture: the delivery problem, 5 matching passage pairs across at least 4 passages on each side, best similarity 0.48 Individualism is the flavor AI chatbots can't stomach ↔ Why context engineering was always the job, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.468 Individualism is the flavor AI chatbots can't stomach ↔ Four gears of AI-assisted development: from coding to context, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.462 Individualism is the flavor AI chatbots can't stomach ↔ The right answer has to be woven, 1 matching passage pair across at least 1 passage on each side, best similarity 0.465 Individualism is the flavor AI chatbots can't stomach ↔ Let AI worry about the code, you worry about the work, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.487 Individualism is the flavor AI chatbots can't stomach ↔ Why 'reviewed' should be a protected verb, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.531 Individualism is the flavor AI chatbots can't stomach ↔ CADI: a prescriptive path for slop-free AI in content work, 26 matching passage pairs across at least 7 passages on each side, best similarity 0.521 Individualism is the flavor AI chatbots can't stomach ↔ 13 words to turn a rumor into AI fact, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.538 Individualism is the flavor AI chatbots can't stomach ↔ A fresh coat of paint and making information actionable for 24 years, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.466 Individualism is the flavor AI chatbots can't stomach ↔ Improving AI chatbots with an editorial handbook from your best content, 72 matching passage pairs across at least 9 passages on each side, best similarity 0.589 Individualism is the flavor AI chatbots can't stomach ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 1 matching passage pair across at least 1 passage on each side, best similarity 0.463 Individualism is the flavor AI chatbots can't stomach ↔ Turning vague content guidelines into measurable AI-ready standards, 1 matching passage pair across at least 1 passage on each side, best similarity 0.451 Individualism is the flavor AI chatbots can't stomach ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.557 Thoughtful AI integration beats bolted-on Clippy ↔ The power of the pause: How planning beats prompt tuning, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.715 Thoughtful AI integration beats bolted-on Clippy ↔ Plenty to learn from Fedora's approach to AI code, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.524 Thoughtful AI integration beats bolted-on Clippy ↔ Making sense of Microsoft's many AI Copilots, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.51 Thoughtful AI integration beats bolted-on Clippy ↔ Digest videos into sketchnotes through AI, 1 matching passage pair across at least 1 passage on each side, best similarity 0.53 Thoughtful AI integration beats bolted-on Clippy ↔ Digital transformation for complex organizations (Parts 1-2), 5 matching passage pairs across at least 2 passages on each side, best similarity 0.571 Thoughtful AI integration beats bolted-on Clippy ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 1 matching passage pair across at least 1 passage on each side, best similarity 0.507 Thoughtful AI integration beats bolted-on Clippy ↔ Comprehension debt, when AI-generated code outpaces human understanding, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.52 Thoughtful AI integration beats bolted-on Clippy ↔ Why context engineering was always the job, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.461 Thoughtful AI integration beats bolted-on Clippy ↔ Four gears of AI-assisted development: from coding to context, 11 matching passage pairs across at least 2 passages on each side, best similarity 0.575 Thoughtful AI integration beats bolted-on Clippy ↔ The right answer has to be woven, 10 matching passage pairs across at least 2 passages on each side, best similarity 0.515 Thoughtful AI integration beats bolted-on Clippy ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.503 Thoughtful AI integration beats bolted-on Clippy ↔ Let AI worry about the code, you worry about the work, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.545 Thoughtful AI integration beats bolted-on Clippy ↔ Why 'reviewed' should be a protected verb, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.463 Thoughtful AI integration beats bolted-on Clippy ↔ CADI: a prescriptive path for slop-free AI in content work, 47 matching passage pairs across at least 2 passages on each side, best similarity 0.696 Thoughtful AI integration beats bolted-on Clippy ↔ 13 words to turn a rumor into AI fact, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.451 Thoughtful AI integration beats bolted-on Clippy ↔ Improving AI chatbots with an editorial handbook from your best content, 31 matching passage pairs across at least 2 passages on each side, best similarity 0.799 Thoughtful AI integration beats bolted-on Clippy ↔ Turning vague content guidelines into measurable AI-ready standards, 12 matching passage pairs across at least 2 passages on each side, best similarity 0.595 The power of the pause: How planning beats prompt tuning ↔ Introducing a "Work" section, 1 matching passage pair across at least 1 passage on each side, best similarity 0.461 The power of the pause: How planning beats prompt tuning ↔ Plenty to learn from Fedora's approach to AI code, 1 matching passage pair across at least 1 passage on each side, best similarity 0.473 The power of the pause: How planning beats prompt tuning ↔ Making sense of Microsoft's many AI Copilots, 1 matching passage pair across at least 1 passage on each side, best similarity 0.502 The power of the pause: How planning beats prompt tuning ↔ Large projects need large communicating, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.537 The power of the pause: How planning beats prompt tuning ↔ Digital transformation for complex organizations (Parts 1-2), 4 matching passage pairs across at least 2 passages on each side, best similarity 0.466 The power of the pause: How planning beats prompt tuning ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 45 matching passage pairs across at least 10 passages on each side, best similarity 0.563 The power of the pause: How planning beats prompt tuning ↔ AI coding tools turned my once-a-year hobby project into a daily habit, 1 matching passage pair across at least 1 passage on each side, best similarity 0.456 The power of the pause: How planning beats prompt tuning ↔ Comprehension debt, when AI-generated code outpaces human understanding, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.519 The power of the pause: How planning beats prompt tuning ↔ The ladder was always context, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.54 The power of the pause: How planning beats prompt tuning ↔ Why context engineering was always the job, 30 matching passage pairs across at least 7 passages on each side, best similarity 0.598 The power of the pause: How planning beats prompt tuning ↔ Four gears of AI-assisted development: from coding to context, 43 matching passage pairs across at least 9 passages on each side, best similarity 0.602 The power of the pause: How planning beats prompt tuning ↔ The right answer has to be woven, 13 matching passage pairs across at least 4 passages on each side, best similarity 0.559 The power of the pause: How planning beats prompt tuning ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 12 matching passage pairs across at least 5 passages on each side, best similarity 0.579 The power of the pause: How planning beats prompt tuning ↔ Let AI worry about the code, you worry about the work, 31 matching passage pairs across at least 6 passages on each side, best similarity 0.632 The power of the pause: How planning beats prompt tuning ↔ CADI: a prescriptive path for slop-free AI in content work, 140 matching passage pairs across at least 13 passages on each side, best similarity 0.721 The power of the pause: How planning beats prompt tuning ↔ We act like startups but skip their hard-won lessons, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.516 The power of the pause: How planning beats prompt tuning ↔ Improving AI chatbots with an editorial handbook from your best content, 36 matching passage pairs across at least 4 passages on each side, best similarity 0.71 The power of the pause: How planning beats prompt tuning ↔ Turning vague content guidelines into measurable AI-ready standards, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.541 Output: An HTML-native tag once again saves JS befuddling ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.484 Introducing a "Work" section ↔ How to measure impact when analytics lie, 1 matching passage pair across at least 1 passage on each side, best similarity 0.465 Introducing a "Work" section ↔ Digital transformation for complex organizations (Parts 1-2), 8 matching passage pairs across at least 1 passage on each side, best similarity 0.609 Introducing a "Work" section ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 14 matching passage pairs across at least 1 passage on each side, best similarity 0.586 Introducing a "Work" section ↔ Content architecture: the delivery problem, 1 matching passage pair across at least 1 passage on each side, best similarity 0.51 Introducing a "Work" section ↔ A fresh coat of paint and making information actionable for 24 years, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.453 Introducing a "Work" section ↔ Building a component library adopted across 50+ scientific properties, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.489 Introducing a "Work" section ↔ Reclaiming three weeks of editorial time every month, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.549 Introducing a "Work" section ↔ Recovering platform performance after a cloud migration failure, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.469 Introducing a "Work" section ↔ One shared truth for Storybook and Figma, 1 matching passage pair across at least 1 passage on each side, best similarity 0.496 Plenty to learn from Fedora's approach to AI code ↔ Digital transformation for complex organizations (Parts 1-2), 3 matching passage pairs across at least 1 passage on each side, best similarity 0.482 Plenty to learn from Fedora's approach to AI code ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 1 matching passage pair across at least 1 passage on each side, best similarity 0.456 Plenty to learn from Fedora's approach to AI code ↔ Comprehension debt, when AI-generated code outpaces human understanding, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.493 Plenty to learn from Fedora's approach to AI code ↔ Four gears of AI-assisted development: from coding to context, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.542 Plenty to learn from Fedora's approach to AI code ↔ The right answer has to be woven, 1 matching passage pair across at least 1 passage on each side, best similarity 0.466 Plenty to learn from Fedora's approach to AI code ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 1 matching passage pair across at least 1 passage on each side, best similarity 0.457 Plenty to learn from Fedora's approach to AI code ↔ Let AI worry about the code, you worry about the work, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.491 Plenty to learn from Fedora's approach to AI code ↔ Why 'reviewed' should be a protected verb, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.587 Plenty to learn from Fedora's approach to AI code ↔ CADI: a prescriptive path for slop-free AI in content work, 21 matching passage pairs across at least 2 passages on each side, best similarity 0.583 Plenty to learn from Fedora's approach to AI code ↔ Improving AI chatbots with an editorial handbook from your best content, 8 matching passage pairs across at least 1 passage on each side, best similarity 0.533 Plenty to learn from Fedora's approach to AI code ↔ Turning vague content guidelines into measurable AI-ready standards, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.544 Why AI can't be debugged like traditional software ↔ Comprehension debt, when AI-generated code outpaces human understanding, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.529 Why AI can't be debugged like traditional software ↔ Why context engineering was always the job, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.471 Why AI can't be debugged like traditional software ↔ Four gears of AI-assisted development: from coding to context, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.568 Why AI can't be debugged like traditional software ↔ The right answer has to be woven, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.485 Why AI can't be debugged like traditional software ↔ Let AI worry about the code, you worry about the work, 1 matching passage pair across at least 1 passage on each side, best similarity 0.453 Why AI can't be debugged like traditional software ↔ CADI: a prescriptive path for slop-free AI in content work, 7 matching passage pairs across at least 1 passage on each side, best similarity 0.543 Why AI can't be debugged like traditional software ↔ Rehabilitating Johnny Castaway for the browser, 1 matching passage pair across at least 1 passage on each side, best similarity 0.461 Why AI can't be debugged like traditional software ↔ When one person leaves, a team leaves with them, 1 matching passage pair across at least 1 passage on each side, best similarity 0.454 Making sense of Microsoft's many AI Copilots ↔ Four gears of AI-assisted development: from coding to context, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.563 Making sense of Microsoft's many AI Copilots ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.546 Making sense of Microsoft's many AI Copilots ↔ Let AI worry about the code, you worry about the work, 1 matching passage pair across at least 1 passage on each side, best similarity 0.536 Making sense of Microsoft's many AI Copilots ↔ CADI: a prescriptive path for slop-free AI in content work, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.491 Making sense of Microsoft's many AI Copilots ↔ Improving AI chatbots with an editorial handbook from your best content, 8 matching passage pairs across at least 1 passage on each side, best similarity 0.567 Measuring success beyond the page view ↔ How to measure impact when analytics lie, 162 matching passage pairs across at least 12 passages on each side, best similarity 0.751 Measuring success beyond the page view ↔ Digital transformation for complex organizations (Parts 1-2), 32 matching passage pairs across at least 6 passages on each side, best similarity 0.705 Measuring success beyond the page view ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 24 matching passage pairs across at least 7 passages on each side, best similarity 0.615 Measuring success beyond the page view ↔ Let AI worry about the code, you worry about the work, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.459 Measuring success beyond the page view ↔ Eye-tracking heatmaps in your browser, no lab needed, 1 matching passage pair across at least 1 passage on each side, best similarity 0.465 Measuring success beyond the page view ↔ CADI: a prescriptive path for slop-free AI in content work, 21 matching passage pairs across at least 4 passages on each side, best similarity 0.571 Measuring success beyond the page view ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.454 Measuring success beyond the page view ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 9 matching passage pairs across at least 3 passages on each side, best similarity 0.505 Measuring success beyond the page view ↔ Untangling an 80-link footer into scannable navigation, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.507 Measuring success beyond the page view ↔ Making disaster economics compelling for global policymakers, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.516 Measuring success beyond the page view ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 104 matching passage pairs across at least 9 passages on each side, best similarity 0.717 Measuring success beyond the page view ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 10 matching passage pairs across at least 4 passages on each side, best similarity 0.553 Large projects need large communicating ↔ Digital transformation for complex organizations (Parts 1-2), 1 matching passage pair across at least 1 passage on each side, best similarity 0.455 Large projects need large communicating ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 3 matching passage pairs across at least 1 passage on each side, best similarity 0.512 Large projects need large communicating ↔ Let AI worry about the code, you worry about the work, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.488 Large projects need large communicating ↔ CADI: a prescriptive path for slop-free AI in content work, 1 matching passage pair across at least 1 passage on each side, best similarity 0.477 Digest videos into sketchnotes through AI ↔ Comprehension debt, when AI-generated code outpaces human understanding, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.498 Digest videos into sketchnotes through AI ↔ CADI: a prescriptive path for slop-free AI in content work, 10 matching passage pairs across at least 1 passage on each side, best similarity 0.517 Digest videos into sketchnotes through AI ↔ Improving AI chatbots with an editorial handbook from your best content, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.484 URLs are the state management you should use ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 matching passage pair across at least 1 passage on each side, best similarity 0.501 URLs are the state management you should use ↔ Collaborate on any webpage with a bookmarklet and URL state, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.509 How to measure impact when analytics lie ↔ Digital transformation for complex organizations (Parts 1-2), 43 matching passage pairs across at least 12 passages on each side, best similarity 0.701 How to measure impact when analytics lie ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 24 matching passage pairs across at least 5 passages on each side, best similarity 0.645 How to measure impact when analytics lie ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.466 How to measure impact when analytics lie ↔ Content architecture: the delivery problem, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.454 How to measure impact when analytics lie ↔ Let AI worry about the code, you worry about the work, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.461 How to measure impact when analytics lie ↔ CADI: a prescriptive path for slop-free AI in content work, 18 matching passage pairs across at least 3 passages on each side, best similarity 0.563 How to measure impact when analytics lie ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.463 How to measure impact when analytics lie ↔ Improving AI chatbots with an editorial handbook from your best content, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.47 How to measure impact when analytics lie ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.475 How to measure impact when analytics lie ↔ Making disaster economics compelling for global policymakers, 7 matching passage pairs across at least 2 passages on each side, best similarity 0.509 How to measure impact when analytics lie ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 125 matching passage pairs across at least 9 passages on each side, best similarity 0.771 How to measure impact when analytics lie ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 23 matching passage pairs across at least 5 passages on each side, best similarity 0.571 Digital transformation for complex organizations (Parts 1-2) ↔ The practitioner's guide to planning digital transformation (Parts 3-4), 275 matching passage pairs across at least 16 passages on each side, best similarity 0.798 Digital transformation for complex organizations (Parts 1-2) ↔ Two-way communication beats another shipped feature, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.528 Digital transformation for complex organizations (Parts 1-2) ↔ Content architecture: the delivery problem, 164 matching passage pairs across at least 15 passages on each side, best similarity 0.633 Digital transformation for complex organizations (Parts 1-2) ↔ Why context engineering was always the job, 11 matching passage pairs across at least 4 passages on each side, best similarity 0.553 Digital transformation for complex organizations (Parts 1-2) ↔ Four gears of AI-assisted development: from coding to context, 19 matching passage pairs across at least 7 passages on each side, best similarity 0.533 Digital transformation for complex organizations (Parts 1-2) ↔ The right answer has to be woven, 64 matching passage pairs across at least 13 passages on each side, best similarity 0.632 Digital transformation for complex organizations (Parts 1-2) ↔ EmDash won't beat WordPress. Drupal just needs to wait, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.457 Digital transformation for complex organizations (Parts 1-2) ↔ Let AI worry about the code, you worry about the work, 1 matching passage pair across at least 1 passage on each side, best similarity 0.478 Digital transformation for complex organizations (Parts 1-2) ↔ Why 'reviewed' should be a protected verb, 1 matching passage pair across at least 1 passage on each side, best similarity 0.482 Digital transformation for complex organizations (Parts 1-2) ↔ My daily routine assumes the internet survives the disaster, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.461 Digital transformation for complex organizations (Parts 1-2) ↔ CADI: a prescriptive path for slop-free AI in content work, 43 matching passage pairs across at least 10 passages on each side, best similarity 0.634 Digital transformation for complex organizations (Parts 1-2) ↔ A fresh coat of paint and making information actionable for 24 years, 9 matching passage pairs across at least 3 passages on each side, best similarity 0.495 Digital transformation for complex organizations (Parts 1-2) ↔ When one person leaves, a team leaves with them, 11 matching passage pairs across at least 3 passages on each side, best similarity 0.515 Digital transformation for complex organizations (Parts 1-2) ↔ Improving AI chatbots with an editorial handbook from your best content, 30 matching passage pairs across at least 4 passages on each side, best similarity 0.546 Digital transformation for complex organizations (Parts 1-2) ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 1 matching passage pair across at least 1 passage on each side, best similarity 0.495 Digital transformation for complex organizations (Parts 1-2) ↔ Building a component library adopted across 50+ scientific properties, 18 matching passage pairs across at least 7 passages on each side, best similarity 0.554 Digital transformation for complex organizations (Parts 1-2) ↔ Untangling an 80-link footer into scannable navigation, 8 matching passage pairs across at least 3 passages on each side, best similarity 0.513 Digital transformation for complex organizations (Parts 1-2) ↔ Decoupling content from platforms across 80 properties, 55 matching passage pairs across at least 9 passages on each side, best similarity 0.577 Digital transformation for complex organizations (Parts 1-2) ↔ Reclaiming three weeks of editorial time every month, 13 matching passage pairs across at least 3 passages on each side, best similarity 0.578 Digital transformation for complex organizations (Parts 1-2) ↔ Turning vague content guidelines into measurable AI-ready standards, 25 matching passage pairs across at least 4 passages on each side, best similarity 0.628 Digital transformation for complex organizations (Parts 1-2) ↔ Making disaster economics compelling for global policymakers, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.483 Digital transformation for complex organizations (Parts 1-2) ↔ Recovering platform performance after a cloud migration failure, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.485 Digital transformation for complex organizations (Parts 1-2) ↔ One shared truth for Storybook and Figma, 19 matching passage pairs across at least 3 passages on each side, best similarity 0.607 Digital transformation for complex organizations (Parts 1-2) ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 27 matching passage pairs across at least 6 passages on each side, best similarity 0.607 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Two-way communication beats another shipped feature, 1 matching passage pair across at least 1 passage on each side, best similarity 0.552 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Content architecture: the delivery problem, 45 matching passage pairs across at least 14 passages on each side, best similarity 0.593 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Why context engineering was always the job, 7 matching passage pairs across at least 4 passages on each side, best similarity 0.531 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Four gears of AI-assisted development: from coding to context, 11 matching passage pairs across at least 6 passages on each side, best similarity 0.508 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ The right answer has to be woven, 26 matching passage pairs across at least 8 passages on each side, best similarity 0.587 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ EmDash won't beat WordPress. Drupal just needs to wait, 1 matching passage pair across at least 1 passage on each side, best similarity 0.45 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Let AI worry about the code, you worry about the work, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.469 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ CADI: a prescriptive path for slop-free AI in content work, 79 matching passage pairs across at least 15 passages on each side, best similarity 0.605 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ A fresh coat of paint and making information actionable for 24 years, 5 matching passage pairs across at least 3 passages on each side, best similarity 0.548 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ When one person leaves, a team leaves with them, 12 matching passage pairs across at least 3 passages on each side, best similarity 0.562 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Improving AI chatbots with an editorial handbook from your best content, 15 matching passage pairs across at least 5 passages on each side, best similarity 0.522 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Building a component library adopted across 50+ scientific properties, 10 matching passage pairs across at least 6 passages on each side, best similarity 0.511 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Decoupling content from platforms across 80 properties, 16 matching passage pairs across at least 4 passages on each side, best similarity 0.536 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Reclaiming three weeks of editorial time every month, 25 matching passage pairs across at least 4 passages on each side, best similarity 0.61 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Turning vague content guidelines into measurable AI-ready standards, 24 matching passage pairs across at least 7 passages on each side, best similarity 0.556 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Making disaster economics compelling for global policymakers, 8 matching passage pairs across at least 3 passages on each side, best similarity 0.484 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Recovering platform performance after a cloud migration failure, 8 matching passage pairs across at least 3 passages on each side, best similarity 0.528 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ One shared truth for Storybook and Figma, 9 matching passage pairs across at least 1 passage on each side, best similarity 0.517 The practitioner's guide to planning digital transformation (Parts 3-4) ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 12 matching passage pairs across at least 4 passages on each side, best similarity 0.541 Your browser utility wants to be a floating palette ↔ PDF-A-go-slim: a browser-based PDF optimizer, 19 matching passage pairs across at least 4 passages on each side, best similarity 0.693 Your browser utility wants to be a floating palette ↔ Feedback buttons without JavaScript, using a 1990s web pattern, 1 matching passage pair across at least 1 passage on each side, best similarity 0.454 Your browser utility wants to be a floating palette ↔ Eye-tracking heatmaps in your browser, no lab needed, 1 matching passage pair across at least 1 passage on each side, best similarity 0.452 Your browser utility wants to be a floating palette ↔ Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.555 Your browser utility wants to be a floating palette ↔ Building a component library adopted across 50+ scientific properties, 1 matching passage pair across at least 1 passage on each side, best similarity 0.513 PDF-A-go-slim: a browser-based PDF optimizer ↔ Stop converting SVG text to outlines, 11 matching passage pairs across at least 4 passages on each side, best similarity 0.63 PDF-A-go-slim: a browser-based PDF optimizer ↔ Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.59 PDF-A-go-slim: a browser-based PDF optimizer ↔ Reclaiming three weeks of editorial time every month, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.48 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Collaborate on any webpage with a bookmarklet and URL state, 14 matching passage pairs across at least 5 passages on each side, best similarity 0.608 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Blog art that belongs, 1 matching passage pair across at least 1 passage on each side, best similarity 0.451 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Eye-tracking heatmaps in your browser, no lab needed, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.517 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Building a virtual garage for hobby projects, 1 matching passage pair across at least 1 passage on each side, best similarity 0.499 Feedback buttons without JavaScript, using a 1990s web pattern ↔ A fresh coat of paint and making information actionable for 24 years, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.47 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 1 matching passage pair across at least 1 passage on each side, best similarity 0.451 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Untangling an 80-link footer into scannable navigation, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.481 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Decoupling content from platforms across 80 properties, 1 matching passage pair across at least 1 passage on each side, best similarity 0.498 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Making disaster economics compelling for global policymakers, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.542 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.483 Feedback buttons without JavaScript, using a 1990s web pattern ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 1 matching passage pair across at least 1 passage on each side, best similarity 0.469 Two-way communication beats another shipped feature ↔ Let AI worry about the code, you worry about the work, 1 matching passage pair across at least 1 passage on each side, best similarity 0.464 Two-way communication beats another shipped feature ↔ CADI: a prescriptive path for slop-free AI in content work, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.484 Collaborate on any webpage with a bookmarklet and URL state ↔ Blog art that belongs, 1 matching passage pair across at least 1 passage on each side, best similarity 0.493 Collaborate on any webpage with a bookmarklet and URL state ↔ Building a virtual garage for hobby projects, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.494 Collaborate on any webpage with a bookmarklet and URL state ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.485 Collaborate on any webpage with a bookmarklet and URL state ↔ Untangling an 80-link footer into scannable navigation, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.497 Site search without a search service ↔ Semantic search on a static site, no API keys required, 91 matching passage pairs across at least 7 passages on each side, best similarity 0.839 Site search without a search service ↔ Untangling an 80-link footer into scannable navigation, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.468 Semantic search on a static site, no API keys required ↔ Blog art that belongs, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.509 Semantic search on a static site, no API keys required ↔ The right answer has to be woven, 1 matching passage pair across at least 1 passage on each side, best similarity 0.455 Semantic search on a static site, no API keys required ↔ Stop converting SVG text to outlines, 1 matching passage pair across at least 1 passage on each side, best similarity 0.46 Semantic search on a static site, no API keys required ↔ Eye-tracking heatmaps in your browser, no lab needed, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.466 Semantic search on a static site, no API keys required ↔ CADI: a prescriptive path for slop-free AI in content work, 7 matching passage pairs across at least 2 passages on each side, best similarity 0.509 Semantic search on a static site, no API keys required ↔ 13 words to turn a rumor into AI fact, 1 matching passage pair across at least 1 passage on each side, best similarity 0.456 Semantic search on a static site, no API keys required ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.456 Semantic search on a static site, no API keys required ↔ Improving AI chatbots with an editorial handbook from your best content, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.517 Semantic search on a static site, no API keys required ↔ Decoupling content from platforms across 80 properties, 1 matching passage pair across at least 1 passage on each side, best similarity 0.455 Semantic search on a static site, no API keys required ↔ Turning vague content guidelines into measurable AI-ready standards, 7 matching passage pairs across at least 2 passages on each side, best similarity 0.486 Blog art that belongs ↔ 13 words to turn a rumor into AI fact, 1 matching passage pair across at least 1 passage on each side, best similarity 0.452 Blog art that belongs ↔ A fresh coat of paint and making information actionable for 24 years, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.504 AI coding tools turned my once-a-year hobby project into a daily habit ↔ Four gears of AI-assisted development: from coding to context, 8 matching passage pairs across at least 2 passages on each side, best similarity 0.509 AI coding tools turned my once-a-year hobby project into a daily habit ↔ Let AI worry about the code, you worry about the work, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.493 AI coding tools turned my once-a-year hobby project into a daily habit ↔ CADI: a prescriptive path for slop-free AI in content work, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.474 11ty is dead, long live Build Awesome ↔ Building a component library adopted across 50+ scientific properties, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.485 Content architecture: the delivery problem ↔ The ladder was always context, 1 matching passage pair across at least 1 passage on each side, best similarity 0.472 Content architecture: the delivery problem ↔ Why context engineering was always the job, 77 matching passage pairs across at least 13 passages on each side, best similarity 0.663 Content architecture: the delivery problem ↔ Go schema-first and skeleton loading stops being a problem, 9 matching passage pairs across at least 1 passage on each side, best similarity 0.566 Content architecture: the delivery problem ↔ Four gears of AI-assisted development: from coding to context, 5 matching passage pairs across at least 1 passage on each side, best similarity 0.478 Content architecture: the delivery problem ↔ The right answer has to be woven, 212 matching passage pairs across at least 19 passages on each side, best similarity 0.672 Content architecture: the delivery problem ↔ EmDash won't beat WordPress. Drupal just needs to wait, 13 matching passage pairs across at least 2 passages on each side, best similarity 0.548 Content architecture: the delivery problem ↔ CADI: a prescriptive path for slop-free AI in content work, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.514 Content architecture: the delivery problem ↔ A fresh coat of paint and making information actionable for 24 years, 22 matching passage pairs across at least 6 passages on each side, best similarity 0.533 Content architecture: the delivery problem ↔ When one person leaves, a team leaves with them, 1 matching passage pair across at least 1 passage on each side, best similarity 0.47 Content architecture: the delivery problem ↔ Improving AI chatbots with an editorial handbook from your best content, 1 matching passage pair across at least 1 passage on each side, best similarity 0.45 Content architecture: the delivery problem ↔ Scaling Drupal e-commerce for 150,000 satellite-connected customers, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.482 Content architecture: the delivery problem ↔ Building a component library adopted across 50+ scientific properties, 116 matching passage pairs across at least 10 passages on each side, best similarity 0.733 Content architecture: the delivery problem ↔ Untangling an 80-link footer into scannable navigation, 10 matching passage pairs across at least 2 passages on each side, best similarity 0.561 Content architecture: the delivery problem ↔ Decoupling content from platforms across 80 properties, 365 matching passage pairs across at least 15 passages on each side, best similarity 0.717 Content architecture: the delivery problem ↔ Reclaiming three weeks of editorial time every month, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.464 Content architecture: the delivery problem ↔ Turning vague content guidelines into measurable AI-ready standards, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.5 Content architecture: the delivery problem ↔ Making disaster economics compelling for global policymakers, 11 matching passage pairs across at least 3 passages on each side, best similarity 0.546 Content architecture: the delivery problem ↔ Recovering platform performance after a cloud migration failure, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.493 Content architecture: the delivery problem ↔ One shared truth for Storybook and Figma, 45 matching passage pairs across at least 6 passages on each side, best similarity 0.642 Content architecture: the delivery problem ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.461 Comprehension debt, when AI-generated code outpaces human understanding ↔ The ladder was always context, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.526 Comprehension debt, when AI-generated code outpaces human understanding ↔ Why context engineering was always the job, 14 matching passage pairs across at least 3 passages on each side, best similarity 0.571 Comprehension debt, when AI-generated code outpaces human understanding ↔ Four gears of AI-assisted development: from coding to context, 21 matching passage pairs across at least 3 passages on each side, best similarity 0.592 Comprehension debt, when AI-generated code outpaces human understanding ↔ The right answer has to be woven, 11 matching passage pairs across at least 3 passages on each side, best similarity 0.618 Comprehension debt, when AI-generated code outpaces human understanding ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.529 Comprehension debt, when AI-generated code outpaces human understanding ↔ Let AI worry about the code, you worry about the work, 8 matching passage pairs across at least 3 passages on each side, best similarity 0.576 Comprehension debt, when AI-generated code outpaces human understanding ↔ CADI: a prescriptive path for slop-free AI in content work, 26 matching passage pairs across at least 3 passages on each side, best similarity 0.564 Comprehension debt, when AI-generated code outpaces human understanding ↔ Rehabilitating Johnny Castaway for the browser, 1 matching passage pair across at least 1 passage on each side, best similarity 0.454 Comprehension debt, when AI-generated code outpaces human understanding ↔ Improving AI chatbots with an editorial handbook from your best content, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.479 The ladder was always context ↔ Why context engineering was always the job, 50 matching passage pairs across at least 3 passages on each side, best similarity 0.733 The ladder was always context ↔ Four gears of AI-assisted development: from coding to context, 26 matching passage pairs across at least 3 passages on each side, best similarity 0.657 The ladder was always context ↔ The right answer has to be woven, 22 matching passage pairs across at least 3 passages on each side, best similarity 0.611 The ladder was always context ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.486 The ladder was always context ↔ CADI: a prescriptive path for slop-free AI in content work, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.518 Why context engineering was always the job ↔ Four gears of AI-assisted development: from coding to context, 102 matching passage pairs across at least 10 passages on each side, best similarity 0.661 Why context engineering was always the job ↔ The right answer has to be woven, 250 matching passage pairs across at least 17 passages on each side, best similarity 0.782 Why context engineering was always the job ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 13 matching passage pairs across at least 1 passage on each side, best similarity 0.566 Why context engineering was always the job ↔ Let AI worry about the code, you worry about the work, 10 matching passage pairs across at least 4 passages on each side, best similarity 0.622 Why context engineering was always the job ↔ CADI: a prescriptive path for slop-free AI in content work, 31 matching passage pairs across at least 10 passages on each side, best similarity 0.647 Why context engineering was always the job ↔ A fresh coat of paint and making information actionable for 24 years, 1 matching passage pair across at least 1 passage on each side, best similarity 0.46 Why context engineering was always the job ↔ When one person leaves, a team leaves with them, 1 matching passage pair across at least 1 passage on each side, best similarity 0.455 Why context engineering was always the job ↔ Improving AI chatbots with an editorial handbook from your best content, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.472 Why context engineering was always the job ↔ Building a component library adopted across 50+ scientific properties, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.474 Why context engineering was always the job ↔ Decoupling content from platforms across 80 properties, 10 matching passage pairs across at least 2 passages on each side, best similarity 0.519 Why context engineering was always the job ↔ Turning vague content guidelines into measurable AI-ready standards, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.504 Why context engineering was always the job ↔ One shared truth for Storybook and Figma, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.528 Four gears of AI-assisted development: from coding to context ↔ The right answer has to be woven, 84 matching passage pairs across at least 9 passages on each side, best similarity 0.645 Four gears of AI-assisted development: from coding to context ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 18 matching passage pairs across at least 2 passages on each side, best similarity 0.618 Four gears of AI-assisted development: from coding to context ↔ Let AI worry about the code, you worry about the work, 48 matching passage pairs across at least 6 passages on each side, best similarity 0.662 Four gears of AI-assisted development: from coding to context ↔ CADI: a prescriptive path for slop-free AI in content work, 113 matching passage pairs across at least 10 passages on each side, best similarity 0.641 Four gears of AI-assisted development: from coding to context ↔ Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.493 Four gears of AI-assisted development: from coding to context ↔ When one person leaves, a team leaves with them, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.54 Four gears of AI-assisted development: from coding to context ↔ Improving AI chatbots with an editorial handbook from your best content, 16 matching passage pairs across at least 4 passages on each side, best similarity 0.521 Four gears of AI-assisted development: from coding to context ↔ Turning vague content guidelines into measurable AI-ready standards, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.508 Four gears of AI-assisted development: from coding to context ↔ Recovering platform performance after a cloud migration failure, 1 matching passage pair across at least 1 passage on each side, best similarity 0.456 Four gears of AI-assisted development: from coding to context ↔ One shared truth for Storybook and Figma, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.472 The right answer has to be woven ↔ EmDash won't beat WordPress. Drupal just needs to wait, 1 matching passage pair across at least 1 passage on each side, best similarity 0.493 The right answer has to be woven ↔ How to write one skill for both Claude Code and GitHub Copilot CLI, 9 matching passage pairs across at least 2 passages on each side, best similarity 0.563 The right answer has to be woven ↔ Let AI worry about the code, you worry about the work, 20 matching passage pairs across at least 5 passages on each side, best similarity 0.631 The right answer has to be woven ↔ Why 'reviewed' should be a protected verb, 1 matching passage pair across at least 1 passage on each side, best similarity 0.475 The right answer has to be woven ↔ CADI: a prescriptive path for slop-free AI in content work, 108 matching passage pairs across at least 20 passages on each side, best similarity 0.636 The right answer has to be woven ↔ When one person leaves, a team leaves with them, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.5 The right answer has to be woven ↔ Improving AI chatbots with an editorial handbook from your best content, 52 matching passage pairs across at least 11 passages on each side, best similarity 0.559 The right answer has to be woven ↔ Building a component library adopted across 50+ scientific properties, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.49 The right answer has to be woven ↔ Decoupling content from platforms across 80 properties, 53 matching passage pairs across at least 7 passages on each side, best similarity 0.592 The right answer has to be woven ↔ Turning vague content guidelines into measurable AI-ready standards, 46 matching passage pairs across at least 9 passages on each side, best similarity 0.579 The right answer has to be woven ↔ Making disaster economics compelling for global policymakers, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.484 The right answer has to be woven ↔ One shared truth for Storybook and Figma, 15 matching passage pairs across at least 3 passages on each side, best similarity 0.603 EmDash won't beat WordPress. Drupal just needs to wait ↔ Building a component library adopted across 50+ scientific properties, 15 matching passage pairs across at least 3 passages on each side, best similarity 0.591 EmDash won't beat WordPress. Drupal just needs to wait ↔ Decoupling content from platforms across 80 properties, 28 matching passage pairs across at least 3 passages on each side, best similarity 0.594 EmDash won't beat WordPress. Drupal just needs to wait ↔ Reclaiming three weeks of editorial time every month, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.473 EmDash won't beat WordPress. Drupal just needs to wait ↔ Recovering platform performance after a cloud migration failure, 1 matching passage pair across at least 1 passage on each side, best similarity 0.484 EmDash won't beat WordPress. Drupal just needs to wait ↔ One shared truth for Storybook and Figma, 1 matching passage pair across at least 1 passage on each side, best similarity 0.454 How to write one skill for both Claude Code and GitHub Copilot CLI ↔ Let AI worry about the code, you worry about the work, 29 matching passage pairs across at least 6 passages on each side, best similarity 0.598 How to write one skill for both Claude Code and GitHub Copilot CLI ↔ CADI: a prescriptive path for slop-free AI in content work, 20 matching passage pairs across at least 4 passages on each side, best similarity 0.605 How to write one skill for both Claude Code and GitHub Copilot CLI ↔ Improving AI chatbots with an editorial handbook from your best content, 5 matching passage pairs across at least 2 passages on each side, best similarity 0.507 How to write one skill for both Claude Code and GitHub Copilot CLI ↔ Turning vague content guidelines into measurable AI-ready standards, 1 matching passage pair across at least 1 passage on each side, best similarity 0.455 Let AI worry about the code, you worry about the work ↔ CADI: a prescriptive path for slop-free AI in content work, 38 matching passage pairs across at least 7 passages on each side, best similarity 0.644 Let AI worry about the code, you worry about the work ↔ A fresh coat of paint and making information actionable for 24 years, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.492 Let AI worry about the code, you worry about the work ↔ Improving AI chatbots with an editorial handbook from your best content, 15 matching passage pairs across at least 5 passages on each side, best similarity 0.583 Let AI worry about the code, you worry about the work ↔ Turning vague content guidelines into measurable AI-ready standards, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.497 Let AI worry about the code, you worry about the work ↔ One shared truth for Storybook and Figma, 1 matching passage pair across at least 1 passage on each side, best similarity 0.453 Let AI worry about the code, you worry about the work ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 10 matching passage pairs across at least 4 passages on each side, best similarity 0.642 Why 'reviewed' should be a protected verb ↔ CADI: a prescriptive path for slop-free AI in content work, 8 matching passage pairs across at least 1 passage on each side, best similarity 0.545 Why 'reviewed' should be a protected verb ↔ 13 words to turn a rumor into AI fact, 1 matching passage pair across at least 1 passage on each side, best similarity 0.456 Why 'reviewed' should be a protected verb ↔ Turning vague content guidelines into measurable AI-ready standards, 1 matching passage pair across at least 1 passage on each side, best similarity 0.471 Stop converting SVG text to outlines ↔ Eye-tracking heatmaps in your browser, no lab needed, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.567 Stop converting SVG text to outlines ↔ A data font, from the inside out, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.471 Stop converting SVG text to outlines ↔ Creating warm, dappled light with CSS and SVG, 1 matching passage pair across at least 1 passage on each side, best similarity 0.485 Eye-tracking heatmaps in your browser, no lab needed ↔ NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.487 Eye-tracking heatmaps in your browser, no lab needed ↔ Rehabilitating Johnny Castaway for the browser, 1 matching passage pair across at least 1 passage on each side, best similarity 0.481 Eye-tracking heatmaps in your browser, no lab needed ↔ Creating warm, dappled light with CSS and SVG, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.473 My daily routine assumes the internet survives the disaster ↔ When one person leaves, a team leaves with them, 1 matching passage pair across at least 1 passage on each side, best similarity 0.457 My daily routine assumes the internet survives the disaster ↔ Making disaster economics compelling for global policymakers, 5 matching passage pairs across at least 1 passage on each side, best similarity 0.566 CADI: a prescriptive path for slop-free AI in content work ↔ 13 words to turn a rumor into AI fact, 11 matching passage pairs across at least 3 passages on each side, best similarity 0.537 CADI: a prescriptive path for slop-free AI in content work ↔ A fresh coat of paint and making information actionable for 24 years, 14 matching passage pairs across at least 5 passages on each side, best similarity 0.558 CADI: a prescriptive path for slop-free AI in content work ↔ When one person leaves, a team leaves with them, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.471 CADI: a prescriptive path for slop-free AI in content work ↔ Improving AI chatbots with an editorial handbook from your best content, 253 matching passage pairs across at least 16 passages on each side, best similarity 0.711 CADI: a prescriptive path for slop-free AI in content work ↔ Decoupling content from platforms across 80 properties, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.465 CADI: a prescriptive path for slop-free AI in content work ↔ Reclaiming three weeks of editorial time every month, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.541 CADI: a prescriptive path for slop-free AI in content work ↔ Turning vague content guidelines into measurable AI-ready standards, 124 matching passage pairs across at least 8 passages on each side, best similarity 0.654 CADI: a prescriptive path for slop-free AI in content work ↔ One shared truth for Storybook and Figma, 11 matching passage pairs across at least 3 passages on each side, best similarity 0.513 CADI: a prescriptive path for slop-free AI in content work ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 17 matching passage pairs across at least 3 passages on each side, best similarity 0.571 13 words to turn a rumor into AI fact ↔ Improving AI chatbots with an editorial handbook from your best content, 10 matching passage pairs across at least 3 passages on each side, best similarity 0.508 Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon ↔ NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT, 62 matching passage pairs across at least 6 passages on each side, best similarity 0.752 Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon ↔ Rehabilitating Johnny Castaway for the browser, 1 matching passage pair across at least 1 passage on each side, best similarity 0.512 A fresh coat of paint and making information actionable for 24 years ↔ When one person leaves, a team leaves with them, 1 matching passage pair across at least 1 passage on each side, best similarity 0.469 A fresh coat of paint and making information actionable for 24 years ↔ Improving AI chatbots with an editorial handbook from your best content, 7 matching passage pairs across at least 4 passages on each side, best similarity 0.487 A fresh coat of paint and making information actionable for 24 years ↔ Untangling an 80-link footer into scannable navigation, 1 matching passage pair across at least 1 passage on each side, best similarity 0.464 A fresh coat of paint and making information actionable for 24 years ↔ Decoupling content from platforms across 80 properties, 9 matching passage pairs across at least 3 passages on each side, best similarity 0.532 A fresh coat of paint and making information actionable for 24 years ↔ Reclaiming three weeks of editorial time every month, 6 matching passage pairs across at least 1 passage on each side, best similarity 0.514 A fresh coat of paint and making information actionable for 24 years ↔ Turning vague content guidelines into measurable AI-ready standards, 1 matching passage pair across at least 1 passage on each side, best similarity 0.477 A fresh coat of paint and making information actionable for 24 years ↔ Making disaster economics compelling for global policymakers, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.462 A fresh coat of paint and making information actionable for 24 years ↔ Recovering platform performance after a cloud migration failure, 1 matching passage pair across at least 1 passage on each side, best similarity 0.477 A fresh coat of paint and making information actionable for 24 years ↔ One shared truth for Storybook and Figma, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.506 A fresh coat of paint and making information actionable for 24 years ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.536 When one person leaves, a team leaves with them ↔ Building a component library adopted across 50+ scientific properties, 3 matching passage pairs across at least 1 passage on each side, best similarity 0.51 When one person leaves, a team leaves with them ↔ Decoupling content from platforms across 80 properties, 1 matching passage pair across at least 1 passage on each side, best similarity 0.494 When one person leaves, a team leaves with them ↔ Reclaiming three weeks of editorial time every month, 6 matching passage pairs across at least 2 passages on each side, best similarity 0.531 When one person leaves, a team leaves with them ↔ Recovering platform performance after a cloud migration failure, 1 matching passage pair across at least 1 passage on each side, best similarity 0.472 When one person leaves, a team leaves with them ↔ One shared truth for Storybook and Figma, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.554 Improving AI chatbots with an editorial handbook from your best content ↔ Turning vague content guidelines into measurable AI-ready standards, 99 matching passage pairs across at least 9 passages on each side, best similarity 0.758 Improving AI chatbots with an editorial handbook from your best content ↔ Making disaster economics compelling for global policymakers, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.472 Scaling Drupal e-commerce for 150,000 satellite-connected customers ↔ Building a component library adopted across 50+ scientific properties, 1 matching passage pair across at least 1 passage on each side, best similarity 0.451 Scaling Drupal e-commerce for 150,000 satellite-connected customers ↔ Decoupling content from platforms across 80 properties, 7 matching passage pairs across at least 2 passages on each side, best similarity 0.545 Scaling Drupal e-commerce for 150,000 satellite-connected customers ↔ Making disaster economics compelling for global policymakers, 4 matching passage pairs across at least 1 passage on each side, best similarity 0.514 Scaling Drupal e-commerce for 150,000 satellite-connected customers ↔ Recovering platform performance after a cloud migration failure, 21 matching passage pairs across at least 4 passages on each side, best similarity 0.589 Scaling Drupal e-commerce for 150,000 satellite-connected customers ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 7 matching passage pairs across at least 2 passages on each side, best similarity 0.486 Building a component library adopted across 50+ scientific properties ↔ Untangling an 80-link footer into scannable navigation, 26 matching passage pairs across at least 7 passages on each side, best similarity 0.568 Building a component library adopted across 50+ scientific properties ↔ Decoupling content from platforms across 80 properties, 110 matching passage pairs across at least 10 passages on each side, best similarity 0.7 Building a component library adopted across 50+ scientific properties ↔ Reclaiming three weeks of editorial time every month, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.482 Building a component library adopted across 50+ scientific properties ↔ Making disaster economics compelling for global policymakers, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.483 Building a component library adopted across 50+ scientific properties ↔ Recovering platform performance after a cloud migration failure, 9 matching passage pairs across at least 3 passages on each side, best similarity 0.497 Building a component library adopted across 50+ scientific properties ↔ One shared truth for Storybook and Figma, 15 matching passage pairs across at least 4 passages on each side, best similarity 0.52 Building a component library adopted across 50+ scientific properties ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 5 matching passage pairs across at least 1 passage on each side, best similarity 0.521 Untangling an 80-link footer into scannable navigation ↔ Decoupling content from platforms across 80 properties, 69 matching passage pairs across at least 13 passages on each side, best similarity 0.694 Untangling an 80-link footer into scannable navigation ↔ Making disaster economics compelling for global policymakers, 2 matching passage pairs across at least 2 passages on each side, best similarity 0.513 Untangling an 80-link footer into scannable navigation ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.507 Decoupling content from platforms across 80 properties ↔ Reclaiming three weeks of editorial time every month, 20 matching passage pairs across at least 4 passages on each side, best similarity 0.608 Decoupling content from platforms across 80 properties ↔ Making disaster economics compelling for global policymakers, 12 matching passage pairs across at least 2 passages on each side, best similarity 0.474 Decoupling content from platforms across 80 properties ↔ Recovering platform performance after a cloud migration failure, 9 matching passage pairs across at least 1 passage on each side, best similarity 0.582 Decoupling content from platforms across 80 properties ↔ One shared truth for Storybook and Figma, 7 matching passage pairs across at least 3 passages on each side, best similarity 0.513 Decoupling content from platforms across 80 properties ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 9 matching passage pairs across at least 2 passages on each side, best similarity 0.575 Reclaiming three weeks of editorial time every month ↔ Making disaster economics compelling for global policymakers, 4 matching passage pairs across at least 2 passages on each side, best similarity 0.48 Reclaiming three weeks of editorial time every month ↔ Recovering platform performance after a cloud migration failure, 8 matching passage pairs across at least 4 passages on each side, best similarity 0.679 Reclaiming three weeks of editorial time every month ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 1 matching passage pair across at least 1 passage on each side, best similarity 0.48 Turning vague content guidelines into measurable AI-ready standards ↔ Making disaster economics compelling for global policymakers, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.487 Turning vague content guidelines into measurable AI-ready standards ↔ One shared truth for Storybook and Figma, 2 matching passage pairs across at least 1 passage on each side, best similarity 0.473 Turning vague content guidelines into measurable AI-ready standards ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 5 matching passage pairs across at least 1 passage on each side, best similarity 0.51 Making disaster economics compelling for global policymakers ↔ Recovering platform performance after a cloud migration failure, 9 matching passage pairs across at least 3 passages on each side, best similarity 0.585 Making disaster economics compelling for global policymakers ↔ One shared truth for Storybook and Figma, 3 matching passage pairs across at least 2 passages on each side, best similarity 0.512 Making disaster economics compelling for global policymakers ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 12 matching passage pairs across at least 4 passages on each side, best similarity 0.54 Making disaster economics compelling for global policymakers ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 1 matching passage pair across at least 1 passage on each side, best similarity 0.457 Recovering platform performance after a cloud migration failure ↔ Designing analytics infrastructure that measures audience quality, not just traffic, 1 matching passage pair across at least 1 passage on each side, best similarity 0.455 Designing analytics infrastructure that measures audience quality, not just traffic ↔ Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge, 16 matching passage pairs across at least 5 passages on each side, best similarity 0.598 2013-03-21 — Cutting down on Postfix spam relaying — cloud infrastructure in Platforms — 0 cross-family connections in this panel 2013-06-12 — Muliple IPs on an Ubuntu EC2 VPC? Yes, please! — cloud infrastructure in Platforms — 0 cross-family connections in this panel 2013-12-08 — A model for better content, better readers, better journalism — content strategy in Content — 7 cross-family connections in this panel 2014-04-07 — UX success story: Doubling conversion rates, sales — UX design in IA / UX — 2 cross-family connections in this panel 2015-01-28 — How to install Lyra the graphical visualization environment — data visualization in Evidence — 0 cross-family connections in this panel 2017-07-23 — Better corporate design through information architecture — information architecture in IA / UX — 10 cross-family connections in this panel 2017-07-25 — A new site for little reason — career reflection in Personal — 6 cross-family connections in this panel 2017-09-13 — Fluid IA to enable user discovery, prepare for change — information architecture in IA / UX — 14 cross-family connections in this panel 2017-10-06 — Five highlights from EuroIA 2017 — information architecture in IA / UX — 15 cross-family connections in this panel 2017-10-27 — 8 Video conferencing tips, dos, don'ts — productivity in Transformation — 2 cross-family connections in this panel 2017-11-12 — Comparing IBM Plex and Fira Sans — typography in Typography — 0 cross-family connections in this panel 2018-01-22 — The Content-Action Model origin story — content strategy in Content — 8 cross-family connections in this panel 2018-01-22 — Introducing the Content-Action Model for Web Systems — content strategy in Content — 27 cross-family connections in this panel 2018-02-07 — UX, discovery, analysis + the CAM — content strategy in Content — 10 cross-family connections in this panel 2018-02-10 — Migrating to Zurb Panini 2.0 — static sites in Publishing — 4 cross-family connections in this panel 2018-03-19 — What if: A web font for data — typography in Typography — 1 cross-family connection in this panel 2018-03-29 — Inside the Content-Action Model — content strategy in Content — 18 cross-family connections in this panel 2018-09-12 — Faster scientific websites through reusability — design systems in Design systems — 0 cross-family connections in this panel 2019-06-27 — EMBL-EBI Day: Visual Framework 2.0 outreach — Visual Framework in Design systems — 0 cross-family connections in this panel 2019-10-21 — Integrating Eleventy with gulp, upstream JS — Eleventy in Publishing — 2 cross-family connections in this panel 2019-11-12 — Fractal and Eleventy: Getting static sites closer to the design system — Eleventy in Publishing — 3 cross-family connections in this panel 2019-11-18 — Building your first page with the Visual Framework 2.0 — Visual Framework in Design systems — 3 cross-family connections in this panel 2020-02-08 — Publishing since the 2000s — career reflection in Personal — 16 cross-family connections in this panel 2020-07-13 — Moving from Panini to Eleventy — Eleventy in Publishing — 3 cross-family connections in this panel 2020-11-11 — Lerna monorepos with fewer tags — developer tools in Making — 3 cross-family connections in this panel 2020-12-12 — Using Nunjucks templates with React — JavaScript in Making — 4 cross-family connections in this panel 2021-08-30 — EMBL.org: Empowering users to navigate a large scientific organization — information architecture in IA / UX — 0 cross-family connections in this panel 2021-12-21 — Enabling a more dynamic EMBL online — design systems in Design systems — 0 cross-family connections in this panel 2021-12-23 — Something new for 2022 — career reflection in Personal — 10 cross-family connections in this panel 2025-05-08 — It's been 3.5 years — career reflection in Personal — 13 cross-family connections in this panel 2025-07-10 — Drupal delayed by Azure MySQL — Drupal in Platforms — 1 cross-family connection in this panel 2025-08-11 — Making PDFs more viewable — PDF in Making — 7 cross-family connections in this panel 2025-08-31 — A simpler, faster site: moving to pure Eleventy v3 — Eleventy in Publishing — 20 cross-family connections in this panel 2025-09-04 — Recursion: it's fonts all the way down — typography in Typography — 0 cross-family connections in this panel 2025-09-05 — Go-go-go … I missed EmbedPDF — PDF in Making — 3 cross-family connections in this panel 2025-09-06 — Exposing HTML: The No-JS nudist CSS toggle — CSS in Design systems — 1 cross-family connection in this panel 2025-09-07 — Predictable, token-based filenames with Eleventy Image — Eleventy in Publishing — 1 cross-family connection in this panel 2025-09-12 — Sacrificing knowledge in the name of data — AI in AI — 6 cross-family connections in this panel 2025-09-14 — Individualism is the flavor AI chatbots can't stomach — AI in AI — 14 cross-family connections in this panel 2025-09-19 — A stop-gap Drupal module to kill Word Junk in CKEditor 5 — Drupal in Platforms — 0 cross-family connections in this panel 2025-09-19 — Thoughtful AI integration beats bolted-on Clippy — AI in AI — 4 cross-family connections in this panel 2025-09-23 — The power of the pause: How planning beats prompt tuning — AI in AI — 7 cross-family connections in this panel 2025-09-27 — Embracing px and rem for CSS — CSS in Design systems — 0 cross-family connections in this panel 2025-09-29 — Developers are becoming context technical writers for AI — AI in AI — 0 cross-family connections in this panel 2025-10-03 — Context engineering beats prompt tricks for AI agents — context engineering in AI — 0 cross-family connections in this panel 2025-10-13 — It's true, short disruptions costs lots of time — productivity in Transformation — 0 cross-family connections in this panel 2025-10-13 — Output: An HTML-native tag once again saves JS befuddling — web development in Publishing — 0 cross-family connections in this panel 2025-10-28 — Introducing a "Work" section — career reflection in Personal — 10 cross-family connections in this panel 2025-11-04 — Plenty to learn from Fedora's approach to AI code — AI in AI — 3 cross-family connections in this panel 2025-11-07 — Why AI can't be debugged like traditional software — AI in AI — 1 cross-family connection in this panel 2025-12-03 — Making sense of Microsoft's many AI Copilots — AI in AI — 0 cross-family connections in this panel 2025-12-03 — Measuring success beyond the page view — analytics in Evidence — 12 cross-family connections in this panel 2025-12-04 — Large projects need large communicating — project management in Transformation — 4 cross-family connections in this panel 2025-12-05 — Digest videos into sketchnotes through AI — AI in AI — 0 cross-family connections in this panel 2025-12-26 — URLs are the state management you should use — web development in Publishing — 0 cross-family connections in this panel 2026-01-15 — How to measure impact when analytics lie — analytics in Evidence — 14 cross-family connections in this panel 2026-01-24 — VR Productivity finally almost surpasses physical displays — productivity in Transformation — 0 cross-family connections in this panel 2026-01-30 — Digital transformation for complex organizations (Parts 1-2) — digital transformation in Transformation — 41 cross-family connections in this panel 2026-02-05 — The practitioner's guide to planning digital transformation (Parts 3-4) — digital transformation in Transformation — 35 cross-family connections in this panel 2026-02-16 — Your browser utility wants to be a floating palette — retro computing in Personal — 6 cross-family connections in this panel 2026-02-16 — PDF-A-go-slim: a browser-based PDF optimizer — PDF in Making — 5 cross-family connections in this panel 2026-02-20 — Feedback buttons without JavaScript, using a 1990s web pattern — web development in Publishing — 16 cross-family connections in this panel 2026-02-22 — Two-way communication beats another shipped feature — project management in Transformation — 2 cross-family connections in this panel 2026-02-25 — Collaborate on any webpage with a bookmarklet and URL state — web development in Publishing — 7 cross-family connections in this panel 2026-02-28 — Site search without a search service — search in Evidence — 2 cross-family connections in this panel 2026-03-02 — Semantic search on a static site, no API keys required — search in Evidence — 13 cross-family connections in this panel 2026-03-03 — Blog art that belongs — AI in AI — 5 cross-family connections in this panel 2026-03-04 — AI coding tools turned my once-a-year hobby project into a daily habit — AI in AI — 0 cross-family connections in this panel 2026-03-05 — 11ty is dead, long live Build Awesome — Eleventy in Publishing — 1 cross-family connection in this panel 2026-03-27 — Content architecture: the delivery problem — content architecture in Content — 30 cross-family connections in this panel 2026-03-28 — Comprehension debt, when AI-generated code outpaces human understanding — AI in AI — 2 cross-family connections in this panel 2026-03-29 — The ladder was always context — software engineering in Making — 9 cross-family connections in this panel 2026-03-30 — Why context engineering was always the job — context engineering in AI — 14 cross-family connections in this panel 2026-04-04 — Go schema-first and skeleton loading stops being a problem — content architecture in Content — 0 cross-family connections in this panel 2026-04-05 — Four gears of AI-assisted development: from coding to context — AI in AI — 9 cross-family connections in this panel 2026-04-07 — The right answer has to be woven — context engineering in AI — 18 cross-family connections in this panel 2026-04-08 — EmDash won't beat WordPress. Drupal just needs to wait — Drupal in Platforms — 14 cross-family connections in this panel 2026-04-08 — How to write one skill for both Claude Code and GitHub Copilot CLI — AI in AI — 2 cross-family connections in this panel 2026-04-20 — Let AI worry about the code, you worry about the work — AI in AI — 11 cross-family connections in this panel 2026-04-23 — Why 'reviewed' should be a protected verb — AI in AI — 2 cross-family connections in this panel 2026-04-29 — Stop converting SVG text to outlines — typography in Typography — 6 cross-family connections in this panel 2026-05-03 — Eye-tracking heatmaps in your browser, no lab needed — open source in Making — 8 cross-family connections in this panel 2026-05-06 — My daily routine assumes the internet survives the disaster — digital transformation in Transformation — 2 cross-family connections in this panel 2026-05-09 — Building a virtual garage for hobby projects — cloud infrastructure in Platforms — 3 cross-family connections in this panel 2026-05-12 — A data font, from the inside out — typography in Typography — 0 cross-family connections in this panel 2026-06-09 — CADI: a prescriptive path for slop-free AI in content work — AI in AI — 21 cross-family connections in this panel 2026-06-15 — 13 words to turn a rumor into AI fact — AI in AI — 3 cross-family connections in this panel 2026-06-26 — Field notes on Mac OS 9.2, New World ROMs, and Apple Silicon — retro computing in Personal — 2 cross-family connections in this panel 2026-08-08 — A fresh coat of paint and making information actionable for 24 years — career reflection in Personal — 33 cross-family connections in this panel 2026-08-09 — We act like startups but skip their hard-won lessons — software engineering in Making — 1 cross-family connection in this panel 2026-08-10 — NewSheep: forking SheepShaver to boot New World Mac OS 9.2 on Apple Silicon + JIT — retro computing in Personal — 1 cross-family connection in this panel 2026-08-12 — From the roof, eclipse day 2026 — photography in Other — 0 cross-family connections in this panel 2026-10-05 — Sunrise and the Siebengebirge — photography in Other — 0 cross-family connections in this panel 2026-10-19 — Rehabilitating Johnny Castaway for the browser — retro computing in Personal — 3 cross-family connections in this panel 2026-10-24 — When one person leaves, a team leaves with them — AI in AI — 11 cross-family connections in this panel 2025-12-21 — Improving AI chatbots with an editorial handbook from your best content — AI in AI — 11 cross-family connections in this panel 2025-11-08 — Creating warm, dappled light with CSS and SVG — CSS in Design systems — 2 cross-family connections in this panel 2014-06-30 — Scaling Drupal e-commerce for 150,000 satellite-connected customers — Drupal in Platforms — 13 cross-family connections in this panel 2019-11-12 — Building a component library adopted across 50+ scientific properties — Visual Framework in Design systems — 29 cross-family connections in this panel 2021-08-30 — Untangling an 80-link footer into scannable navigation — information architecture in IA / UX — 15 cross-family connections in this panel 2020-12-21 — Decoupling content from platforms across 80 properties — content architecture in Content — 22 cross-family connections in this panel 2025-08-17 — Reclaiming three weeks of editorial time every month — editorial workflow in Content — 15 cross-family connections in this panel 2025-12-21 — Turning vague content guidelines into measurable AI-ready standards — content strategy in Content — 21 cross-family connections in this panel 2025-10-18 — Making disaster economics compelling for global policymakers — data visualization in Evidence — 21 cross-family connections in this panel 2025-07-01 — Recovering platform performance after a cloud migration failure — Drupal in Platforms — 18 cross-family connections in this panel 2026-10-21 — One shared truth for Storybook and Figma — design systems in Design systems — 21 cross-family connections in this panel 2026-04-22 — Designing analytics infrastructure that measures audience quality, not just traffic — analytics in Evidence — 17 cross-family connections in this panel 2026-04-20 — Putting GA4 where the work happens: an in-browser analytics overlay and its MCP bridge — analytics in Evidence — 2 cross-family connections in this panel AI — 23 entriesAIContent — 10 entriesContentIA / UX — 6 entriesIA / UXPublishing — 11 entriesPublishingDesign systems — 9 entriesDesign systemsTypography — 5 entriesTypographyPlatforms — 8 entriesPlatformsEvidence — 8 entriesEvidenceTransformation — 8 entriesTransformationMaking — 8 entriesMakingPersonal — 10 entriesPersonalOther — 2 entriesOther
614 pairs; 417 cross a topic-family boundary.

Posts by year108 entries

Posts by publication year A sparkline of the entries in the radial diagrams from 2013 to 2026. Highlighted years follow the active entry, connection or topic family above. 2013 — 3 posts 3 2013 2014 — 2 posts 2 2014 2015 — 1 post 1 2015 2016 — 0 posts 0 2016 2017 — 6 posts 6 2017 2018 — 7 posts 7 2018 2019 — 5 posts 5 2019 2020 — 5 posts 5 2020 2021 — 4 posts 4 2021 2022 — 0 posts 0 2022 2023 — 0 posts 0 2023 2024 — 0 posts 0 2024 2025 — 32 posts 32 2025 2026 — 43 posts 43 2026

Hover a topic, entry or connection; keyboard users can focus a topic family or an entry link.

The contrast is itself a possible story: authored links cross topic-family boundaries much more often than the semantic map does. That may mean the writing makes explicit arguments between domains while the model mostly groups repeated vocabulary within them.

Limits shared by these experiments
  • The corpus is uneven: 75 of 108 entries sit in the UNDRR-era band, with a public-writing gap in 2022–24.
  • The public semantic map uses whole-entry similarity 0.6 and at most three neighbours per entry. The radial semantic panel instead compares non-header passages at 0.45 with no per-entry cap. Longer entries can produce more passage-pair matches, so line weight uses distinct passage support instead of the raw match count.
  • Essays, digesting notes and impact stories are different genres. Similarity can mean recurrence, continuation or two accounts of the same work.
  • 52 of the 71 displayed pairs are linked directly in the source. The model often confirms an authored connection rather than discovering one.
  • Career chapters are inferred from dates. They locate an entry in Ken's working life but do not prove an employer influenced it.
  • The model proposes resemblance. Claims such as “this idea matured” or “I changed my mind” require close reading and editorial annotation.
  • Outbound links are extracted from rendered article content. They include citations, tools, image credits and repeated links; they do not distinguish endorsement from criticism.
  • Suffix groups describe URL endings, not ownership or trustworthiness. Career comparisons are especially fragile in the five linked entries from the DRS-era sample.
  • The semantic index is the most recent full-build snapshot. Each passage vector also contains the entry title; the first, metadata-heavy chunk is excluded from passage comparisons.
  • The radial families are editorial groupings, not clusters discovered by the model. Radius means cross-family connection count within that panel; angle means assigned family; neither diagram is a hierarchy or genealogy.
  • The stacked topic sparklines omit one-off topics and normalize every recurring topic independently. They reveal timing and shape, but the line heights cannot be compared as publication volume.

Research precedents

These experiments borrow visual grammar and storytelling questions, not the sources' palettes, typography or composition.

  1. Martin Wattenberg, The Shape of Song: recurrence encoded as arcs along a sequence.
  2. Susan Havre, Elizabeth Hetzler and Lucy Nowell, ThemeRiver: thematic change over time read alongside contextual events.
  3. ThemeDelta: topics splitting and merging over time.
  4. Lev Manovich, On Broadway: multiple data layers aligned to a shared spine.
  5. Fernanda Viégas, Martin Wattenberg and Kushal Dave, History Flow: continuity, disappearance and reappearance across time.
  6. The Bohemian Bookshelf: coordinated visual access points into one corpus.
  7. Giorgia Lupi and Stefanie Posavec, Dear Data: personal documentary visualization with subjectivity visible.
  8. Stefanie Posavec, Writing Without Words: visualization as a close reading of significant writing.
  9. Martin Wattenberg, Notes on text visualization: bringing words and phrases forward rather than relying only on aggregation.
  10. The Pudding, How to make dope shit, part 3: exploration is raw material; a finished visualization still needs a story.
  11. Brian Moore, Radial Family Trees in Tableau: radial position combines distance from the centre with position around the circle, while bundled line elements expose relationships within and between groups.
  12. Kevin Marks, The Joy of Sparks: vertically offset, filled activity sparklines make bursts and quiet periods legible as a layered terrain.