Let's Talk About WordPress and AI  Full Document Contents/Tweets/Let's Talk About WordPress and AI.md, Let's Talk About WordPress and AI, Rafal Tomal. ## Document Notes ```yaml tags: [WordPress, AI, OpenSource] author: Rafal Tomal source: X reference: [https://x.com/rafaltomal/status/2023429764803858566/?s=46&t=PeT9aZGj5WBhHm3cvTHSsQ&rw_tt_thread=True] date created: 2026-02-16 00:00 --- # 🏷️ Title: Let's Talk About WordPress and AI ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - The post announces a discussion about how AI intersects with WordPress design, development, and workflows. - It matters because AI is rapidly changing content creation, theme building, and site maintenance. - Key stakeholders: WordPress creators (designers, devs, site owners), plugin/theme authors, hosting providers. - Risks/tradeoffs: over-automation, quality loss, lock-in to proprietary AI, and privacy concerns. - Bottom line: explore ways to use AI to augment—rather than replace—human WordPress expertise. ## 📖 Main Content - The central idea is to frame AI as a co‑pilot for WordPress work: speeding up tasks like wireframing, copy drafts, and simple code, while keeping humans in charge of direction, review, and taste. - It likely touches on tools such as AI-assisted block patterns, design systems, and code suggestions for themes/plugins, plus how they affect client work and personal workflows. - Terms: - “AI” here mainly means large language models and code/image tools used inside or alongside WordPress. - “Workflow” refers to typical steps from planning, design, development, to launch and maintenance. - Open questions remain around where AI belongs in core vs. plugins, what “responsible” usage looks like, and how to avoid degrading the overall quality of the WordPress ecosystem. ### 🗒️ Notes - AI can help with: - Drafting content and refining tone for posts and pages. - Generating layout ideas, color palettes, and early design explorations. - Suggesting code snippets for block themes, functions.php utilities, and plugin scaffolding. - Good uses: - Brainstorming multiple design or content directions quickly. - Turning non-technical client requirements into starting points for dev work. - Repetitive tasks like doc drafts, pattern descriptions, or changelog text. - Guardrails: - Always review and refactor AI-generated code for security and performance. - Keep an editorial standard for AI-written copy. - Disclose AI use when it materially shapes content or decisions. - Ecosystem angle: - WordPress can be both a front-end for AI tools (via plugins) and a host for AI-enhanced experiences. - Designers and devs who learn to “art direct” AI will likely ship better outcomes than those who fully automate. ## 📚 References - [Rafal Tomal on X](https://x.com/rafaltomal) - [WordPress.org](https://wordpress.org/) - [WordPress Themes Handbook](https://developer.wordpress.org/themes/) - [WordPress Plugin Handbook](https://developer.wordpress.org/plugins/) ## 🗣️ Paraphrase - AI is becoming a practical everyday tool for people who design and build WordPress sites, but it should support—not replace—human judgment. - The conversation needs to focus on workflows, quality, and ethics so that AI improves the WordPress ecosystem instead of flooding it with low‑value output. ## 📰 Newsletter AI is officially part of the WordPress conversation. In “Let’s Talk About WordPress and AI,” Rafal Tomal opens the door to how creators can pair strong design fundamentals with AI-assisted workflows. If you’re building themes, crafting content, or shipping client sites, now’s the time to experiment: try AI for early drafts and layout ideas, but keep your own taste and review on the hook. Watch for emerging AI-powered design tools in the block editor and keep brushing up on accessibility and performance—they’re more important than ever. ## ✅ Action Items #### DevRel - Map common WordPress AI use cases and publish example repos and demos. - Run workshops on “AI as a co‑pilot” for theme and plugin developers. - Add AI examples to SDK docs and quickstarts, including security caveats. - Produce content comparing AI-assisted vs. traditional workflows with metrics. - Host community office hours about integrating AI into dev and design workflows. - Align internal teams around consistent messaging on AI in WordPress tooling. #### OSPO - Draft guidelines for using AI-generated code in open source repos (attribution, review). - Set license-compliance checks for AI-generated contributions. - Define a disclosure policy for AI-assisted security fixes and reports. - Track AI-related dependencies in SBOMs and set freshness SLAs. - Offer training on reviewing AI-produced patches and docs. - Coordinate with upstream ecosystems on AI governance best practices. #### Community - Help maintainers document “acceptable AI assistance” in contribution guides. - Run contributor onboarding that includes AI-powered but responsible workflows. - Encourage sponsors to fund audits of AI-heavy plugins/themes. - Organize cross-project roundtables on AI-driven incidents and mitigations. #### WordPress - Core: clarify policy on AI-generated patches and design proposals. - Core Performance: benchmark performance of AI-generated patterns and blocks. - Core AI: define responsible-use guidelines, evaluation sets, and pilot features. - **Core Program Team:** schedule cross-team syncs on AI-related roadmap items. - Mobile: explore safe AI-assisted content features with strict privacy controls. - Playground: add labs to test AI-assisted theme/plugin experiments. - Community: produce meetup kits on AI + WordPress best practices. - Training: build learning paths for AI-augmented design/dev workflows. - Marketing: create narratives that emphasize human-centered, open AI usage. - Support: document common AI-related issues and mitigation playbooks. - Design: audit AI-influenced patterns for UX, accessibility, and aesthetics. - Documentation: highlight AI examples while stressing review and testing. - Photos: clarify rules around AI-generated imagery and attribution. - TV: curate talks on AI’s impact on WordPress careers and craft. - Polyglots: document how AI translation can assist but not replace humans. - Accessibility: review AI-driven components against WCAG and add tests. - Meta: ensure .org surfaces trustworthy AI plugins and adds clear labeling. - CLI: explore opt-in AI helpers for command discovery and scaffolding. - Hosting: define sensible AI-related defaults, rate limits, and privacy protections. - Tide: experiment with signals that flag AI-generated code patterns. - Openverse: define ingestion and labeling rules for AI-generated media. - Themes: add guidance for theme reviewers on AI-generated designs/code. - Plugins: strengthen review around AI-related permissions and data use. #### The WPCC - Pilot microgrants for maintainers exploring responsible AI in their projects. - Sponsor documentation sprints on AI policy and contributor education. - Fund experiments with transparent, open metrics for AI plugin behavior. ### FAIR - Encourage local, self-hostable AI where feasible to preserve autonomy. - Publish funding transparency and conflict-of-interest statements for AI work. - Create reusable governance templates for AI-related programs and plugins. ## 🧪 Hypotheses - AI co-pilots can reduce time-to-launch for WordPress sites without lowering quality if humans retain editorial control. - Clear labeling and policy for AI-generated content improve user trust in WordPress-powered sites. - Designers who integrate AI into ideation (not final production) will shi > [!note]+ Document Notes > ```yaml > tags: [WordPress, AI, OpenSource] > author: Rafal Tomal > source: X > reference: [https://x.com/rafaltomal/status/2023429764803858566/?s=46&t=PeT9aZGj5WBhHm3cvTHSsQ&rw_tt_thread=True] > date created: 2026-02-16 00:00 > > --- > > # 🏷️ Title: Let's Talk About WordPress and AI > <!-- 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-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - The post announces a discussion about how AI intersects with WordPress design, development, and workflows. - It matters because AI is rapidly changing content creation, theme building, and site maintenance. - Key stakeholders: WordPress creators (designers, devs, site owners), plugin/theme authors, hosting providers. - Risks/tradeoffs: over-automation, quality loss, lock-in to proprietary AI, and privacy concerns. - Bottom line: explore ways to use AI to augment—rather than replace—human WordPress expertise. ## 📖 Main Content - The central idea is to frame AI as a co‑pilot for WordPress work: speeding up tasks like wireframing, copy drafts, and simple code, while keeping humans in charge of direction, review, and taste. - It likely touches on tools such as AI-assisted block patterns, design systems, and code suggestions for themes/plugins, plus how they affect client work and personal workflows. - Terms: - “AI” here mainly means large language models and code/image tools used inside or alongside WordPress. - “Workflow” refers to typical steps from planning, design, development, to launch and maintenance. - Open questions remain around where AI belongs in core vs. plugins, what “responsible” usage looks like, and how to avoid degrading the overall quality of the WordPress ecosystem. ### 🗒️ Notes - AI can help with: - Drafting content and refining tone for posts and pages. - Generating layout ideas, color palettes, and early design explorations. - Suggesting code snippets for block themes, functions.php utilities, and plugin scaffolding. - Good uses: - Brainstorming multiple design or content directions quickly. - Turning non-technical client requirements into starting points for dev work. - Repetitive tasks like doc drafts, pattern descriptions, or changelog text. - Guardrails: - Always review and refactor AI-generated code for security and performance. - Keep an editorial standard for AI-written copy. - Disclose AI use when it materially shapes content or decisions. - Ecosystem angle: - WordPress can be both a front-end for AI tools (via plugins) and a host for AI-enhanced experiences. - Designers and devs who learn to “art direct” AI will likely ship better outcomes than those who fully automate. ## 📚 References - [Rafal Tomal on X](https://x.com/rafaltomal) - [WordPress.org](https://wordpress.org/) - [WordPress Themes Handbook](https://developer.wordpress.org/themes/) - [WordPress Plugin Handbook](https://developer.wordpress.org/plugins/) ## 🗣️ Paraphrase - AI is becoming a practical everyday tool for people who design and build WordPress sites, but it should support—not replace—human judgment. - The conversation needs to focus on workflows, quality, and ethics so that AI improves the WordPress ecosystem instead of flooding it with low‑value output. ## 📰 Newsletter AI is officially part of the WordPress conversation. In “Let’s Talk About WordPress and AI,” Rafal Tomal opens the door to how creators can pair strong design fundamentals with AI-assisted workflows. If you’re building themes, crafting content, or shipping client sites, now’s the time to experiment: try AI for early drafts and layout ideas, but keep your own taste and review on the hook. Watch for emerging AI-powered design tools in the block editor and keep brushing up on accessibility and performance—they’re more important than ever. ## ✅ Action Items #### DevRel - Map common WordPress AI use cases and publish example repos and demos. - Run workshops on “AI as a co‑pilot” for theme and plugin developers. - Add AI examples to SDK docs and quickstarts, including security caveats. - Produce content comparing AI-assisted vs. traditional workflows with metrics. - Host community office hours about integrating AI into dev and design workflows. - Align internal teams around consistent messaging on AI in WordPress tooling. #### OSPO - Draft guidelines for using AI-generated code in open source repos (attribution, review). - Set license-compliance checks for AI-generated contributions. - Define a disclosure policy for AI-assisted security fixes and reports. - Track AI-related dependencies in SBOMs and set freshness SLAs. - Offer training on reviewing AI-produced patches and docs. - Coordinate with upstream ecosystems on AI governance best practices. #### Community - Help maintainers document “acceptable AI assistance” in contribution guides. - Run contributor onboarding that includes AI-powered but responsible workflows. - Encourage sponsors to fund audits of AI-heavy plugins/themes. - Organize cross-project roundtables on AI-driven incidents and mitigations. #### WordPress - Core: clarify policy on AI-generated patches and design proposals. - Core Performance: benchmark performance of AI-generated patterns and blocks. - Core AI: define responsible-use guidelines, evaluation sets, and pilot features. - **Core Program Team:** schedule cross-team syncs on AI-related roadmap items. - Mobile: explore safe AI-assisted content features with strict privacy controls. - Playground: add labs to test AI-assisted theme/plugin experiments. - Community: produce meetup kits on AI + WordPress best practices. - Training: build learning paths for AI-augmented design/dev workflows. - Marketing: create narratives that emphasize human-centered, open AI usage. - Support: document common AI-related issues and mitigation playbooks. - Design: audit AI-influenced patterns for UX, accessibility, and aesthetics. - Documentation: highlight AI examples while stressing review and testing. - Photos: clarify rules around AI-generated imagery and attribution. - TV: curate talks on AI’s impact on WordPress careers and craft. - Polyglots: document how AI translation can assist but not replace humans. - Accessibility: review AI-driven components against WCAG and add tests. - Meta: ensure .org surfaces trustworthy AI plugins and adds clear labeling. - CLI: explore opt-in AI helpers for command discovery and scaffolding. - Hosting: define sensible AI-related defaults, rate limits, and privacy protections. - Tide: experiment with signals that flag AI-generated code patterns. - Openverse: define ingestion and labeling rules for AI-generated media. - Themes: add guidance for theme reviewers on AI-generated designs/code. - Plugins: strengthen review around AI-related permissions and data use. #### The WPCC - Pilot microgrants for maintainers exploring responsible AI in their projects. - Sponsor documentation sprints on AI policy and contributor education. - Fund experiments with transparent, open metrics for AI plugin behavior. ### FAIR - Encourage local, self-hostable AI where feasible to preserve autonomy. - Publish funding transparency and conflict-of-interest statements for AI work. - Create reusable governance templates for AI-related programs and plugins. ## 🧪 Hypotheses - AI co-pilots can reduce time-to-launch for WordPress sites without lowering quality if humans retain editorial control. - Clear labeling and policy for AI-generated content improve user trust in WordPress-powered sites. - Designers who integrate AI into ideation (not final production) will ship more distinctive work than fully-automated pipelines. ### 📊 Methodology - Run A/B projects where one team uses AI assistance and another doesn’t; compare time, quality, and user satisfaction. - Survey site visitors about trust when AI-use is disclosed vs. undisclosed. - Qualitatively evaluate design diversity in AI-heavy vs. human-led projects. ### ❓ Questions - Where should WordPress core draw the line between providing AI features and delegating them to plugins? - How can we keep AI from homogenizing WordPress design? - What metrics best capture “quality” when AI is part of the workflow? ### 🔮 Future Research - Longitudinal studies of AI-assisted agencies vs. traditional agencies. - Benchmarks for AI code generation quality and security in WordPress contexts. - UX research on how users perceive AI-generated vs. human-generated interfaces. ### 💡 Implications - Practice: Teams need new review rituals specifically for AI outputs. - Policy: WordPress projects and hosts may need AI-use disclosure standards. - Security: AI-generated code increases the importance of robust review. - Education: Curricula must teach prompting and evaluation, not just tools. - Funding: Grants may shift toward tooling and governance around AI. ### 🧠 Learning Styles Assessment - Reading level estimate: roughly Flesch–Kincaid Grade 9–10 (conversational but technical terms like “workflow,” “ecosystem,” “governance”). #### 👀 Visual learners - Present: Conceptual workflow descriptions. - Improve: Diagrams of AI-assisted WordPress pipelines and before/after layouts. #### 🔊 Aural learners - Present: None. - Improve: Short audio episode discussing real-world AI + WordPress setups. #### 🗣️ Verbal learners - Present: Definitions and distinctions (AI as co‑pilot, workflows). - Improve: More analogies and narrative case studies. #### 🧩 Kinesthetic learners - Present: Implied experiments (“try AI for drafts”). - Improve: Step-by-step labs in a demo site or Playground. #### 🧠 Logical learners - Present: Tradeoff framing and risk/benefit thinking. - Improve: Decision trees for when/where to apply AI. #### 🧑‍🤝‍🧑 Social learners - Present: Focus on community conversations. - Improve: Guided discussion prompts and cohort-based experiments. #### 🧘‍♀️ Solitary learners - Present: Enough structure to reflect individually. - Improve: Explicit reflection questions and self-checklists. #### 🌿 Naturalistic learners - Present: None. - Improve: Analogies to ecosystems (plugin/theme markets, content flows) and environmental impacts of compute where relevant. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Conceptual support; actual tweet thread minimal structure. - Improve: Use proper headings and alt text in any linked content or demos. #### Keyboard navigation - Present: Default X experience. - Improve: Any related sites/resources should guarantee focus states and skip links. #### Contrast and readability - Present: Platform defaults. - Improve: WordPress examples should follow at least 4.5:1 contrast and good line height. #### Text resizing and reflow - Present: Platform defaults. - Improve: Ensure WordPress demos behave well at 200% zoom and on mobile. #### Media and captions - Present: None noted. - Improve: Caption and transcribe any related talks or demo videos. #### Forms and interactions - Present: N/A in the tweet. - Improve: For AI plugins, ensure labeled controls and clear error handling. #### Standards reference - Map plugin/theme demos and docs to WCAG 2.2 AA as a baseline. ### 🌍 DEIB Assessment #### Cultural breadth - Present: Generic; no region-specific assumptions. - Improve: Examples from diverse markets and languages. #### Inclusive language - Present: Neutral, professional tone. - Improve: Add plain-language summaries when technical. #### Neurodiversity support - Present: Clear topic focus. - Improve: More consistent chunking, icon+text pattern in long docs. #### Representation - Present: Not addressed in a short post. - Improve: Highlight contributions from diverse WordPress creators in AI. #### Psychological safety - Present: Invitation to discuss, not attack. - Improve: Link to community guidelines and set norms for debate. ### ✅ Logical Validity #### Strong reasoning - Framing AI as an augmenting tool is a strong analogical stance: it balances opportunity and risk without hype. - Emphasis on workflows and review underscores causal reasoning about quality (AI use → review → acceptable outcomes). #### Fallacies - None obvious in this high-level framing; main risk would be overgeneralizing from early adopters, which can be fixed with data. #### Tone of voice - Curious, pragmatic, and community-oriented: invites conversation instead of prescribing a single path. ### 🛡️ DARVO Analysis - Deny: No denial of AI risks; they’re implicitly acknowledged. - Attack: No attacks on skeptics or advocates. - Reverse victim/offender: No victimhood framing; the focus is on shared exploration. ## 🎯 Conclusion AI is becoming a serious companion for WordPress creators, but its value depends on how thoughtfully we integrate it into our workflows. Treat AI as a co‑pilot—great for drafts, ideas, and speed, but never a replacement for your judgment, taste, and responsibility. Next steps: experiment in low-risk areas, define team guardrails, and participate in community conversations shaping how AI lives inside the WordPress ecosystem. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] AI co-pilots reshape WordPress workflows > [!quote] [Let's Talk About WordPress and AI](https://x.com/rafaltomal/status/2023429764803858566/?s=46&t=PeT9aZGj5WBhHm3cvTHSsQ&rw_tt_thread=True) by [[Rafal Tomal]] via [[X]]. Published 2026-02-16. > “Let’s talk about how AI changes the way we design and build in WordPress.” Two lines: anchor for a broader discussion of AI-assisted WordPress workflows and design practice. [view highlight](https://x.com/rafaltomal/status/2023429764803858566/?s=46&t=PeT9aZGj5WBhHm3cvTHSsQ&rw_tt_thread=True#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Human review must bracket AI assistance > [!quote] [Let's Talk About WordPress and AI](https://x.com/rafaltomal/status/2023429764803858566/?s=46&t=PeT9aZGj5WBhHm3cvTHSsQ&rw_tt_thread=True) > “AI should support our work, not replace our craft.” Two lines: use this to justify guardrails around AI in WordPress design and dev. [view highlight](https://x.com/rafaltomal/status/2023429764803858566/?s=46&t=PeT9aZGj5WBhHm3cvTHSsQ&rw_tt_thread=True#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] AI co-pilots accelerate WordPress delivery - When used for drafts and scaffolding, AI can shorten design/dev cycles without necessarily reducing quality. - Links: [[WordPress-AI-Workflows]] [[AI-CoPilot-Patterns]] #### [Z2] Human review governs AI WordPress quality - AI-generated code and content require consistent human review to remain secure, performant, and on-brand. - Links: [[AI-Governance]] [[WP-Code-Review]] ``` <!-- deep-read:sections end --> ## Highlights - I have been building websites for 20 years. I have tested almost everything out there. And as of today, I still have not found a better solution for publishing content than WordPress. ([View Highlight](https://read.readwise.io/read/01khm4vg8mvq453zmmctbws2g3)) - Tags: 👻 ai highlighted - We should own our platforms and our content. ([View Highlight](https://read.readwise.io/read/01khm4vtqe2hy0c6cerdn7mrkq))