# DevRel MOC ## Synthesis additions (2026-10-18 — a hackathon in place of a workshop: students, first contributions and uncounted outcomes) - [[3. Resources/Readwise/Articles/A Hackathon Instead of a Workshop, a Sold-Out WordCamp Full of Students, and a First Contribution in an Hour|A hackathon instead of a workshop…]] — Make WordPress Community roundup: Dhaka's hackathon (about half of registrants never took part) and a one-hour WP LATAM session reported with 80% first-time contributors but no attendee count. 18 of 52 links go to Slack, and no participant is quoted. ## Synthesis additions (2026-10-17 — a practitioner interview: DevRel as translation, live coding and community signals) - [[3. Resources/Readwise/Articles/Episode 36 Jacquie Capur]] — Community & Code (host Chris Reynolds): the guest on DevRel as translating geek speak, automating toil to make room for ideas, and non-employee answers in a Discord as a community health signal; several figures (142 VMs, a 16-agent pipeline, 450 sign-ups against a 400 cap) are unsourced. The guest's surname appears two ways across the description and captions. ## Synthesis additions (2026-10-15 — DevRelCon NYC 2026: agents as readers, measurement, education, community, craft) Event map: [[3. Resources/MOCs/Events/DevRelCon NYC 2026 MOC]] (34 talks). Permanents written from it: - [[3. Resources/Permanent Notes/A Coding Agent Mentioning Your Tool Does Not Mean It Installs Your Tool]] — mention rate is top of funnel; install rate is the outcome (Silverman and Barnes) - [[3. Resources/Permanent Notes/A Coding Agent Evaluates a Tool by Reading Its Docs and Pricing Pages]] — setup page, README and pricing text are the product the agent evaluates (Silverman and Barnes) - [[3. Resources/Permanent Notes/A Page Labeled for Developers Loses Readers Who Don't Call Themselves Developers]] — test the audience word in a page header when the real readers have outgrown it (Kundel) - [[3. Resources/Permanent Notes/Developers Who Build Through Agents Often Can't Name the API They Call]] — start support from what the developer is building, not which API they call (Rabasa) - [[3. Resources/Permanent Notes/Usage Is Not Adoption When a Connector Fails in Silence]] — session counts can't tell an integrated developer from one who left; adoption needs an engagement measure (Jotwani) - [[3. Resources/Permanent Notes/The Same DevRel Activity Serves a Different Audience at Each Adoption Stage]] — name the adopter stage before choosing the activity (Blanco) - [[3. Resources/Permanent Notes/Builders Partners and Customers Need Separate Funnels Because They Make Different Decisions]] — one blended engagement number hides three decisions (Morrow) - [[3. Resources/Permanent Notes/A Shared End-of-Session Check Makes Every Teaching Format Comparable]] — one shared check makes workshop, webinar and booth results comparable without changing content (Lord) - [[3. Resources/Permanent Notes/A Metric Nobody Else Acts On Is a Diary]] — a DevRel metric earns its place when someone outside DevRel changes a decision because of it (Gorton) - [[3. Resources/Permanent Notes/A Completion Count Measures Compliance Until It Is Paired With a Build Count]] — a finished-course number says who completed, not who built; report it beside something the learner made and kept (Keegan) - [[3. Resources/Permanent Notes/A Demo-Only Rubric Selects for Developers Who Cannot Explain What They Shipped]] — score the explanation as part of the rubric, not as a follow-up (Saha) - [[3. Resources/Permanent Notes/A Shared Gate Definition Turns Onboarding Complaints Into a Count Product Can Dispute]] — count the gates between arrival and first success on one real route before arguing onboarding is hard (Save) - [[3. Resources/Permanent Notes/A Contributor Program Should Ask for the Smallest Next Step Not the Top Role]] — write the smallest meaningful ask for each stage of the contributor journey (Sampaio) - [[3. Resources/Permanent Notes/A Developer Who Goes Quiet Is Telling You the Explanation Failed]] — read silent drop-off as a failed explanation before lack of interest (Murray) - [[3. Resources/Permanent Notes/A Promise Boundary Set Before the Plan Turns a Failed Swing Into a Private Incident]] — decide what the organization won't promise in public, and write a fallback that works without the ambitious part (Ruparel) - [[3. Resources/Permanent Notes/Hiring Outside Expertise Does Not Outsource Accountability for the Result]] — check one primary artifact yourself before repeating a vendor's or agent's confidence (Ruparel) - [[3. Resources/Permanent Notes/The Agent That Captured Everything Is the Wrong Reader to Find the Story]] — capture and story-finding need different readers (Meyer) - [[3. Resources/Permanent Notes/A Pitch Earns Coverage by Handing the Reporter Something No Competitor Can]] — a pitch works when it offers a fact, quote or experience nobody else can (Purdy) - [[3. Resources/Permanent Notes/A Tutorial Starts at the Reader's Actual Level, Not the Author's]] — set a tutorial's start line by what the reader knows (Kretzschmar) ## Synthesis additions (2026-10-01 — open source project governance, contribution, and exits) - [[3. Resources/Readwise/Articles/WordPress Contributor Toolkit 1.2 One App for Your First Core or Gutenberg Contribution]] — JuanMa Garrido's Make WordPress Core post (first-party release note) announces Contributor Toolkit 1.2.0, a desktop app that now covers Gutenberg GitHub contributions as well as Core Trac tickets. ## Synthesis additions (2026-10-01 — agent-facing contracts: WebMCP, WebSkill, and WordPress Abilities) - [[3. Resources/Readwise/Articles/Bringing WordPress AI to the Market]] — briancoords.com opinion post (author's own go-to-market thought exercise) proposes a Core Abilities plugin, MCP as the canonical protocol, and external agent access ranked above dashboard AI features. ## Synthesis additions (2026-10-01 — creator partnerships and WordPress product marketing) - [[3. Resources/Readwise/Articles/Building an Influencer Marketing Strategy for Tech Products]] — WP Product Talk: Katie Keith and Matt Cromwell interview Brittany Celata, Automattic's Head of Influencer Marketing, on picking creators for technical products; the campaign results cited are self-reported and unverified. ## Synthesis additions (2026-09-23 — Write the Docs Berlin: docs metrics and honest gaps) - [[3. Resources/Permanent Notes/A Docs Metric Earns Its Place by Naming Which Job It Does]] — Tal Gluck's split from the State of Docs research: a number either proves value to leadership or improves the docs; one that does neither is parked, not tracked. - [[3. Resources/Permanent Notes/A Documentation Gap Is Acceptable Only Once It Is a Recorded Decision]] — Elena Baskakova's gap register: two writers to nine products means gaps are certain, so the control is a written decision per gap, not "perfect docs everywhere." ## Synthesis additions (2026-09-26 — developer experience as a delivery KPI; where DevRel reports) - [[3. Resources/Readwise/Articles/Optimizing Developer Experience for High Engineering Performance A Roadmap for Enterprises to Reduce Friction, Measure Impact, and Scale Productivity in Software Delivery]] — Ibrahim Haddad, Linux Foundation Research (2026-09-18): perceived friction leads delivery and adoption metrics for internal and external developers alike; DORA and SPACE numbers are team trendlines, never individual scorecards; the environment builder must be judged on leading indicators or gets cut at the quarter boundary - [[3. Resources/Readwise/Articles/Is Dev Rel Marketing, Engineering, or Product The Answer Is Yes, Says Checkmarx's Tessa Mero]] — Tessa Mero, HackerNoon interview (2026-09-25): DevRel can report into marketing, engineering or product once the sponsoring executive trusts the team; a developer who cannot start in minutes leaves; "Copy Prompt" is replacing "Copy Code" as the lifted quickstart artifact - [[3. Resources/Permanent Notes/Delivery Metrics Are Team Trendlines Not Individual Scorecards]] — Permanent from the LF Research DevEx report: DORA and SPACE ranked per person measure fear - [[3. Resources/Literature Notes/First WordCamp Tips and Tricks]] — GoDaddy Pro video: first-time WordCamp attendee guidance (networking, hallway track, contributor day); sweep-slice note given frontmatter and links this run ## Synthesis additions (2026-09-23 — Write the Docs Berlin: docs metrics and honest gaps) - [[3. Resources/Permanent Notes/A Docs Metric Earns Its Place by Naming Which Job It Does]] — Tal Gluck's split from the State of Docs research: a number either proves value to leadership or improves the docs; one that does neither is parked, not tracked. - [[3. Resources/Permanent Notes/A Documentation Gap Is Acceptable Only Once It Is a Recorded Decision]] — Elena Baskakova's gap register: two writers to nine products means gaps are certain, so the control is a written decision per gap, not "perfect docs everywhere." ## Synthesis additions (2026-09-09 — the Pantheon AI position DevRel will represent) - [[The AI Realist Manifesto - Beyond the Vibe]] — the written company line: "AI Realist" quadrant, augment-not-replace, and a role table that doubles as a talk and livestream calendar. ## Synthesis additions (2026-09-05 — adoption mechanics: delivery location vs internal tool friction) - [[3. Resources/Permanent Notes/Adoption Fails at the Doorway Not the Feature]] — Common Room's doorway/attention-tax argument: a capability loses to habit unless it lives on an existing routine, distinct from in-tool friction ## Synthesis additions (2026-09-05 — documentation as training data for agent recommendations) - [[3. Resources/Permanent Notes/Documentation Is Training Data and It Sets the Recommendation Prior]] — Public documentation and usage examples now set the prior for whether an AI agent recommends a platform at all — reframes DevRel's leverage in the agent era. ## Synthesis additions (2026-09-05 — assessment-first curriculum design) - [[3. Resources/Permanent Notes/Self-Reported Skill Gaps Diverge From Measured Ones So Curriculum Should Assess First]] — Engineers' felt AI skill gaps (understanding, coding with LLMs) diverged from their measured gaps (building LLM systems) -- curriculum scoped from a needs survey alone targets the wrong material. ## Synthesis additions (2026-09-05 — community signals as sales telemetry) - [[3. Resources/Permanent Notes/A Community Signal Reads as Contribution to Stewards and as a Sale Cue to Vendors]] — The same public GitHub star or forum thread reads as contribution to a community steward and as a buying signal to a vendor watching the same channel; the community's norms, not the vendor's stack, decide which reading governs. ## Synthesis additions (2026-09-05 — framing a program cut as a testable theory) - [[3. Resources/Permanent Notes/A Schedule Cut Framed as a Testable Theory Is Cheaper to Make and Cheaper to Reverse]] — Longhorn PHP's organizer named the exact attendance and cost inputs behind a schedule cut and called it a theory before the event ran, turning a shrink into a stated, reversible experiment. ## Synthesis additions (2026-09-04 — what developer education has to prove) - [[3. Resources/Permanent Notes/Adoption and Satisfaction Are Not Evidence That a Teaching Method Works]] — reading instruction spread for thirty years on teacher satisfaction and publisher revenue while the research said it failed; developer education is bought on the same two signals, which measure delivery rather than learning. ## Synthesis additions (2026-08-24 — silence as a signal) - [[3. Resources/Permanent Notes/Absence of Complaint Is Resignation Not Satisfaction]] — quiet internal clients and contributors who stopped filing issues are the same signal; it reads as satisfaction to the people who could still fix it. - [[3. Resources/Readwise/Articles/How to Redesign a Broken Delivery Flow|How to redesign a broken delivery flow]] — the diagnostic: score satisfaction *and* ask for the reason behind the score, because the reasons carried more than the numbers. A map connecting ideas about Developer Relations — what it is, how it produces value, how it measures success, what makes it sustainable, and how it fails. Started 2026-05-28 over DevRel coverage that had accumulated organically without a unifying map. - [[3. Resources/Permanent Notes/Corporate Contribution Fails on Legibility Not Goodwill]] — a DevRel-shaped fix: produce the role definitions, scopes, and return story that corporate systems require before money can move. ## Synthesis addition — 2026-08-11 - [[3. Resources/Permanent Notes/Comparison Listicles Donate AI-Search Prominence to Competitors]] — comparison content can strengthen rivals' corpus presence while diluting the publisher's own topical density. ## Synthesis additions (2026-08-11) - [[3. Resources/Permanent Notes/Content Progression Does Not Create Consent for Sales Contact]] — separates interest in progressively specific content from permission for tracking or outreach. - [[3. Resources/Permanent Notes/Technical Interviews Should Test Explanation and Tradeoffs Not Recall]] — developer-career assessment should measure review judgment and explanation once generation is cheap. ## Core Question What does effective Developer Relations look like, and how do organizations build it so that it survives the structural pressures (invisibility, measurement difficulty, talent compression) that have historically caused DevRel to burn out the people doing it and disappoint the organizations sponsoring it? --- ## Defining the Field ### What DevRel is and isn't - [[3. Resources/Literature Notes/Cultivating Developer Love through Developer Relations]] — the oxytocin/belonging mechanism behind community affect, with the caution that the same bonding can distort group perception - [[3. Resources/Literature Notes/Cultivating a Learning Culture in Organizations]] — the internal-team mirror: the psychological-safety and learning-out-loud practices DevRel builds externally are the same ones a learning culture builds inside the org - [[3. Resources/Literature Notes/Building a Career in Developer Advocacy Amanda's Story]] - [[3. Resources/Literature Notes/Building Your Brand in the Developer Community]] ### DevRel as infrastructure - [[3. Resources/Permanent Notes/DevRel as Railroad Infrastructure]] — DevRel as the connective layer between every department and the developer community; not an audience-marketing function --- ## Strategy + Frameworks ### High-level strategy - [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] — Awareness / Activation / Engagement / Retention as the discipline against vanity-metric drift - [[3. Resources/Literature Notes/The AAARRRP Developer Relations Strategy Framework]] - [[3. Resources/Literature Notes/Developing a Successful Developer Relations Strategy]] - [[3. Resources/Literature Notes/Strategies for Setting Up a Successful Developer Relations Program]] - [[3. Resources/Literature Notes/Creating a Culture of DevRel in Organizations]] ### Developer segmentation - [[3. Resources/Permanent Notes/Developer Segmentation Requires Four Filters Not One]] — Technical / User / Organization / Market filters; no one-dimensional segmentation works ### The Developer Journey - [[3. Resources/Literature Notes/The Developer Journey - Awareness to Advocacy - Literature Note]] — synthesis of multiple sources on the journey arc ### JTBD and discovery methods - [[4. Archives/Book reviews/The Jobs to Be Done Playbook]] — a practical discovery sequence: distinguish job performer, buyer, and affected people; use interviews to form hypotheses before treating outcomes as market evidence - [[4. Archives/Book reviews/Jobs to Be Done — Theory to Practice]] — Outcome-Driven Innovation’s high-rigor path for desired-outcome research; its published success rate remains an author/company claim, not an independent benchmark - [[4. Archives/Book reviews/The Jobs-to-be-Done Pyramid]] — a five-layer scaffold for product interaction, progress, role identity, image identity, and emotion; use it as a research aid, not a psychological diagnosis - [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]] — keeps JTBD outcome measures accountable to a defined outcome, method, and local evidence --- ## Measurement + Operations ### Lead measures, lag measures, vanity measures - [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] (above) - [[3. Resources/Permanent Notes/A System Failure That Looks Like a Performance Failure Never Gets Fixed]] (added 2026-06-09) — the metric-misattribution trap: a broken stack/system surfaces as missed quota and low conversion (a *people* metric), so the org "fixes" the people and the system gets a free pass. When underperformance is widespread, suspect the system before the people. Common Room data-stack audit; twin of [[3. Resources/Permanent Notes/Information Overload Is at Least as Much a Structure Problem as a Volume Problem]]. - [[3. Resources/Literature Notes/Measuring DevRel Success - Thinking Outside the Funnel]] - [[3. Resources/Literature Notes/Importance Of Measuring Developer Experience]] ### Time-to-first-value - [[3. Resources/Permanent Notes/Time-to-Hello-World Is the Critical Developer Experience Metric]] ### Operations + scale - [[3. Resources/Literature Notes/DevRel at Scale - Operations Measurement and Organizational Design - Literature Note]] — operations layer for mature programs ### Friction logging - [[3. Resources/Permanent Notes/Friction Logging Is the DevRel Equivalent of Code Review]] — the practitioner discipline of walking the journey and documenting every stumble --- ## What Marketing Looks Like for Developers - [[3. Resources/Permanent Notes/Education Is the Only Marketing That Works With Developers]] — developers don't respond to traditional marketing; education that solves real problems is the only signal that doesn't get filtered out - [[3. Resources/Literature Notes/Understanding Developer Marketing - Engage, Educate, and Empower]] --- ## Sustainability + the Pipeline Problem ### Why DevRel burns people out - [[3. Resources/Permanent Notes/DevRel Burnout Is Structural Not Personal]] — invisible infrastructure work + measurement gap = burnout pipeline. Not solvable by wellness interventions; solvable by making the work visible and measurable. - [[3. Resources/Permanent Notes/Open Source Depends on Teaching Labor That Has No Formal Home]] — added 2026-06-24; the upstream cause: peer-teaching labor (blogs, meetup talks, 11pm Discord answers) is load-bearing yet unrecognized and unfunded, so the people doing it burn out by structure ### Career path problems ### Documentation & Technical Writing - [[3. Resources/MOCs/Documentation & Technical Writing MOC]] — the docs discipline has its own map (added 2026-09-24): docs as infrastructure, docs metrics, docs that agents read, governing a docs function, the six technical-writing book reviews, and the Write the Docs Berlin 2026 event map ### Community + Sustainability - [[3. Resources/Permanent Notes/Perm · Open source sustainability fails when emotional labor is expected for free]] — projects burn on community management; emotional labor must be paid or boundaries set - [[3. Resources/Permanent Notes/Perm · WordCamp organizers should be paid, not voluntold]] — unpaid volunteers unsustainable + exclusionary; honorariums improve fairness and inclusion - [[3. Resources/Permanent Notes/DevRel Career Paths Have a Glass Ceiling Problem]] — breadth prevents depth, limiting advancement - [[3. Resources/Literature Notes/Importance of Career Path for Developer Relations Professionals]] - [[3. Resources/Literature Notes/Camunda's Career Path for Developer Relations Professionals]] - [[3. Resources/Literature Notes/The Importance of Career Laddering]] ### Should DevRel carry revenue responsibility? - [[3. Resources/Permanent Notes/DevRel Should Never Carry a Sales Quota]] — quota-bearing DevRel transforms into sales; the function that survives is no longer DevRel ### Maturity progression - [[3. Resources/Permanent Notes/DevRel Maturity Is a Five-Stage Progression Not a Binary State]] — five stages; organizations don't skip stages; misaligning stage and investment kills programs ### Timeline mismatch - [[3. Resources/Permanent Notes/DevRel Programs Take Three to Five Years to Show Results]] — annual-budget cycles produce 3-5 year program failure rates - [[3. Resources/Literature Notes/Raising the Next Generation of DevRel]] --- - [[3. Resources/Permanent Notes/Ask the Room What It Knows Before Teaching It Anything]] — when the plan cannot run, the room's actual starting point beats recovering the lesson plan. - [[3. Resources/Permanent Notes/Recent Graduates Re-Teaching a Curriculum Makes It Local]] — graduates remember what was confusing and carry the local context the designers lacked. ## DevRel Adjacent Disciplines ### Developer Experience (DX) - [[3. Resources/Literature Notes/Developer Experience in Practice]] - [[3. Resources/Literature Notes/Matches, Spoons, and the Relationship Between DX and UX]] - [[3. Resources/Literature Notes/The Developer Advocate's Guide to Addressing Product Friction]] ### Documentation & Technical Writing - [[3. Resources/MOCs/Documentation & Technical Writing MOC]] — the docs discipline has its own map (added 2026-09-24): docs as infrastructure, docs metrics, docs that agents read, governing a docs function, the six technical-writing book reviews, and the Write the Docs Berlin 2026 event map ### Community Operations + Measurement - [[3. Resources/Literature Notes/A Guide to Community Operations]] - [[3. Resources/Literature Notes/A Guide to Community Analytics]] - [[3. Resources/Literature Notes/Community Growth - Strategies and Metrics]] — Common Room's four metric categories (membership, engagement, responsiveness, business impact) and the CLG framing ### Developer Advocacy specifically - [[3. Resources/Literature Notes/Building a Career in Developer Advocacy Amanda's Story]] --- ## Compounding Pressures ### The AI compression problem - [[3. Resources/Permanent Notes/AI Compresses the Knowledge-Worker Pipeline From Both Ends]] — entry-tier DevRel work (demos, tutorials, low-context docs) is exactly what AI tools now do faster; the senior-DevRel pipeline may not survive intact unless deliberate apprenticeship infrastructure is built - [[3. Resources/Permanent Notes/AI Tools Don't Eliminate the Apprenticeship Layer They Relocate Its Cost]] — added 2026-05-28; the apprenticeship work the entry-tier tasks were the occasion for still has to happen; the funding model for producing senior judgment breaks unless deliberate apprenticeship infrastructure is built - [[3. Resources/Permanent Notes/The Recommend Layer Is Where Vendor Markets Make Their Real Decisions]] — added 2026-05-28; explains why DevRel's measurable output (recommendation-layer trust) takes years to build and why direct-to-buyer marketing systematically underperforms ### Hiring + Talent - [[3. Resources/Literature Notes/Community Engagement In Open Source 2]] — OSS community participation as an employee-satisfaction and retention lever - [[3. Resources/Literature Notes/Characteristics of Knowledge Workers]] — Kidd on what knowledge workers are and why their value lies in diversity of interpretation ### Leadership challenges - [[3. Resources/Permanent Notes/The Workhorse Trap Prevents Leadership Emergence]] — added 2026-06-28; the single-point-of-failure pattern from the open-source-checklist deep-read applied to DevRel: the advocate who "does the hard things" personally never builds the bench, so the program stays one person deep and breaks when they leave - [[3. Resources/Permanent Notes/Intent-Based Leadership Outperforms Permission-Based Leadership]] — added 2026-06-28; the structural fix for the workhorse trap — distribute authority via "I intend to" rather than concentrating decisions, so the program survives the founder - [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]] — added 2026-06-28; the same scarcity DevRel faces — the bottleneck is human attention to review/triage/support, not output, which is exactly what the workhorse trap exhausts --- ## Related MOCs - [[Open Source Governance MOC]] — DevRel and OSS governance share a structural problem (invisible infrastructure work becoming visible only when it breaks) - [[Commons & Community Governance MOC]] — community operations as a sub-discipline of community governance - [[AI Agent Safety MOC]] — adjacent infrastructure-layer concern; agent-safety patterns affect what DevRel can recommend to developer customers ## Open Questions Worth Tracking - What's the right organizational reporting structure for DevRel given that it serves Engineering / Marketing / Product / Customer Success simultaneously? No single home is correct; multi-stakeholder structures consistently underperform. - How does the AI compression of the entry-tier change DevRel hiring and apprenticeship in the next 3-5 years? See [[3. Resources/Permanent Notes/AI Compresses the Knowledge-Worker Pipeline From Both Ends]] for the framing. - What's the right level of revenue accountability for DevRel programs without crossing the line into sales-quota territory that destroys the function? - Does the Pinto et al. mentoring finding ([[3. Resources/Literature Notes/Deliberate Mentoring Accelerates OSS Onboarding - Literature Note]]) apply to DevRel team onboarding too? The structural setup is similar; the empirical question hasn't been tested. ## Synthesis additions (2026-06-11) From the 3-day Readwise review — new atoms wired in: - [[3. Resources/Permanent Notes/Enterprise Adoption Validates a Platform Through Authority Transfer]] — the trust-via-borrowed-reputation lever (CERN); distinct from education's trust-via-understanding - [[3. Resources/Permanent Notes/Developer-Tool Adoption Tracks Cognitive-Load Reduction Not Feature Count]] — ongoing-use cost for the already-onboarded; sibling of Time-to-Hello-World - [[3. Resources/Permanent Notes/Curated Mastery Conferences Serve Practitioners That Volume Conferences Cannot]] — segmentation applied to events; pay speakers; curated depth as the scarce good (Remkus de Vries) ## Synthesis additions (2026-06-11, batch 2) From the second 3-day-batch synthesis pass: - [[3. Resources/Permanent Notes/Contribution-Based Education Produces Work-Ready Developers Faster Than Credentials]] — contribution-trained pipeline cuts employer onboarding months→days; activation applied to careers ## Synthesis additions (2026-06-12) - [[3. Resources/Permanent Notes/Curated Mastery Conferences Serve Practitioners That Volume Conferences Cannot]] — reinforced 2026-06-12 by 'It's Time to Pay WordCamp Organizers and Speakers' — the organizer-side compensation case (see Lit · Pay WordCamp organizers and speakers) ## Synthesis additions (2026-06-14) - [[3. Resources/Permanent Notes/Value Gates Cadence]] — Rizel Scarlett's correction to the "post consistently" advice: consistency without value is noise; technical depth is the trust currency that makes any cadence worth maintaining; own your platform. Sharpens [[3. Resources/Permanent Notes/Education Is the Only Marketing That Works With Developers]]. ## Synthesis additions (2026-06-15) - [[3. Resources/Permanent Notes/AI Erodes the WordPress Plugin Value Props Pushing Monetization Toward SaaS and Services]] — GravityKit's Casey Burridge: AI drops support volume + can do updates, so plugin value migrates to SaaS/services; the durable moat may be distribution (being the MCP an agent reaches for). Cross-homed from [[AI & the Future of Knowledge Work MOC]]. ## Connected Literature Notes (synthesis 2026-06-17) - [[63% of Developers Engage With AI-Assisted Development]] — developer AI-adoption trend DevRel must track - [[A Guide to Community Analytics]] — measuring community health with data - [[A Guide to Community Operations]] — the community back-office function - [[6 Lessons on Using Technical RFCs as a Management Tool]] — RFCs as a transparent technical-decision practice - [[6 Best Instructional Design Tips to Develop Effective Microlearning]] — instructional-design tips underpinning DevRel education/workshops (synthesis 2026-06-17) ## Connected Literature Notes (synthesis 2026-06-18) - [[Ada Developers Academy - A Tuition-Free Coding School]] — inclusive developer-pipeline building - [[Agile Project Management in Rapid eLearning]] — instructional design for DevRel education - [[Admin Design - Introduction]] — wp-admin redesign shapes contributor onboarding/docs (backfill 2026-06-18) ## Connected Literature Notes (synthesis 2026-06-20) - [[Balancing Internal and External Activities in DevRel]] — the internal/external-balance strategy question - [[Benefits of Microlearning in Corporate Training]] — microlearning for developer education ## Permanent Notes (synthesis 2026-06-21 gap-fill) - [[Readiness Is Predicted by Behavior Over Time Not Static Attributes]] — score community readiness by behavior, not logos - [[Block Library - Introduction]] — WP block-management UX → contributor docs/onboarding (synthesis 2026-06-21) - [[Bloom’s Taxonomy Questions]] — cognitive-level questioning for developer education (synthesis 2026-06-21) - [[Book Review - "Engineering Management for the Rest of Us" by Sarah Drasner]] — leadership/values/trust for DevRel management (synthesis 2026-06-21) - [[Building Realistic Roadmaps for Tech Debt Cleanup]] — tech-debt roadmapping as a management practice (synthesis 2026-06-21) - [[The CMS Decision Turns on How a Site Is Edited Not What It Contains]] — contrast/caution: DevRel often defaults to "WordPress for everything"; this is the case for choosing static when editing won't happen. Match the tool to the editing workflow, not the content (synthesis 2026-06-21) ## Connected Literature Notes (synthesis 2026-06-26) - [[Importance Of Measuring Developer Experience]] — DevEx measurement as a DevRel instrumentation concern (orphan reconnected this sweep) - [[Importance of Career Path for Developer Relations Professionals]] — career-path clarity as a DevRel professionalization issue (orphan reconnected this sweep) ## Synthesis additions (2026-06-30 gap-fill) From Common Room (AI GTM) and Christopher Penn (vanity metrics) — both map directly onto developer-adoption measurement (swap "pipeline" for "contributor pipeline," "intent data" for community signals): - [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]] — Penn's measurement humility for the vanity-metric thread above: active-installs, Slack counts, WordCamp RSVPs, docs pageviews are textbook "non-zero" metrics, but whether any is vanity is dataset-specific — regress against retention/the real outcome before dismissing it. Sharpens [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] (map to objectives) with the test that confirms the mapping holds. Cross-homed in [[Product & Startup Instincts MOC]]. - [[3. Resources/Permanent Notes/AI's Leverage Comes From the Data Foundation Not the Model]] — Common Room's foundation-not-tool argument is the B2B mirror of DevRel attribution: GitHub stars, installs, Discord activity, docs visits live in disconnected buckets that never resolve to one human, so AI run over them is "louder, not smarter." Resolve identity and weight behavior before automating; pairs with [[3. Resources/Permanent Notes/Readiness Is Predicted by Behavior Over Time Not Static Attributes]] and [[3. Resources/Permanent Notes/A System Failure That Looks Like a Performance Failure Never Gets Fixed]]. Primary home: [[AI & the Future of Knowledge Work MOC]]. ### Accessibility (added 2026-06-30) - [[3. Resources/Permanent Notes/Accessibility Enforced at Authoring Time Beats Post-Hoc Auditing]] — the advocacy lesson from the Made Right Media case + the WordPress block-accessibility notes: stop selling accessibility as an after-the-fact audit/overlay upsell and bake it into the authoring path (block validations, required content-role attributes). Ties the three sweep accessibility Literature notes ([[3. Resources/Literature Notes/Lit · Accessibility work shapes product and culture]], [[3. Resources/Literature Notes/Lit · Block validations prevent inaccessible content at source]], [[3. Resources/Literature Notes/Lit · Block attributes require explicit content role marking for accessibility]]) to a single claim. ## Synthesis additions (2026-07-01) - [[3. Resources/Permanent Notes/Code Review Is a Human Knowledge-Transfer Ritual Not Just a Quality Gate]] — Ryan McCue's "Pull requests are for humans": review is one of the few places engineering judgment actually transfers between contributors, so agent-to-agent PRs (AI descriptions, unfiltered prompt-to-PR, feeding review comments back to an agent) hollow out the loop — and against volunteer OSS maintainers it's "outright rude." Extends the AI-compression thread (§Compounding Pressures) and pairs with [[3. Resources/Permanent Notes/Friction Logging Is the DevRel Equivalent of Code Review]]. ## Synthesis additions (2026-07-03) - [[3. Resources/Permanent Notes/Block Theme Development Has Outpaced Block Theme Adoption]] — the "we shipped it ≠ they adopted it" signal for the Themes/Training/DevRel teams: block themes are 44.2% of new WordPress.org submissions but only 8.3% of non-default installs (classic 91.7%). A supply-side win read as an ecosystem win; the adoption headwind to design around (relevant to Ollie / courtneyr-child block-theme work). Primary home: [[Open Source Governance MOC]]. ## Synthesis additions (2026-07-10) - [[3. Resources/Literature Notes/Lit · WordPress centralizes education initiatives]] — evidence for the unified WordPress.org student-education hub captured by [[3. Resources/Permanent Notes/Zet · WordPress centralizes student education programs]]; distinct from [[3. Resources/Permanent Notes/Zet · Three programs structure WordPress Education]], which records the Campus Connect, Credits, and Student Clubs taxonomy ## Connected Literature Notes (synthesis 2026-07-18 — 20-doc batch) - [[3. Resources/Literature Notes/The DevRel Show Episode 53 — Chris DeMars from TuxCare]] — DevRel as mission not team; two-way ambassadorship (users + product/org); human relationship as the AI-proof core - [[3. Resources/Literature Notes/Community & Code Episode 30 - Miriam Goldman]] — Drupal-excitement vs WordPress-exhaustion; pay-WordCamp-organizers proposal; burnout-blocks-succession catch-22 ## Connected Literature Notes (synthesis 2026-07-18 — batch 2) - [[3. Resources/Literature Notes/Writing Winning LinkedIn Content, Without AI]] — AI as editor not author preserves the voice signal readers now pattern-match as AI-written - [[3. Resources/Literature Notes/Project-Based Learning That Works in Business Education]] — test whether an assignment is genuinely applied learning by checking for a decision the learner must make and defend ## Connected Literature Notes (synthesis 2026-07-18 — batch 3) - [[3. Resources/Literature Notes/Member Spotlight — Tia Wood]] — WP community member spotlight; entrepreneurship delivering both structure and autonomy when the owner builds their own systems - [[3. Resources/Literature Notes/I Built a Workflow That Reads My Community's Slack and Writes a Week of Posts in My Voice]] — community-intelligence automation with a human-in-the-loop; AI approval gates need hard numeric caps, not just 'be selective' instructions ## Connected Literature Notes (synthesis 2026-07-21) - [[3. Resources/Literature Notes/Lit · Block attributes require explicit content role marking for accessibility]] — the developer API that declares which block fields authors can safely edit - [[3. Resources/Literature Notes/Lit · Block validations prevent inaccessible content at source]] — publish-blocking checks turn accessibility education into an enforceable authoring gate - [[3. Resources/Literature Notes/Lit · CERN chose WordPress]] — high-authority enterprise adoption gives WordPress advocates a stronger proof point than a feature list - [[3. Resources/Literature Notes/Lit · Content-only mode protects pattern structure while enabling content editing]] — a developer-experience contract that preserves structure while giving authors bounded control - [[3. Resources/Literature Notes/Lit · Ending responsive images]] — a teachable case where a removed browser constraint makes an older front-end workaround optional ## Synthesis additions (2026-07-21 — run 2) - [[3. Resources/Literature Notes/Lit · GenerateBlocks CSS mode and live preview]] — live preview changes adoption by closing the feedback loop without adding underlying capability - [[3. Resources/Literature Notes/Lit · Governance and workflows reduce risk]] — enterprise roles and approvals are the collaboration controls developer advocates must teach, not just feature checkboxes - [[3. Resources/Literature Notes/Lit · Inconsistency acknowledged commitment follows|Inconsistency acknowledged; commitment follows]] — a product evangelist's acknowledged drift captures the identity work behind sustained advocacy - [[3. Resources/Permanent Notes/Repeated Workarounds Are Unfiled Bug Reports]] — repeated configuration exceptions are passive developer feedback that product teams can mine before users file issues ## Synthesis additions (2026-07-21 — run 3) - [[3. Resources/Literature Notes/Lit · Pay WordCamp organizers and speakers]] — argues that a free ticket doesn't compensate months of skilled event labor - [[3. Resources/Permanent Notes/Perm · WordCamp organizers should be paid, not voluntold]] — treats event compensation as participation infrastructure rather than a reward after the work - [[3. Resources/Permanent Notes/Zet · Playground demos improve client feedback on themes]] — a no-setup browser trial lowers the evaluation burden for clients and stakeholders ## Connected Literature Notes (synthesis 2026-07-21 — run 4) - [[3. Resources/Literature Notes/Lit · The WordPress conference we need next]] — argues for a curated mastery conference that values depth and pays speakers - [[3. Resources/Literature Notes/Lit · Three core WordPress education programs]] — records the Campus Connect, Credits, and Student Clubs education pipeline - [[3. Resources/Literature Notes/Lit · WP Rig theme framework and ESBuild migration]] — a theme-development tool case where build-speed gains reduce adoption overhead - [[3. Resources/Permanent Notes/Zet · Three programs structure WordPress Education]] — maps the three programs that form WordPress's student and university education pipeline ## Connected Literature Notes (synthesis 2026-07-21 — run 5) - [[3. Resources/Literature Notes/Lit · WordPress 69 introduces enhanced block development capabilities]] — block bindings and Interactivity API changes expand the extension points developer education must explain - [[3. Resources/Literature Notes/Lit · WordPress contribution education for university students]] — reviewed project contributions shorten the path from university learning to employable WordPress practice - [[3. Resources/Permanent Notes/Zet · Extensible architectures enable third-party integration]] — extension points turn core capability into a surface the developer ecosystem can build against ## Connected Literature Notes (synthesis 2026-07-21 — run 7) - [[3. Resources/Literature Notes/Purpose of the 2023 Developer Relations Report]] — defines the evidence base and questions behind a field-wide DevRel benchmark - [[3. Resources/Literature Notes/Reflection on Being the Emcee at Day of Rest Conference]] — captures facilitation as skilled community infrastructure rather than stage decoration - [[3. Resources/Literature Notes/Reflections on Dealing with a Performance Improvement Plan]] — career-management evidence about expectations, power, and documented performance - [[3. Resources/Literature Notes/Running WordPress Without a Server With Adam Zieliński]] — WordPress Playground changes the first-run and teaching surface for developers ## Connected Literature Notes (synthesis 2026-07-21 — run 8) - [[3. Resources/Literature Notes/Scaling Developer Content Production at Snyk]] — documents the editorial systems needed to increase technical content without losing practitioner trust - [[3. Resources/Literature Notes/Soft Skills for Community Managers]] — names the relational skills that make technical communities workable - [[3. Resources/Literature Notes/Summary of The Cambridge Handbook of Computing Education]] — research base for designing developer education beyond tutorial production ## Connected Literature Notes (synthesis 2026-07-21 — run 9) - [[3. Resources/Literature Notes/The Evolution and Challenges of Developer Relations]] — maps how the function's organizational role and recurring constraints changed over time - [[3. Resources/Literature Notes/The Importance of Customer Obsession and Data-Driven Insights in DevRel at Vercel]] — links developer advocacy decisions to observed user friction and product evidence - [[3. Resources/Literature Notes/The Key Steps to Building a Community Mentorship Program]] — makes mentor structure and support part of the contributor-development system ## Connected Literature Notes (synthesis 2026-07-21 — run 10) - [[3. Resources/Literature Notes/The Role of Tutorials in Developer Marketing]] — working tutorials turn product education into a trust-building path toward first value - [[3. Resources/Literature Notes/Untitled 1]] — the trust triangle of authenticity, empathy, and logic supplies a practical leadership frame for technical teams and community work ## Connected Literature Notes (synthesis 2026-07-21 — run 11) - [[3. Resources/Literature Notes/WordPress Developer Relations from Joost]] — treats integrations with emerging open-source tools as active ecosystem development rather than passive compatibility work ## Connected Literature Notes (synthesis 2026-07-21 — run 12) - [[3. Resources/Literature Notes/Your First 30 Days in a New DevRel Role]] — makes listening, stakeholder mapping, and a firsthand developer-experience audit the work of a new advocate's first month ## Connected Permanent Notes (synthesis 2026-07-21 — run 16) - [[3. Resources/Permanent Notes/Event Recap Process]] — coordinates publishing and community teams across pre-event framing, live note capture, post-event synthesis, review, and follow-up updates ## Connected Permanent Notes (synthesis 2026-07-21 — run 18) - [[3. Resources/Permanent Notes/Open Source Community Scorecard]] — a sparse working artifact for coordinating community-program metrics, communications stakeholders, and follow-through ## Connected Permanent Notes (synthesis 2026-07-21 — run 24) - [[3. Resources/Permanent Notes/Zet · Boilerplate automation accelerates FSE theme setup]] — reduces repeated namespacing and theme scaffolding so agency developers can reach project-specific work sooner ## Connected Permanent Notes (synthesis 2026-07-21 — run 25) - [[3. Resources/Permanent Notes/Zet · People-first framing strengthens contributor motivation]] — uses recurring recognition and contributor spotlights to make community labor visible and reinforce participation ## Synthesis additions (2026-07-22) - [[3. Resources/Literature Notes/Creating a Culture of DevRel in Organizations]] — frames DevRel as a cross-functional company capability. - [[3. Resources/Literature Notes/Developing a Successful Developer Relations Strategy]] — maps outreach, education, advocacy, community, tooling, and measurement. - [[3. Resources/Literature Notes/Elements of a Good Technical Document]] — connects documentation clarity to developer education. - [[3. Resources/Literature Notes/Criteria for Valuable RFI Inputs]] — connects public technical consultation to structured stakeholder engagement. ## Synthesis additions (2026-07-23) - [[3. Resources/Permanent Notes/Type Compatibility Can Hide Runtime Removal]] — warns migration guidance to separate accepted type shapes from behavior that still runs. - [[3. Resources/Permanent Notes/Zet · Server-side development reduces JavaScript complexity]] — reconnects a developer-experience option for fixed, content-focused WordPress components. ## Synthesis additions (2026-07-25) - [[3. Resources/Permanent Notes/Funnel Position Predicts Which Content AI Search Extracts]] — sorts a content portfolio by extraction risk: top-of-funnel is the exposed category, lived specifics are the moat. - [[3. Resources/Permanent Notes/Republishing Into a Rival Index Recovers Traffic an Aggregator Intercepted]] — the remedy half: put assets into search systems whose business model still requires handing off the visitor. - [[3. Resources/Literature Notes/Lit · Losing half of Google traffic to AI Overviews]] — the SignLab case behind both, including the operational cost of the YouTube migration. ## Synthesis additions (2026-08-01, run 3–4) - [[3. Resources/Permanent Notes/Advocacy Converts on the Specificity of the Ask Not the Force of the Indictment]] — "contribute to WordPress" converts poorly; "join Test on Thursday, here is the Playground link, twenty minutes" converts. Specific, low-friction, recurring beats forceful. - [[3. Resources/Permanent Notes/AI's Highest-Leverage Role in Open Source Is Communicating Intent Not Generating Code]] — the content angle with real leverage is teaching people to build a janky prototype in order to *ask a question*, not to generate a plugin. - [[3. Resources/Permanent Notes/Prevented Work Is Invisible to Velocity Metrics]] — the open-source cognate of the invisible validator is the plugin-review and triage queue, measured by volume if at all, never by what it stopped. ## Synthesis additions (2026-08-01, run 5) - [[3. Resources/Permanent Notes/A Tool's Difficulty Reputation Outlives the Difficulty]] — the under-produced content angle is "this thing you gave up on has changed." Most tutorials address people who never tried; the larger audience tried and stopped, and nothing tells them the cost moved. - [[3. Resources/Permanent Notes/A Findable Resource Beats a Warning Broadcast at the Unready]] — reframes advisories, deprecation notices and migration guides: be findable at failure time rather than loud at announcement time. ## Synthesis additions (2026-08-07) - [[3. Resources/Permanent Notes/An Aggregate Score Cannot Tell You Who to Act On]] — Cosby's "it's 80 points" failure (a full ABM webinar) and Manor's "empty calories" (devrelshow ep55) are the same defect from opposite ends of the funnel: an account-level score is unusable across a team handoff because it collapses every stakeholder into one number, and the receiver needs a name, not a magnitude. - [[3. Resources/Permanent Notes/DevRel Programs Take Three to Five Years to Show Results]] — corroborated by a third, independent (vendor-content, so weigh accordingly) source: a Common Room PLG+SLG post asserts the same multi-year timeline for a new motion to compound, with zero data behind the claim — a case study in when patience arguments should and shouldn't be trusted at face value. ## Synthesis additions (2026-08-11, reconciliation) - [[3. Resources/Literature Notes/Lit · WordPress centralizes education initiatives]] — connects WordPress's centralized student and beginner programs to developer education as long-term contributor infrastructure. ## Synthesis additions (2026-08-11, GTM backlog) - [[3. Resources/Readwise/Articles/How I Grew Signups 71% in 90 Days by Running GTM Like an Engineer]] — supports system-first developer GTM, reusable launch infrastructure, and human judgment over campaign-only execution. - [[3. Resources/Readwise/Articles/AI Agents in GTM What They Should Truly Do]] — supports the existing claim that an agent's value depends on a defined job and a clean data foundation, with vendor interest explicitly retained. - [[3. Resources/Readwise/Articles/On-Brand Maintenance Mode for WordPress Block Themes]] — practical developer-education source for preserving brand and communication quality during maintenance without creating a new general claim. ## Synthesis pass — 2026-08-11 reference connections - [WordPress Playground Team Calls for Testers as New Dock-Based UI Aims](https://read.readwise.io/read/01ky6dh5mztat5v8rhsy7gz900) — a concrete testing ask whose dual-audience UI and accessibility needs connect product discovery to contributor activation. - [And now my watch has ended](https://read.readwise.io/read/01kyb9nrkqqgdnsdhffszt45pm) — documents the career impact of losing a long-tenured WordPress maintainer and preserves the source's actionable hiring ask. ## Synthesis pass — 2026-08-11 program references - [Liberating sites with Studio Code](https://read.readwise.io/read/01kyhyjtfsrhzx2yxbnz6xn7p9) — a developer-education example for teaching local WordPress workflows through a concrete build. - [Escape The Downward Spiral](https://read.readwise.io/read/01kyhyjtnv63amx5r2wxk58kbh) — a vendor talk retained as product-lifecycle and customer-education context, not promoted into a general claim. - [Your Champion Isn't Enough](https://read.readwise.io/read/01kymsbfwtjrjgmy6qsxxc14ea) — vendor guidance on buying-committee coverage that transfers cautiously to multi-stakeholder developer adoption. - [The Spirit of Open Source: Penpot's Ambassador Program](https://read.readwise.io/read/01kymvtjyncx61r5r90x84hwkc) — connects learning-cycle program design to ambassador and meetup-organizer development. ## Synthesis pass — 2026-08-11 practitioner references - [What Agency Owners Need to Know Before Buying a Plugin Business](https://read.readwise.io/read/01kyskbvbe51xwb6fmj0e8r4r7) — practitioner guidance connecting acquisition diligence to support knowledge, subscriptions, and go-to-market work. - [Where Will Cloud Native Take You?](https://read.readwise.io/read/01kyskbzc8xdbaze35wwtj3gte) — a contributor-onboarding example showing that community expertise can complement rather than duplicate maintainer skills. ## Synthesis pass — 2026-08-11 adoption references - [The CEO Goes First](https://read.readwise.io/read/01kywpan901pczce2sajs8g4vh) — a short leadership-adoption case where visible executive behavior affects the uncommitted middle, with incentive and coercion still confounded. - [Introducing BoardScribe](https://read.readwise.io/read/01kywq8agbtdg2py4jza91dmtz) — a product-education reference whose machine-recovered description highlights the difference between an accessible interface and accessible meeting content. - [The Marketing Channel AI Can't Commoditize](https://read.readwise.io/read/01kywpb11nngv6ez9pqmzsk9hk) — commercially framed referral guidance retained as evidence about voice-of-customer discovery rather than promoted into a general claim. - [Background blur arrives in Penpot 2.17](https://read.readwise.io/read/01kyysasjwcsrwhdm6ncx3xj8n) — a lean product-announcement example documenting one competitive feature gap closing. ## Synthesis pass — 2026-08-11 workflow references - [Can WordPress Studio Code Build This Website?](https://read.readwise.io/read/01kyyv1gjxf29krdr0jw8e4ya6) — a live-test teaching artifact showing AI defaults, block-binding choices, and maintenance tradeoffs. - [Silly Software, Sugar Snap Peas, and Coding in Gen Z Slang](https://read.readwise.io/read/01kyyvg607318kb4tnxmnn8780) — a podcast example of agent-to-agent skill transfer and the thin control boundary around shared developer tools. - [GitHub docs to WordPress with DocsPress](https://read.readwise.io/read/01kz6h7t1kxar65x4wtzmm2mnm) — a developer-documentation publishing workflow retained as practitioner reference. ## Synthesis pass — 2026-08-11 ecosystem study - [Death of a Software Ecosystem: a Developer Relations perspective](https://read.readwise.io/read/01kz7w1arb8n05hp591zzwe5cz) — exploratory ecosystem-decline research retained as a DevRel case rather than generalized beyond its evidence. ## Synthesis pass — 2026-08-11 contributor and practice references - [The Rise of the Design Engineer](https://read.readwise.io/read/01kz92mn5vycz7tfme1df9g7tm) — practitioner evidence about design engineering, testing, and coding-agent efficiency. - [Why It Took Me 16 Years to Contribute to WordPress](https://read.readwise.io/read/01kz939vyepatf6sb61ks9rx60) — first-person evidence about contributor onboarding, mentorship capacity, non-code paths, and accountable AI review. - [#228 – Priscilla Collado Ramirez on Reducing WordPress Beginner Anxiety](https://read.readwise.io/read/01kz940w4syvbgxfs0mdaz4qkr) — connects beginner choice architecture, safe practice, and learning support to WordPress education. - [Built It. Shipped It. Nobody Knows How It Works Anymore.](https://read.readwise.io/read/01kzcf32j4qzqzdz33r1rn0mfz) — vendor-authored operations guidance retained for its distinction between defining plays and automating workflows. ## Synthesis pass — 2026-08-11 product-community references - [Beyond Expertise: The AI Technique That Breaks Your Skill Ceiling](https://read.readwise.io/read/01kzcf2e1jp67wa5vds6c71a4j) — a WordPress product-talk example of an AI-assisted research and evidence loop. - [Quick Look: What Is ThinkRank?](https://read.readwise.io/read/01kzcf2vzvs3nk4v0xy3bmdw53) — a plugin overview connecting AI SEO claims to the risk of MCP write access. - [Penpot AI Kit: agent skills for your design files](https://read.readwise.io/read/01kze5580cdb0q65m2ygzg73we) — a skills-as-artifact example whose scaffolding claim is stronger than its unevidenced capability claim. - [Carousel Designer](https://read.readwise.io/read/01kzgvzyhy088q9b8v6aps9686) — a WordPress product demonstration retained as a practitioner reference while full analysis remains pending. - [Should You Sell on the WooCommerce Marketplace?](https://read.readwise.io/read/01kzgw00bd9dpv45593j2hyxpf) — a two-sided marketplace discussion retained for WordPress product and channel strategy. ## Synthesis pass — 2026-08-11 final reference set - [Guardrails, not gates: Scaling juniors in the AI era](https://read.readwise.io/read/01kzp0p3jgq4qzd0dn8742d119) — an 18-second teaser retained only as a pointer to a fuller junior-development talk if it can be located. - [Zero to Agent in 30 Minutes](https://read.readwise.io/read/01kzp0nghgb75zm5pv524mgp25) — a tutorial example connecting model quality, context requirements, and agent-skill scaffolding. - [The AI-augmented leader](https://read.readwise.io/read/01kzp0p15znbkrsn9n0jtasb2v) — a truncated leadership talk retained for its time-audit and delegation framing, not as evidence of the missing system. - [Don't Use Next.js Without These 7 Skills](https://read.readwise.io/read/01kzp0nvy8kfxvrr86fhq63bb4) — a skills-plus-tools example supporting the practical role of explicit context in developer enablement. - [Agile Leadership](https://read.readwise.io/read/01kzp1fgrawrv8hz3wjxsp9qxj) — connects leadership foundations to delegation and maintainer-contributor trust. - [I'm Unemployed. What Do I List On Linkedin?](https://read.readwise.io/read/01kzp31w855tfd61630jkygr1w) — practical career guidance favoring a skills-focused headline over an employment-status label. - [Design tokens just got easier in Penpot 2.17](https://read.readwise.io/read/01kz92mdy5g6yc9e99gmjfzrnp) — a concise product-education example documenting Penpot's typography-token workflow. ## Synthesis additions (2026-08-13) - [[3. Resources/Literature Notes/A DevRel-Led Funnel That Puts Developers First - Literature Note]] — Adato's four-stage conversational funnel (DevRel → PMM → Demand Gen → Sales); reframes the "where should DevRel report" debate as a handoff-coherence question instead of an org-chart question. - [[3. Resources/Permanent Notes/Funnel Stages Run on Earned Permission]] — the generalizable claim: each stage's escalation must be licensed by the audience's own observable engagement with the previous stage, not asserted in advance. ## Synthesis additions (2026-08-16) ### Interview assessment + AI pairing - [[3. Resources/Literature Notes/Coding Interviews in the AI Era - Beyond LeetCode for Career Growth]] — companion literature note for [[3. Resources/Permanent Notes/Technical Interviews Should Test Explanation and Tradeoffs Not Recall]]; ports the second, previously-uncaptured claim - [[3. Resources/Permanent Notes/Always-Available AI Pairing Decouples Output-Pairing From Social-Pairing]] — always-on AI pairing satisfies the output half of pairing while leaving the relationship-building half unmet ### Lead scoring - [[3. Resources/Literature Notes/You're Scoring Leads Like It's 2015]] — signal taxonomy and derive-your-own-signature method behind [[Readiness Is Predicted by Behavior Over Time Not Static Attributes]] (already mapped above) ### Contribution pipelines + education programs - [[3. Resources/Literature Notes/WordPress Contributor Dashboard Gets Customizable Ladders for Make Teams in First Major Update Since Pilot Launch]] — customizable Make-team ladders extend the contribution-pipeline thread - [[3. Resources/Permanent Notes/Team-Defined Contribution Metrics Beat One Fixed Yardstick]] — each Make team sets its own progression criteria rather than inheriting one global ladder - [We Planned for 10 Ambassadors. We're Welcoming 138.](3.%20Resources/Literature%20Notes/We%20Planned%20for%2010%20Ambassadors.%20We're%20Welcoming%20138..md) — an ambassador program's scaling story under sudden demand - [[3. Resources/Permanent Notes/A Published Quality Bar Scales Better Than a Headcount Cap]] — publishing the acceptance bar scales a volunteer program further than capping the roster does - [[3. Resources/Literature Notes/How WordPress Education Programs Are Growing (WP Tavern 222)]] — distinct source from the vault's existing three-programs note, connects to public-credit and pipeline notes instead of repeating them - [[3. Resources/Permanent Notes/Open Source Education Works as a Three-Stage Contribution Funnel]] — awareness, guided practice, and independent contribution as a repeatable funnel shape - [[3. Resources/Literature Notes/Why It Took Me 16 Years to Contribute to WordPress]] — first-person contributor-onboarding account: event discovery, mentorship, and non-code paths - [[3. Resources/Permanent Notes/Event Discovery Without Onboarding Produces False Mental Models]] — finding an event isn't the same as understanding how to participate in it - [[3. Resources/Permanent Notes/Mentorship Capacity Is Retention Infrastructure Not Volunteer Bonus]] — mentor bandwidth is a hard constraint on contributor retention, not a nice-to-have - [[3. Resources/Literature Notes/228 – Priscilla Collado Ramirez on Reducing WordPress Beginner Anxiety]] — beginner choice architecture and safe-practice design for WordPress education - [[3. Resources/Permanent Notes/Choice Becomes Instruction Only With a Named Default]] — offering options only reduces anxiety when one option is named as the safe default - [[3. Resources/Permanent Notes/Recoverable Action Produces Confidence Reassurance Does Not]] — confidence comes from knowing an action can be undone, not from being told not to worry ### Vendor GTM + sales content - [[3. Resources/Literature Notes/The AI SDR Playbook]] — vendor content, flagged as such throughout - [[3. Resources/Permanent Notes/Automation Amplifies a Foundation Rather Than Fixing It]] — automating a sales motion scales whatever foundation already exists, sound or not; companion to [[3. Resources/Permanent Notes/A System Failure That Looks Like a Performance Failure Never Gets Fixed]] - [[3. Resources/Literature Notes/How to Find the Real Buying Committee (Common Room recap)]] — recap webinar; core claim already covered by [[3. Resources/Permanent Notes/An Aggregate Score Cannot Tell You Who to Act On]] - [[3. Resources/Literature Notes/Accounts Don't Buy. People Do. (full webinar)]] — primary source for the recap above, verified to contain a competitive-context confound the recap omits - [[3. Resources/Permanent Notes/Access Asymmetry Gates One Channel While Leaving Another Open]] — a buying committee's blocked channel doesn't mean every channel is blocked - [[3. Resources/Permanent Notes/A Blocker Is Often a Procedural Checklist Not a Persuadable Opinion]] — some stakeholder objections are compliance boxes to check, not minds to change - [[3. Resources/Permanent Notes/A Summary of a Hedged Source Strips the Hedge]] — a recap of a caveated source routinely drops the caveats, verified by direct comparison - [[3. Resources/Literature Notes/Stop Guessing How to Use AI to Distinguish Real KPIs from Vanity Metrics]] — missing literature note for an existing permanent; links to [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]] rather than duplicating it - [[3. Resources/Literature Notes/AI Go-to-Market Strategy (Common Room)]] — both candidate claims already exist as permanents ([[3. Resources/Permanent Notes/AI's Leverage Comes From the Data Foundation Not the Model]] and [[Readiness Is Predicted by Behavior Over Time Not Static Attributes]]); linked, no new permanents needed - [[3. Resources/Literature Notes/The Motion Is New. The Team Needs to Grow With It]] — third Common Room document in the vault; evidentiary weaknesses noted throughout - [[3. Resources/Permanent Notes/A Cross-Functional Motion Without a Named Owner Inherits Its Hosts Priorities]] — a motion that spans teams defaults to whichever team happens to host it unless someone is named owner - [[3. Resources/Literature Notes/Your Champion Isn't Enough]] — formalizes an earlier bare reference into a full deep-read - [[3. Resources/Permanent Notes/The Unrepresented Role Predicts Failure Better Than the Dormant One]] — a stakeholder role with no advocate in the room predicts deal failure better than a quiet advocate does ### Community management - [[3. Resources/Literature Notes/Digital Evangelism Creating Community with Social Media]] — UCC church-communications webinar; mainstream, cross-applies directly to DevRel community management - [[3. Resources/Permanent Notes/A Collective Voice Signals a Living Community Not One Broadcaster]] — many voices posting signals an active community; one broadcaster signals a marketing channel - [[3. Resources/Permanent Notes/Intentional Engagement Builds Durable Community Better Than Reach]] — engagement depth with fewer people compounds; reach without engagement doesn't ### AI dev tooling (WordPress Studio, Playground, MCP) - [[3. Resources/Literature Notes/WordPress Studio + MCP - A Better AI Workflow]] — colon replaced with ' - ' in filename for filesystem safety - [[3. Resources/Permanent Notes/Agent Tooling Earns Adoption by Augmenting Existing Workflows]] — agent tooling gets adopted when it slots into a workflow developers already run, not when it replaces the workflow - [[3. Resources/Literature Notes/How to use Blueprints in WordPress Studio]] — Blueprint-based environment setup - [[3. Resources/Permanent Notes/Reproducible Environments Encode Repeated Setup as Config]] — turning manual setup steps into a config file is what makes an environment reproducible - [[3. Resources/Literature Notes/WordPress Studio MCP (Jonathan Bossenger)]] — disambiguated by author suffix from a separate WordPress Studio MCP video - [[3. Resources/Permanent Notes/Agentic Tooling Shifts the Developer From Author to Editor]] — agent-driven scaffolding moves the developer's role from writing code to reviewing and directing it - [[3. Resources/Literature Notes/Using WordPress Studio to speed up testing 7.1]] — deep-read with a clear atomic split between generated and real-use testing - [[3. Resources/Permanent Notes/Generated Test Fixtures Are Not Evidence Until Independently Validated]] — an AI-generated test fixture proves the test ran, not that the behavior is correct - [[3. Resources/Permanent Notes/Real-Use Testing and Constructed Fixtures Catch Different Bug Classes]] — the two testing modes are complementary, not substitutes for each other - [[3. Resources/Literature Notes/New Playground UI]] — every claim atom already covered by existing permanents (connect, not create); literature note itself was the missing piece - [[3. Resources/Literature Notes/Debug WordPress Like a Pro (Xdebug with WordPress Studio)]] — Studio quietly removed Xdebug's compile-and-configure setup pain; Richmond only learned this from a colleague at Contributor Day, not from documentation ### Content quality + SEO - [[3. Resources/Literature Notes/WPBeginner Collapse — Outdated Content, Not Just Promotion (EEAT)]] — cross-linked to the existing Discipleship Deficit note for its shared small-sample evidentiary pattern - [[3. Resources/Permanent Notes/Unmaintained Tutorial Content Is an SEO and Safety Liability]] — a tutorial that stops being updated becomes both a search liability and a security liability - [[3. Resources/Permanent Notes/A Small Sample Cannot Prove a Sitewide Decay Claim]] — a handful of stale examples doesn't establish that a whole site's content has decayed - [[3. Resources/Literature Notes/GitHub docs to WordPress with DocsPress]] — formalizes an earlier bare reference; two of three atoms already covered by existing notes - [[3. Resources/Permanent Notes/Unclear Setup Docs Force a Security Decision Onto the User]] — when setup documentation doesn't specify a security posture, the user makes that call by default, usually without realizing it ### Accessibility - [[3. Resources/Literature Notes/How Made Right Media Convinced Clients to Embrace Accessibility]] — the shift-left claim already lives in [[3. Resources/Permanent Notes/Accessibility Enforced at Authoring Time Beats Post-Hoc Auditing]]; this adds the sales-framing claim - [[3. Resources/Permanent Notes/Accessibility Sells as Stewardship Tied to a Persona Not an Upsell]] — accessibility sells better framed as care for a named user persona than as an add-on service - [[3. Resources/Literature Notes/Open Source Accessibility What You're Getting Wrong]] — links to the parallel Automattic-tracker security-dependency note - [[3. Resources/Permanent Notes/Dependency Properties Become Product Properties Regardless of Application Effort]] — a dependency's accessibility gaps become the product's accessibility gaps no matter how carefully it's used - [[3. Resources/Permanent Notes/Excluding People From Contribution Excludes Them From the Career It Confers]] — an inaccessible contribution path is also a blocked career path - [[3. Resources/Literature Notes/What's new in Gutenberg 23.6]] — make.wordpress.org release notes; two distinct permanent claims - [[3. Resources/Permanent Notes/Stabilization Is the Accessibility Deadline Not the Finish Line]] — the accessibility bar has to be met by feature stabilization, not treated as post-launch cleanup - [[3. Resources/Permanent Notes/Variations Beat New Blocks for Shipping Optional Behavior]] — shipping optional behavior as a block variation carries less adoption overhead than shipping a new block ### Code review + PR practice - [[3. Resources/Literature Notes/Pull Requests Are for Humans]] — deep-read distinct from the existing McCue code-review note, with its own permanent candidate - [[3. Resources/Permanent Notes/Automating Both Ends Of A Review Collapses Its Value]] — a review where both the author and the reviewer are AI-assisted stops functioning as a knowledge-transfer check - [[3. Resources/Literature Notes/Beyond Pull Requests - Quantifying the ROI of InnerSource]] — speaker/company names unreliable in the auto-transcript, flagged in the note - [[3. Resources/Permanent Notes/A Delivery-Throughput Metric Cannot See Whether Knowledge Spread]] — a token- or PR-throughput leaderboard measures delivery speed, not whether anyone actually learned the codebase ### Adoption + technology diffusion data - [[3. Resources/Literature Notes/The State of WordPress Themes Report Reveals a Gap Between Block Theme Development and Adoption]] — data-dense source, four claim atoms - [[3. Resources/Permanent Notes/Technology Availability Precedes User Adoption By Years]] — a capability being shippable and a capability being adopted are separated by a multi-year lag, not a launch event ### Events + programs - [[3. Resources/Literature Notes/Episode 133 - Until Next Time (CHAOSS Cast)]] — sunset/farewell episode; auto-transcript garbled some numbers, flagged for verification - [[3. Resources/Permanent Notes/Community-Owned Programs Outlast Personality-Led Ones]] — a program tied to one founder's continued presence is more fragile than one the community itself owns - [[3. Resources/Literature Notes/Inside WordCamp US 2026 — Lead Organizers on Hitting Reset]] — filename shortened for filesystem hygiene; full title retained in source_title - [[3. Resources/Permanent Notes/Widen The Funnel When Your Core Shrinks]] — when the core organizer base shrinks, the fix is broadening entry points rather than working the existing core harder - [[3. Resources/Literature Notes/WordCamp US 2026 Publishes Schedule With Expanded AI Programming]] — distinct from two other existing WCUS 2026 literature notes; no dedicated WCUS MOC exists, so homed here and in the AI MOC - [[3. Resources/Permanent Notes/Flagship Event AI-Track Size Signals Ecosystem Adoption Momentum]] — the size of a flagship event's AI-focused track is a readable proxy for ecosystem-wide adoption momentum - [[3. Resources/Literature Notes/7 Reasons to Attend WordCamp US 2026 in Phoenix]] — no dedicated WordCamp US MOC exists; homed here and in the WordCamp Europe 2026 MOC - [[3. Resources/Permanent Notes/Recorded Sessions Shift In-Person Event Value to What Recording Cannot Capture]] — once sessions are recorded, in-person attendance value concentrates in what a recording structurally can't reproduce - [[3. Resources/Literature Notes/Milana Cap on WordCamp Belgrade, Documentation Tooling, and Open Source Sponsorship]] — full Refactor-Appendix deep-read - [[3. Resources/Permanent Notes/Schedule Design Is a Volunteer-Welfare Lever Not Just an Attendee One]] — event schedule design affects volunteer burnout risk as much as attendee experience - [[3. Resources/Permanent Notes/AI Documentation Pipelines Need an Explicit Authority Source]] — an AI documentation pipeline needs a named authoritative source or it will confidently document the wrong thing; links to [[The Maker Should Not Grade Its Own Homework]] ### DevRel practice + career - [[3. Resources/Literature Notes/Neurodiversity, DevRel Careers & OpenTelemetry]] — ported from an existing deep-read - [[3. Resources/Permanent Notes/DevRel Value Depends On Organizational Latitude, Not Talent]] — a DevRel practitioner's impact is bounded more by the latitude the org grants than by individual skill - [[3. Resources/Literature Notes/Dear Andy Getting Executive Buy in for OKRs]] — ported from an existing deep-read notes field - [[3. Resources/Permanent Notes/A Watchable Pilot Earns Buy-In Faster Than ROI Proof]] — executives buy into a small demonstrable pilot faster than they buy into a projected-ROI argument - [[3. Resources/Literature Notes/How I Grew Signups 71% in 90 Days by Running GTM Like an Engineer]] — formalizes an earlier bare reference into a full literature note - [[3. Resources/Permanent Notes/Systems-First GTM Compounds Where Campaign-First GTM Does Not]] — reusable GTM infrastructure compounds across launches; one-off campaigns reset to zero each time - [[3. Resources/Literature Notes/devrelshow episode 52 - Joel Hans from ngrok]] — the trust prerequisite for experimental DevRel work, distinct from the vault's existing DevRel-measurement notes - [[3. Resources/Permanent Notes/DevRel Autonomy Requires Leadership Trust Not Just Budget]] — a DevRel program needs leadership's trust to run experiments, which budget alone doesn't buy - [[3. Resources/Permanent Notes/Internal Advocacy Needs a Build-Break-Report Ritual]] — a recurring build-break-report ritual is what makes internal advocacy durable; links to [[3. Resources/Permanent Notes/Friction Logging Is the DevRel Equivalent of Code Review]] and [[3. Resources/Permanent Notes/Time-to-Hello-World Is the Critical Developer Experience Metric]] (literature note for this source already exists in the MOC as "The DevRel Show Episode 53 — Chris DeMars from TuxCare," so no duplicate literature-note line added here) - [[3. Resources/Literature Notes/devrelshow ep55 -- Gabriel L. Manor, Permit.io]] — held back two n=1 practitioner-anecdote claims pending corroboration - [[3. Resources/Permanent Notes/Community Work Deserves the Same Dashboard Discipline as Production Software]] — community programs deserve the same visible metrics dashboard that production software gets by default - [[3. Resources/Permanent Notes/Recovery Time After Public-Facing Work Is a Scheduling Requirement]] — public-facing advocacy work needs recovery time built into the schedule, not treated as free capacity - [[3. Resources/Literature Notes/DevRel in 2026 (Thematic Shifts, Product-Centric Advocacy, Coding Agents)]] — links to [[3. Resources/Permanent Notes/DevRel Maturity Is a Five-Stage Progression Not a Binary State]] as a contrasting periodization - [[3. Resources/Permanent Notes/DevRel Artifacts Must Match How Developers Consume Information]] — a DevRel artifact's format has to match how developers actually consume information, not how the org prefers to publish it ### AI workforce sentiment + burnout - [[3. Resources/Literature Notes/Why the tech workforce is quietly splitting in two - Annual AI sentiment survey (Noam Segal)]] — a companion doc's permanent note already covers workload inflation; only the uncaptured AI-identity-split claim is new here - [[3. Resources/Permanent Notes/AI Identity Shift Outranks Every Pre-AI Predictor of Work Sentiment]] — how a worker's AI-era identity shifted predicts their work sentiment better than any pre-AI demographic or role factor - [[3. Resources/Literature Notes/The Work No One Sees (Carl Alexander)]] — links to existing AI/burnout notes after verifying fit - [[3. Resources/Permanent Notes/Masking's Cost Scales Inversely With Its Visibility]] — the less visible the masking work, the higher its hidden cost - [[3. Resources/Permanent Notes/Awareness Without Agency Does Not Produce Sustainability]] — knowing about a sustainability problem doesn't fix it without the agency to act on that knowledge - [[3. Resources/Literature Notes/Escape The Downward Spiral (LifterLMS-Woody)]] — formalizes an earlier bare reference; AI-infrastructure claims flagged as unsourced - [[3. Resources/Permanent Notes/Proximity to Generous People Is an Upward-Spiral Input]] — being near generous people is itself an input to an upward spiral, not just a byproduct of one ### Ecosystem health + platform lifecycle - [[3. Resources/Literature Notes/Death of a Software Ecosystem A Developer Relations (DevRel) Perspective]] — academic SBES paper (Windows Phone / Stack Overflow); dataset unit and "vital signs" metrics flagged as needing verification - [[3. Resources/Permanent Notes/A Platforms Developer Experience Includes Its Migration Path When Support Ends]] — a platform's developer experience includes how well it lets developers leave when support ends, not only how well it treats them while it's alive ### Learning environments + advocate development - [[3. Resources/Literature Notes/1 Year, 15 Certs, a Raspberry Pi Home Lab (Golden Kubestronaut)]] — links to WordPress Playground as the ecosystem analogue - [[3. Resources/Permanent Notes/A Learning Environment Must Be Destroyable to Teach]] — a practice environment only teaches effectively if the learner can destroy and rebuild it without consequence - [[3. Resources/Literature Notes/Where Will Cloud Native Take You]] — formalizes an earlier bare reference; two new permanents - [[3. Resources/Permanent Notes/A Contributor's Value Is Expertise the Maintainer Lacks]] — a contributor's value to a project is measured by the expertise gap they fill, not by seniority - [[3. Resources/Permanent Notes/Communities With One Entry Path Recruit Only One Temperament]] — a single on-ramp design selects for one kind of contributor and screens out every other disposition - [[3. Resources/Literature Notes/The Spirit of Open Source Penpot's Recipe of Ambassador Program]] — formalizes an earlier bare reference; two new permanents - [[3. Resources/Permanent Notes/A Shared Artifact Outlasts the Activity That Produced It]] — the artifact a community activity produces keeps working after the activity itself has ended - [[3. Resources/Permanent Notes/Not Yet Knowing the Topic Makes a Better Advocate Than Expertise]] — someone recently new to a topic can advocate for it more relatably than an expert who's lost the beginner's-eye view ### Adoption signals (roundups) - [[3. Resources/Literature Notes/'I Only Do Puns on Porpoise' - This Week in WordPress 382]] — the retention/education claim already lives in [[3. Resources/Permanent Notes/A Contribution Pipeline Needs a Defined Next Step After Training]], linked instead of duplicated - [[3. Resources/Permanent Notes/Adoption Is a Repeated-Task Outcome Not a Visual-Polish Outcome]] — a feature gets adopted when it fits a task people repeat, not because its interface looks polished - [[3. Resources/Permanent Notes/Recipient-Side Scanners Can Dominate a Launch's First Traffic Wave]] — automated recipient-side scanners can be the majority of a launch's first traffic spike, distorting early read on real interest ### AI content skills - [[3. Resources/Literature Notes/Almost Timely News How To Expand and Improve Content with AI, Part 1]] — distinct from five other existing "Almost Timely News" literature notes (different episode) - [[3. Resources/Permanent Notes/Gap-Analysis Prompting Is a Distinct Skill From Generation Prompting]] — prompting AI to find the gap in existing content is a different skill from prompting it to generate new content ### AI adoption under competitive pressure - [[3. Resources/Literature Notes/Gutenberg Changelog 133 (Gutenberg 23.6 Release and WordPress 7.1)]] — Imokol's first-person account of AI-tool adoption driven by team shipping-speed pressure rather than persuasion - [[3. Resources/Permanent Notes/Competitive Velocity Converts Tool Adoption Into a Condition]] — when output speed is directly comparable across competitors, non-adoption carries a visible cost and adoption stops being a preference ### Editor architecture + breaking changes - [[3. Resources/Literature Notes/Iframed Editor Changes in WordPress 7.1]] — WordPress 7.1 always iframes the post editor, removing `apiVersion` as a self-declared readiness flag from the decision path entirely; cross-linked to the existing 2026-08-11 permanent notes on predictable breakage and silent failures rather than duplicating them ### AI content tooling + coding-agent practice (synthesis 2026-08-16, batch 2) - [[3. Resources/Literature Notes/Garofalo Details How AI Writes WordPress Social Content, Open Sources the Toolkit]] — no new permanents; both candidate claims were already promoted on 2026-07-05, linked here instead of duplicated - [[3. Resources/Literature Notes/How to Use Claude AI for Coding - Master Claude Code in 30 Minutes (Boris Cherny)]] — full 18/23-section deep-read; the strongest claim (feedback-loop-scales-quality) already existed as a permanent with no literature note, now linked - [[3. Resources/Permanent Notes/Ask The Codebase Questions Before Editing It]] — the one genuinely uncaptured claim from the Cherny deep-read: have the agent question the codebase before editing it, not just after ### Event marketing measurement (synthesis 2026-08-16) - [[3. Resources/Literature Notes/How Effective Are Our Advertising Efforts for WordCamps]] — ported from an existing full deep-read; links to [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]] and [[3. Resources/Permanent Notes/The Four Objectives Framework Replaces Vanity Metrics in DevRel]] - [[3. Resources/Permanent Notes/Optimizing Spend Requires Measuring Incremental Outcomes Not Reach]] — spend optimization has to be judged against incremental outcomes it caused, not against raw reach ### Community teaching + portability (synthesis 2026-08-16) - [[3. Resources/Literature Notes/Community + Code Episode 28 - Carrie Dils]] — FAIR/TYPO3/composer deep-read; two of four claim atoms already generalized by existing permanents (FAIR federated distribution, portability proven by a second implementer) - [[3. Resources/Permanent Notes/Teaching a Concept Cements Understanding Better Than Consuming It]] — explaining a concept to someone else locks in understanding more than passively consuming it did - [[3. Resources/Permanent Notes/A Site Owner Should Never Be Forced to Become a Developer]] — portability and tooling choices should preserve a non-developer site owner's ability to operate their own site ### AI-assisted learning tools (synthesis 2026-08-16) - [[3. Resources/Literature Notes/AI News NotebookLM Gemini Study Notebooks Claude Design 2.0]] — full 18-section deep-read; the P1 candidate (in-context assistants lower adoption barriers) already existed from a prior partial run, linked rather than duplicated - [[3. Resources/Permanent Notes/In-Context AI Assistants Lower the Adoption Barrier More Than Standalone Apps]] — an AI assistant embedded in the tool a developer already uses gets adopted faster than the same capability shipped as a separate app - [[3. Resources/Permanent Notes/A Diagnostic Quiz Before Content Generation Tailors the Learning Path]] — a short diagnostic quiz run before generating learning content lets the content target the learner's actual gap instead of a generic starting point ### Ecosystem decline + governance tradeoffs (synthesis 2026-08-16) - [[3. Resources/Literature Notes/'How the sausage is made' - This Week in WordPress 378]] — the velocity-vs-safety carve-out (P2) overlaps closely with an existing note from a different source, linked instead of duplicated; only the multi-causal-decline claim (P1) was new - [[3. Resources/Permanent Notes/Platform Sustainability Is a Sum of Independent Pressures Not One Cause]] — a platform's declining health is usually the sum of several independent pressures, not one root cause ### Documentation restructuring (synthesis 2026-08-16) - [[3. Resources/Literature Notes/Proposal - Restructure the Community Team Handbooks]] — full deep-read, including a strong comment thread treated as first-class evidence per the source's own framing - [[3. Resources/Permanent Notes/Documentation Restructure Decides Deduplication at Audit Not After]] — a documentation restructure has to resolve duplicate content during the audit pass, not defer the decision to after the new structure ships ## Synthesis additions (2026-08-18, developer marketing and training) - [[3. Resources/Literature Notes/145 Marketing as Engineering]] — Laravel's marketing team shipping real apps via AI agents, from the *Mostly Technical* podcast. - [[3. Resources/Permanent Notes/Sloppy Internals Are an Acceptable Trade for Output Speed Within a Bounded Internal-Tool Scope]] — for internal-only tooling, code quality can be traded for output speed without the tradeoff extending to customer-facing systems. - [[3. Resources/Literature Notes/Building Training Systems, Not Sessions Andrew Adam]] — training as a maintained shared system rather than a one-time event. - [[3. Resources/Permanent Notes/Training as a System Compounds Where a Session Decays]] — training holds value only as a maintained shared system; a one-time session's value decays immediately. ## Synthesis additions (2026-08-21) - [[3. Resources/Literature Notes/Building Trust Inside the WordPress Advanced Professional Developer Certification (Klaus & Dr. Leslie)]] — WordPress VIP + Criterion's psychometric case for certification (job-relatedness, secure administration, path-independence) as a way to earn employer trust rather than just add another badge. ## Book-review additions (2026-08-22) Five completed Work the Book reviews (2026-08-17 and 2026-08-22) that named this MOC in their frontmatter but had no link back from it. ### DevRel practice - [[4. Archives/Book reviews/Effective DevRel]] — Kurtis Kemple (Apress, 2026), 3.5/5. The attempt to join developer journeys, content, feedback, business reporting, and team design into one operating system. Keep the journey audits, blank-environment documentation tests, closed feedback loops, and explicit capacity decisions; discount the passages that attach business certainty or numeric precision to practitioner experience. Reinforces [[3. Resources/Permanent Notes/Friction Logging Is the DevRel Equivalent of Code Review]], [[3. Resources/Permanent Notes/Time-to-Hello-World Is the Critical Developer Experience Metric]], [[3. Resources/Permanent Notes/DevRel Value Depends On Organizational Latitude, Not Talent]], and [[3. Resources/Permanent Notes/DevRel Burnout Is Structural Not Personal]]. - [[4. Archives/Book reviews/Developer Relations Activity Patterns]] — Neward, McAllister, Neal, and Woodruff (Apress, 2026), 3.5/5. A named catalog of 37 recurring activities (Office Hours, Reference Documentation, Ambassadors, Open-Source Project, Customer Check-In, and the rest) with their resource demands. Its contribution is shared vocabulary for deciding *what to do*, not a validated measurement system — many of its suggested metrics record output or attention without establishing developer progress or business causality, so pair it with the measurement cautions under "Lead measures, lag measures, vanity measures" above. ### Documentation as DevRel infrastructure Three docs books arrived together and are best read as one argument at three altitudes — organizational, engineering, and editorial. - [[4. Archives/Book reviews/The Product is Docs]] — Christopher Gales and the Splunk Documentation Team (2nd ed., 2020), 3.5/5. The *organizational* case: documentation is product work that discovers requirements, tests workflows, exposes poor design, and carries customer evidence across team boundaries. Strong on integrating writers into product work, defining audiences, and closing feedback loops. Its ratios, remote-work advice, and measurement examples are one enterprise team's experience, not a comparative study. - [[4. Archives/Book reviews/Docs Like Code]] — Anne Gentle (2nd ed., 2017, CC BY-SA), 3.5/5 overall but 4.5/5 for the operating model and 2/5 for current implementation guidance. The *engineering* case: source in version control, small reviewable changes, automated deterministic checks, required human technical review, repeatable publishing. The model holds; the GitHub Pages tutorial, auth instructions, branch names, and Swagger-era API survey are historical. - [[4. Archives/Book reviews/Modern Technical Writing]] — Andrew Etter (2016), 3.5/5. The *editorial* case: research-first workflow, task focus, minimum useful scope, frequent publishing. Compressed enough that [[4. Archives/Book reviews/Docs for Developers]] supplies the research and maintenance methods it omits. Reject its dismissal of novice readers and its silence on localization and non-developer contribution paths. All three share the same blind spot, which is worth stating once: accessibility, contributor safety, and the concentration of publishing power in repository permissions are treated as polish rather than release gates. That connects them to [[3. Resources/Permanent Notes/Format Choice Is an Accessibility Control Exercised Before Remediation]] and [[3. Resources/Permanent Notes/Contribution Pathways Must Be Documented Not Left Emergent]], and extends the "Documentation restructuring (synthesis 2026-08-16)" thread above. ## Synthesis additions (2026-08-28 — visibility without authority) Jono Alderson's argument is about SEO and is not about SEO. It describes the structural position every horizontal function occupies — broad visibility across systems, narrow authority over any of them — and traces what accumulates there. Read as a diagnosis of DevRel, it explains why competence makes the problem worse rather than better. - [[3. Resources/Permanent Notes/A Reliable Cleanup Crew Removes the Reason to Stop Making the Mess]] — the keystone. A function that reliably absorbs failures it cannot prevent is the mechanism keeping those failures affordable, so its competence is what stops the upstream fix from being funded. Pairs with [[3. Resources/Permanent Notes/DevRel Value Depends On Organizational Latitude, Not Talent]]: latitude is not merely withheld, it is actively made unnecessary. - [[3. Resources/Permanent Notes/Decomposing a Capability Gap Into Tickets Makes It Closeable and Permanent]] — why a horizontal team's throughput can rise every quarter while the thing it exists to fix does not move. Twenty instances of one missing capability become twenty closeable tickets, and closing them is what keeps the capability unfunded. - [[3. Resources/Permanent Notes/A Capability Transfer Is Proven by Absence Not by a Handoff]] — the falsifiable test for whether enablement work moved a capability or moved a document. Absence is the only evidence that cannot be produced by performing it. ## Synthesis additions (2026-09-01 — session design and change announcements) - [[3. Resources/Permanent Notes/Attention Capacity Is Stable but the Effort It Costs Has Been Repriced]] — the evidence base for workshop and WordCamp session design: sustained attention has always reset at 8–30 minutes on stable instruments, so the fix for "nobody can sit through a 45-minute talk" is a reset cadence, not a shorter talk. Retires the goldfish statistic. - [[3. Resources/Permanent Notes/Framing a Decision as a Description Forecloses Disagreement]] — the community-communications failure mode of a warm, modest change announcement: presenting a directional decision as "just naming what we already do" leaves nothing to object to. Rule for writing one: keep the decision legible as a decision — name the premise, the evidence, and the channel for pushback. - [[3. Resources/Permanent Notes/High Expectations and Accommodations Only Work as a Pair]] — the companion the attention note plugs into: a repricing diagnosis keeps expectations and restructures conditions; a capacity diagnosis drops one half of the pair. Previously unregistered in any MOC. ## Synthesis additions (2026-10-05 — developer experience and community events) - [[3. Resources/Readwise/Articles/Inside Atlassian’s Developer Experience Overhaul]] — In a LeadDev interview, Atlassian customer CTO Andrew Boyagi says developers get 10% of their time for developer-experience work and cites 45% faster pull-request cycles and 51% of vulnerabilities auto-resolved; all three figures are self-reported by the vendor with no method given. - [Opus 5.5 Has Been Building Animatics for Me - Draft...](3.%20Resources/Readwise/Tweets/Opus%205.5%20Has%20Been%20Building%20Animatics%20for%20Me%20-%20Draft....md) — Matt Pocock says in a short post that he uses Opus 5.5 to draft course-video animatics (stills plus text-to-speech) before filming; it is a user testimonial for the vendor's model and the video was not reviewed. - [[3. Resources/Readwise/Articles/Jill Binder Launches Tech Differently, a Speaker Accelerator and Conference for People Who Build Differently]] — The Repository reports, almost entirely on organizer Jill Binder's account, that Tech Differently, a six-month speaker accelerator with an online conference on October 27, runs without Automattic or WordPress Community Team backing. - [[3. Resources/Readwise/Articles/Reshaping LoopConf A Fanatically Obsessed Attendee Experience]] — Organizer Brian Richards says in a WP Minute interview clip that LoopConf will sell tickets about 10 months ahead so ticket revenue could replace sponsor conversations; it is a stated plan with no sales figures. ## Synthesis additions (2026-10-07 — community hiring and demo content) - [[3. Resources/Readwise/Articles/From Math Teacher to Developer Community Manager, With Roxy Rodriguez-Becker]] — In an Overcommitted interview, Roxy Rodriguez-Becker says she was an active member of a developer community for about 1.5 years before the community-manager job opened at Torque, her stated employer. - [[3. Resources/Readwise/Articles/What I Learned While Making Short Vertical Videos for WordPress]] — Jos Velasco gives an 8-step checklist for plugin demo videos with his own measurements (1080x1920 canvas, about 100 px lost per side in the TikTok feed, subtitle phrases of about 13 characters) and promotes his own plugin as an example. ## Synthesis additions (2026-10-18 — registering notes missing from MOCs) - [[3. Resources/Permanent Notes/AI Search Visibility Requires Baseline Index Inclusion First]] — the prerequisite layer under the AI-search notes above: no AI-specific tactic makes an unindexed or poorly crawlable page visible, so index inclusion comes first. ## Synthesis additions (2026-10-18 — registering previously unlisted notes) ### Permanent Notes - [[3. Resources/Permanent Notes/A Profile Persuades By Showing Direction Not Status]] — A professional profile persuades more by showing where someone is headed and what they're doing now than by stating current employment status. Closest-fit placement. - [[3. Resources/Permanent Notes/Cross-Channel Coherence Outranks Single-Channel Volume in AI Search]] — When owned, earned, and community channels repeat the same core claim, AI search tools converge on it, so cross-team consistency beats publishing more on one channel. - [[3. Resources/Permanent Notes/Orientation Before Persuasion Outperforms a Sharper Argument]] — The author argues that naming your own position and listening for the other person's does more to persuade than sharpening the argument. Closest-fit placement. - [[3. Resources/Permanent Notes/Zet · Evangelism consistency increases community retention]] — Weekly posts and monthly reviews held for two quarters are the condition under which consistent evangelism raises community retention. ### Literature Notes - [[3. Resources/Literature Notes/DevRel for Black Developers and Why It's Slightly Different]] — A talk argues DevRel for Black developers needs the same craft plus authenticity, visibility, and care, meeting people where they are before pushing a product. - [[3. Resources/Literature Notes/Emcee Responsibilities During Conference Blocks]] — Aaron Jorbin outlines what a conference MC does at the start, middle, and end of each block, covering audience engagement, speaker introductions, and improvisation. - [[3. Resources/Literature Notes/Guppy Pimps, Tripp Pants, and Debugging IE5]] — A banter-driven bonus episode of a web-dev podcast with nostalgia, whiskey tasting, and legacy browser-testing stories; the note finds no argument to summarize. Closest-fit placement. - [[3. Resources/Literature Notes/How Community Size Impacts Engagement Strategy in Online Communities]] — Breaks communities into four size bands and shows how engagement tactics shift, from personal 1:1 outreach at small scale to automation or segmenting as they grow. - [[3. Resources/Literature Notes/How to Build and Hire a Community Team]] — A community team sits across marketing, product, and customer success, and the piece frames five personas and hiring for values fit over task skills. - [[3. Resources/Literature Notes/How to Easily Batch Videos for Reels, Shorts, and TikTok]] — A workflow for batching short-form video: plan, record one source, then edit and publish per platform for Reels, Shorts, and TikTok. Closest-fit placement. - [[3. Resources/Literature Notes/Introduction to Developer Relations for Talent Attraction]] — Introduces Developer Relations as a way to attract talent, building interest and loyalty between a company and IT professionals through technical and soft skills. - [[3. Resources/Literature Notes/Lit · Author identifies as product evangelist now]] — A writer notes a phrase heard from Dave Winer, product evangelist, and ties it to education-first advocacy and community retention. - [[3. Resources/Literature Notes/devrelshow ep 53 - Chris DeMars from TuxCare]] — Chris DeMars defines DevRel as a mission of bidirectional ambassadorship, with credibility from shipping code and defensibility against AI from the human personality.