> [!question] Lingering Questions > - What actually blocks real-time collaboration? "Server-side approaches differ by hosting" is stated but not decomposed — is it persistence, presence, conflict resolution, or all three? > - Were other accessibility validations state-blind the way the contrast-warning check was (silently not firing for viewport and pseudo-states)? That gap suggests a bug *class*, not an isolated instance. > - What is Campus Connect's completion and retention rate? The participation figures (25 institutions, 100+ each) are impressive and say nothing about outcomes. > [!tip] Article Ideas > - "Competitive velocity converts tool adoption from a choice into a condition" — Imokol's first-person AI-adoption account as the honest counter-narrative to enthusiasm framing, generalized past WordPress to any team facing shipping-speed competition. > [!link] Cross Reference > - [[3. Resources/MOCs/DevRel MOC]] — primary home; Campus Connect as teaching labor at scale, the string-freeze framing as reusable DevRel messaging > - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — Imokol's adoption-under-competitive-pressure account > - [[3. Resources/Permanent Notes/AI Tools Don't Eliminate the Apprenticeship Layer They Relocate Its Cost]] — this source's clearest first-person evidence: Imokol's self-directed troubleshooting moved into her own unpaid time > [!quote] Vocabulary > - **Configurable breakpoints** — WordPress 7.1's move of desktop/tablet/mobile viewport definitions from hardcoded values into `theme.json`, letting each theme define its own responsive behavior > - **Iframed post editor** — the post editor gaining its own isolated `document`/`window` context, the last WordPress editor surface to do so (site/template editors have been iframed since 2021) ## Bibliographic capsule Birgit Pauli-Haack (Gutenberg Times) with guest Faith Ruth Imokol (Ugandan developer, WordCamp organizer), *Gutenberg Changelog #133*. YouTube, recorded 2026-07-30, published 2026-08-02, 48m51s. Source: [Gutenberg Changelog 133 Gutenberg 23.6 Release and WordPress 7.1](3.%20Resources/Readwise/Articles/Gutenberg%20Changelog%20%23133%20–%20Gutenberg%2023.6%20Release%20and%20WordPress%207.1.md) ## Author's thesis (as I read it) **What does the episode cover?** Two distinct threads: a release walkthrough of Gutenberg 23.6 / WordPress 7.1 (configurable breakpoints, an upgraded Notes system, the post editor's move into an iframe, Tabs and Playlist blocks), and a community segment on Uganda's WordPress ecosystem, including Imokol's account of AI adoption. **Why the community half matters more than it looks.** Imokol's framing of her own AI adoption refuses both standard scripts — not enthusiasm, not refusal, but compulsion by competitive velocity, with the self-directed troubleshooting that built her expertise displaced into her own unpaid time. That cost is real, lands on the individual, and nobody budgets for it. ## Key arguments (≤3) 1. **AI adoption here was involuntary, driven by competitive pressure, not preference**: "I've been forced in some way to use AI... working along with it in my development" — and the exploration that built her skill moved to personal time. 2. **AI's missing faculty is salience, not correctness**: "it doesn't know what's important and what's not important. It's everything is the same" — verbosity in code, reviews, and analysis all trace to the same absence of proportion. 3. **A validation that silently never runs is worse than none**: the accessibility contrast-warning check wasn't firing at all for viewport and pseudo-states, manufacturing false confidence rather than flagging nothing. ## Claim atoms ### Competitive velocity made AI adoption involuntary, and displaced learning into personal time > [!quote] ID: rw_gutenberg_01 > I've been forced in some way to use AI cuz I'm using it more as a pair, working along with it in my development. **Where:** AI-practice segment. **Why it matters:** the honest adoption narrative — team competition rather than preference, with self-directed troubleshooting (the thing that actually built her expertise) moved into unpaid personal time. A first-person account of the apprenticeship layer relocating onto the individual. ### AI weights everything equally, so salience is the human contribution > [!quote] ID: rw_gutenberg_02 > it doesn't know what's important and what's not important. It's everything is the same. **Where:** AI-capability segment. **Why it matters:** names the missing faculty precisely as proportion, not correctness — pairs with the verbosity observation about code, reviews, and analysis. ### A validation that silently does not run is worse than none **Where:** contrast-warning segment — the accessibility check wasn't firing for viewport or pseudo-states, and 23.6 fixes it. **Why it matters:** false confidence is the actual failure mode; a check present in the UI but never exercised is a declared capability that was never tested. ## Permanent candidates - **Competitive velocity converts tool adoption from a choice into a condition** — distinct from the vault's existing note on which tasks get automated (that's about *which* work gets automated first, not *why* adoption happens under competitive pressure at all) and from the reverse-centaur pattern (which concerns being forced to work like a machine to feed AI, a different mechanism). **Created as permanent note.** - The apprenticeship-cost-relocation claim is already covered by [[3. Resources/Permanent Notes/AI Tools Don't Eliminate the Apprenticeship Layer They Relocate Its Cost]] — this source is a strong first-person instance to add as evidence, connect rather than duplicate. ## Processing checklist - [x] Read the full deep-read notes field (Refactor Appendix present, ported directly) - [x] Create Literature note in Konik format - [x] Create Permanent note for the highest-resonance uncaptured claim - [ ] Raise the state-blind contrast-warning gap with Accessibility as a possible bug class, not an isolated instance - [ ] Amplify WordCamp Jinja (19–20 Sept) and Campus Connect; credit Steven Dumba and Moses ## Links - [[3. Resources/MOCs/DevRel MOC]] — primary home; Campus Connect and the string-freeze framing are directly reusable DevRel material - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — Imokol's adoption-under-pressure account