As part of our ongoing commitment to improving the contributor experience and the efficiency of our documentation efforts, this post outlines a proposed workflow for responsibly using AI to assist in drafting new WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ end-user documentation articles for release 6.9.

This initial phase focuses only on the creation of new articles, using approved style guides to generate structured drafts while keeping human contributors fully in control of fact-checking, editing, and publishing. The goal is to responsibly introduce AI as an augmentative tool – never as a replacement for contributor expertise.

In future release cycles, this workflow will expand to include automated updates to existing documentation, integration with tools like the WordPress Playground for screenshots, and additional opportunities for guided automation. We will document and refine each step as we iterate.

Responsible AI workflow for WordPress.org documentation

This proposed structure outlines a safe and effective way to integrate generative AI into the WordPress.org documentation process. It assumes human oversight at every step and is designed to uphold best practices, contributor safety, and content accuracy — all while increasing efficiency through thoughtful use of AI.

1. Set clear scope and intent (human-led)

Before prompting AI, contributors should define:

• What needs to be created (e.g. a new feature doc).
• Audience: WordPress users with some (limited) technical knowledge.
• What type of article it will be (how-to, reference, landing page, etc.).

Please consider: Think of this like writing a good issue tracker ticket – be specific, but flexible enough for collaboration.

2. Generate a structured draft with AI

AI should be used only to produce a first draft, not a finished product. When prompting:

• Include a separate list of links at the end for internal referencing to dev notes, TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/./GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ issues, and related documentation.
• Specify the intended audience and type of document.
• Request content aligned with the Docs Style Guide and the WordPress Brand Style Guide.

Reminder: AI-generated content is never final. It’s a starting point – the expertise still comes from our contributors.

3. Fact-check and human edit

Every AI-generated draft must be:

• Fact-checked (AI-assisted) against canonical sources such as the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. codebase, as well as the corresponding GitHub pull requests, Trac tickets, and any applicable and related documentation.
• Copyedited for grammar, voice, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), and clarity.
• Reviewed by at least one other contributor to confirm technical accuracy.

4. Run it through style and inclusion checks

AI or human contributors can help ensure the content:

• Uses plain language when appropriate.
• Avoids passive voice and unnecessary jargon.
• Uses accessible formatting (semantic headings, code blocks, etc.).
• Follows inclusive language practices.

Option to consider: You may ask AI to assist with a style pass, but this must be followed by a human final review.

5. Publish with accountability

Before publishing:

• Make sure articles and corresponding GitHub commits indicate whether AI was used.
• Include a changelog comment summarizing the workflow.
• Close the Pull Request with a summary of contributors to be included in the release credits (This will only be applied to major releases.).
• Flag the article for follow-up if the feature it covers is experimental or subject to change.

Keep in mind: Transparency builds trust and helps us trace content lineage.

6. Reflect, iterate, and document the process

This pilot is just the beginning. Contributors are encouraged to:

• Record what worked (and what didn’t) in their prompts or workflows.
• Share findings in team meetings, SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, or GitHub issues.
• Suggest improvements or automation opportunities for future releases (e.g. using AI to detect outdated content).

Guardrails to keep in place

To protect the integrity of WordPress.org documentation:

• Never publish AI-generated content without human review.
• Avoid hallucinations by grounding all prompts in verifiable sources.
• Do not train AI models directly on private or unpublished WordPress.org content.
• Always use a “human-in-the-loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop” approach for oversight and editing.

A note on ethics

AI is not here to replace contributors. It is here to support them.

The goal of this workflow is to reduce friction in the drafting process so contributors can spend more time on high-value tasks like strategy, mentorship, and refining content. This approach upholds the core values of the WordPress project by emphasizing collaboration, transparency, and inclusion.

Developing prompts collaboratively ahead of 6.9

For the upcoming WordPress 6.9 release, we will begin developing AI prompts in advance of the release cycle to support the creation of new documentation articles. This will be a collaborative, iterative effort involving contributors from the Docs Team and beyond.

Rather than providing a fixed prompt template from the outset, we’ll work together to explore:

• What types of prompts produce the most accurate and useful first drafts.
• How audience type, feature complexity, and prompt structure affect output quality.
• What tone, format, and phrasing align best with our style guides and contributor expectations.
• Which prompt patterns reliably reduce friction and avoid common AI issues (e.g. hallucination, redundancy, overly generic content).

We’ll test prompts during regular contributor meetings, in Slack, and through hands-on documentation issues tied to 6.9. These findings will inform the development of prompt libraries and usage guidelines that reflect real contributor experiences and lessons learned.

As we gather results, we’ll document successful prompt themes, refine our approach, and share reusable examples with the broader community to support future releases.

This process ensures that our use of AI remains grounded, transparent, and shaped by the needs of our contributors – empowering more people to participate effectively while maintaining the quality and trustworthiness of WordPress.org documentation.

Next steps

This proposed AI workflow will apply to WordPress 6.9 and focus solely on creating new documentation. Future iterations will expand to include AI-assisted updates to existing articles and explore automation tools such as AI-generated screenshots from the WordPress Playground.

We’ll continue to iterate, document, and refine this process across upcoming release cycles to ensure it meets the needs of both our contributors and the broader WordPress community.

The contributors to this proposal: 

@estelaris, @milana_cap, @ninianepress

#ai, #docs, #proposal