This Week in WordPress #345 🔗 **Source:** [This Week in WordPress #345](https://www.youtube.com/watch?v=C0VtSN5aNWE) > [!note]+ Document Notes > tags: > - #WordPress > - #WPBuilds > - #AI > Author: WP Builds live panel — Host: Nathan Wrigley; Co-hosts/Guests: Michelle Frechette, Dave Gray (“Friendly Web Guy”), Miriam Schwab (Head of WordPress, Elementor) > Source: Live show — *This Week in WordPress #345* (WP Builds) > Reference: YouTube stream & transcript; episode page > date created: 2025-08-19 00:00 > > # Title: Building KPIs, Community Momentum, and AI Experiments — Notes from *This Week in WordPress #345* > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [♿ Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [🧩 Logical Validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: Include a list of sources consulted and cited in the article. ## 📝 Summary **What happened:** The WP Builds panel recapped fresh WordPress news: a burst of core project “mojo,” early agentic-AI experiments (the “Angie” plugin), community-run documentation (“WP Wiki”), new **Data Views** in Gutenberg, plugin business chatter (pricing and distribution), and broader “are we better or worse than last WCUS?” reflections. The tone stayed conversational, pragmatic, and lightly comic—typical WP Builds vibe. **Why it matters:** The show signals where practitioners are investing attention: AI copilots, editorial tooling in Gutenberg, community knowledge bases, and transparent plugin economics. These are levers for contributor onboarding, sustainable funding, and OSPO-grade governance. **Where to click:** Watch segments at timestamps linked below to jump straight to the topics. ## 📖 Main Content The episode mixes **practical demos** (time tracking “Click Tock,” invoice alignment) with **strategic takes** (role of AI in WordPress, community docs, UX in the site editor). Panelists highlight **Data Views** as a step toward scalable content management inside the editor, and they explore **plugin licensing** turbulence on WordPress.com—key for distribution strategies. ### 🗒️ Notes - 🎬 **Cold open & intros** — panel roll-call, show rhythm, and in-jokes - *Timeline:* [00:00](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=0)–[05:00](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=300) - Nathan frames the session; Michelle’s video lag quip; Dave’s “Friendly Web Guy” branding; Miriam returns as Elementor’s Head of WordPress. - Sets a casual, welcoming tone that encourages audience chat. - 🤖 **First agentic AI plugin (“Angie”)** — early access and possibilities - *Timeline:* [15:34](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=934) - Framed as *agentic* (goal-directed) assistance for content optimization and page improvements. - Early-access caveats: capabilities shifting as real users probe workflows. - Signals AI moving from code-assist to “ops-assist” for site owners. - 📚 **WP Wiki** — community-created documentation hub - *Timeline:* [23:58](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1438)–[25:35](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1535) - Introduced as a plugin/community initiative to **add articles** quickly. - Pitch: lower barriers to contribution; make docs editable where people already work (wp-admin). - Caveat: governance, moderation, and spam controls must match ease of editing. - 🧩 **Gutenberg roadmap + “mojo” returning** - *Timeline:* [29:26](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1766), [41:16](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=2476) - Panel senses renewed velocity in core; features feel more coherent. - Focus on **Data Views** and blocks/API consistency; pushes the editor toward CMS-grade list screens. - ⏱️ **Click Tock** — time tracking + invoicing alignment - *Timeline:* [26:48](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1608) - Dave’s tool: measure actual work and invoice accurately; aligns freelancer economics with reality. - Nice micro-case on indie plugin go-to-market (GTM). - 🗺️ **Are we better or worse since last WCUS?** - *Timeline:* [43:02](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=2582) - Healthy meta-question: quality of life for developers, docs, and UX. - Panel leans “better,” citing editor improvements and community momentum, while noting onboarding rough edges. - 🧮 **Data Views deep dive** — practical uses & current limits - *Timeline:* [46:21](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=2781), [52:19](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=3139), [56:15](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=3375) - Emerging list/table interfaces across post types; promises better content ops. - Open questions: custom schemas, bulk actions, performance on large sites. - 🧱 **Block “support,” site editor UX, and plugin distribution/pricing** - *Timeline:* [52:19](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=3139), [42:18](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=2538), [1:07:51](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=4071) - Debate over defaults vs. choice; reducing friction for non-dev users. - WordPress.com **business license** implications for plugin availability noted. > Transcript source (with many of the moments above): > (Also: :contentReference[oaicite:19]{index=19}) ## 📖 References - *This Week in WordPress #345* — YouTube stream (WP Builds). https://www.youtube.com/watch?v=C0VtSN5aNWE - Episode page (show notes & links): WP Builds — “Where’s Miriam? — TWiW #345”. :contentReference[oaicite:22]{index=22} - Live schedule: https://wpbuilds.com/live/ (calendar & player). :contentReference[oaicite:23]{index=23} ## 🗣️ Paraphrase - **On agentic AI in WP (“Angie”)** *Original gist:* Early access shows AI can proactively suggest on-page improvements and workflow shortcuts; still evolving with user feedback. *Paraphrase:* *Angie* isn’t just autocomplete—it chases goals. As testers push it, the tool keeps changing shape, hinting at a future where AI nudges site owners toward faster, smarter content updates. - **On Data Views momentum** *Original gist:* New list/table interfaces across the editor spark optimism; the project feels lively again. *Paraphrase:* Data Views are turning the editor into a proper control room. With this direction, the core project feels energized, and everyday content ops could get a lot saner. ## 📰 Newsletter **This Week in WP: AI helpers grow up, Data Views get real, and plugins mind the money.** - **Learn:** *Agentic AI* lands in early access (“Angie”). It aims for tasks, not just text—think page fixes and smarter checklists. [15:34 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=934) - **Build:** **Data Views** roll into Gutenberg, promising cleaner list screens across post types. Power users cheer; implementers want schemas and bulk actions. [46:21 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=2781) - **Contribute:** **WP Wiki** experiments with docs in wp-admin—fast to add, but governance matters. [23:58 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1438) - **Ship:** Dave Gray’s **Click Tock** tackles time tracking that matches invoices—freelancers, rejoice. [26:48 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1608) - **Debate:** Are we **better or worse** since the last WCUS? The panel votes “better,” with a side of “let’s fix onboarding.” [43:02 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=2582) ## ✅ Action Items - **For your advocacy & OSPO path** - **Codify “Community Docs in the Dashboard.”** Pilot a *WP Wiki*-style contrib flow for Training/Docs: issue templates, moderation queue, and badgeable micro-tasks. Map this to **metrics** (first-time contributor conversion, time-to-publish). [23:58 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1438) - **Run an “Agentic AI in WP” study.** Evaluate *Angie* against educator workflows (lesson plan builder, course outline scaffolds). Capture **task completion time**, **error rates**, and **editor satisfaction**. [15:34 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=934) - **Gutenberg Data Views demo curriculum.** Create a Teaching Kit: use cases (newsrooms, nonprofits), performance tests, and migration paths from wp-admin tables. Offer this to LearnWP and Meetup organizers. [46:21 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=2781) - **Transparent plugin economics.** Publish a “Plugin Pricing & Placement” brief (wp.org vs wp.com business license). Advocate for **clearer policies** and a **vendor code of practice** that aligns with community values. [1:07:51 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=4071) - **KPI prompt template (for each future article):** *“Explain how this piece advances open-source advocacy, contributor engagement, and education in WordPress. Identify concrete KPIs (new contributor signups, docs PRs merged, lesson completions, meetups run), propose equitable governance steps fit for an OSPO, and outline DEIB-friendly onboarding improvements inspired by the article’s arguments and examples.”* ## 🧪 Hypotheses - **H1:** Embedding doc authoring inside wp-admin increases first-time contributor conversions by ≥25% vs. external docs portals. (WP Wiki model) - **H2:** Agentic AI assistants reduce time-to-publish by ≥30% for small teams without hurting editorial quality. - **H3:** Data Views adoption correlates with lower support tickets for content operations on sites with >10 custom post types. ### 📊 Methodology - **Design:** A/B field experiments across partner sites; pre/post rollout with matched cohorts. - **Data sources:** wp-admin logs, GitHub/GitLab contribution graphs, LearnWP course analytics, support ticket systems. - **Analysis:** Difference-in-differences for rollout timing; survival analysis on contributor retention; user-level mixed models for editor task times. ### ❓ Questions - Where should moderation and spam controls live for a *WP Wiki* flow—plugin, platform, or project governance? [23:58 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1438) - What permissions model will keep Data Views flexible but safe for large editorial teams? [46:21 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=2781) - How do agentic tools avoid promoting “fast but wrong” edits? What human-in-the-loop checkpoints work best? [15:34 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=934) ### 🔮 Future Research - **Governance playbooks** for in-dashboard knowledge bases. - **Editor telemetry standards** for Data Views (privacy-respecting metrics). - **Agentic AI evaluation** specific to CMS tasks (prompt injection & supply-chain constraints). ### 💡 Implications - Better *on-ramps* for contributors, measurable learning outcomes, and trustworthy automation. - OSPOs gain clearer reporting lines: **inputs** (training, docs), **outputs** (contribs, releases), **outcomes** (site quality, time-to-value). ### 🧠 Learning Styles Assessment - **Reading level:** Upper high-school to early college (conversational, domain-specific jargon). 1) **Visual:** ✅ Live screen-shares and UI references; add flowcharts for Data Views state transitions. 2) **Aural:** ✅ Panel banter; publish an **audio-only** cut with chapter marks. 3) **Verbal:** ✅ Rich analogies; link to formal docs for each feature. 4) **Physical:** ❌ Minimal; add hands-on mini-labs (“enable Data Views; perform bulk action”). 5) **Logical:** ✅ Roadmap reasoning; include checklists and comparison tables. 6) **Social:** ✅ Live chat; prompt forum threads post-show. 7) **Solitary:** ⚠ Provide reflection prompts and a summary PDF. 8) **Naturalistic:** ❌ Not applicable; optional sustainability segment (green hosting tips) for broader relevance. ### 📊 Accessibility Assessment - **Screen readers:** Ensure show notes use semantic headings and alt text for images/GIFs. - **Keyboard navigation:** Verify focus order and skip-to-content on episode page. - **Contrast & readability:** Use ≥ 4.5:1 contrast; enlarge timestamp links. - **Text resizing:** Test at 200% zoom; avoid layout breakage. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment - **Cultural relevance:** Panel reflects parts of WP’s global mix; future episodes could include non-EN locales for docs & Data Views use. - **Inclusive language:** Maintain gender-neutral phrasing; define jargon (e.g., “agentic AI,” “Data Views”). - **Neurodiversity support:** Provide chapters, summaries, and predictable segment structure. - **Representation:** Rotate guests from diverse backgrounds and roles (docs, training, accessibility). - **Psychological safety:** Continue light-humor tone while inviting critique and questions. ### ✅ Logical Validity **Strengths** - **Inductive reasoning:** “Mojo is back” supported by concrete features and visible pace (Data Views progress). *Improves credibility.* - **Causal hints with caveats:** Agentic AI may speed publishing; panel notes it’s early access, avoiding overclaiming. *Balanced framing.* - **Counterpoints:** “Better or worse since WCUS?” invites dissent, not just cheerleading. *Nuanced view.* **Weaknesses / Potential fallacies (minor)** - **Anecdotal evidence:** Freelancer invoicing gains (Click Tock) rely on single case—risk of **hasty generalization**. *Fix:* Share multi-site data. [26:48 →](https://www.youtube.com/watch?v=C0VtSN5aNWE&t=1608) - **Bandwagon aura:** “Mojo is back” could read as vibe-based. *Fix:* Cite commit counts, release notes. **Tone:** Friendly, lightly comedic, practically optimistic; avoids absolutism and personal attacks. #### 🔍 DARVO Analysis No evidence of **Deny/Attack/Reverse-Victim** tactics. - **Deny:** Not present; the panel acknowledges gaps (onboarding, policy ambiguities). - **Attack:** None; critiques target *processes/policies*, not people. - **Reverse Victim/Offender:** Not present; no victimhood narratives. - **Related fallacies:** Occasional anecdote-driven claims, but no manipulation patterns. ### 🔍 SEO Evaluation - **Keywords:** “WordPress news,” “Gutenberg Data Views,” “agentic AI,” “WP Wiki,” “plugins.” Use them in **title**, **H2s**, and **first 100 words** of show notes. - **Meta description (150–160 chars):** “WordPress weekly: Data Views, agentic AI, WP Wiki docs, plugin economics, and community health—links & timestamps.” - **Title tag (≤60 chars):** “This Week in WordPress #345: Data Views, AI, WP Wiki” - **Headers:** Structure with H2 per segment; include keywords (e.g., “Gutenberg Data Views”). - **Length:** Target 1,200–1,800 words in the post; timestamped bullets boost *time on page*. - **Links:** - **Internal:** Previous TWiW episodes; LearnWP lessons; related plugin pages on wpbuilds.com. - **External:** GitHub issues/PRs for Data Views; plugin homes; Elementor/Make Core posts. - **URL:** `/this-week-in-wordpress-345/` — concise and keyworded. - **Images:** Add alt text like “Gutenberg Data Views table of posts.” Optimize file size. - **Mobile:** Check Core Web Vitals; avoid heavy embeds above the fold. - **Engagement:** Add CTAs: “Share your Data Views tip,” “Try Angie and report results.” - **Schema:** Use `PodcastEpisode` + `VideoObject` with `clip` markup for chaptered timestamps. - **Social:** Open Graph + Twitter Cards with descriptive title and preview image. ## 🎯 Conclusion *This Week in WordPress #345* showcases a community leaning into **AI helpers**, **editor UX maturity (Data Views)**, and **practical plugin business realities**—with a through-line of *make things easier for contributors and users*. For an advocate-educator and future OSPO leader, these threads translate cleanly into pilots, curricula, and policy proposals that improve transparency, inclusion, and measurable impact. <!-- deep-read:sections end -->