Creating a WordPress plugin wasn’t an initial goal. And yet, through ongoing reflections around WPDistrib, the idea emerged: to directly connect my documentation base to the WordPress admin interface itself. This plugin, still in development, aims to provide automatic contextual help linked to existing documentation. It marks a new step for WPDistrib: turning knowledge into a tool, learning into interface, and creating an ecosystem where content and usage meet — where it matters.

Understanding that documenting is not reproducing — it’s thinking

Before mastering a subject, you can already start documenting it. Documenting is not an end in itself, but a tool for analysis, structure, and clarity. Writing helps formalize thoughts, reveal gaps or possibilities. It also allows you to keep a usable trace — for yourself or for others.

This is exactly the spirit in which I decided to write this article, even though my plugin project is still in progress. Taking the time to write, here and now, helps me anchor a logic of understanding before trying to produce more.

Starting a WordPress project without coding: from idea to motivation

It all started with an event: a talk at WordCamp Toulouse 2025 entitled “What if we built a WP plugin together using AI?”. That talk gave me a spark. I thought: why not me? Why couldn’t I create a plugin too, without being a developer?

That moment launched a process: setting the foundations, identifying a real need, and imagining a first concrete response. I then started a conversation with AI (ChatGPT), feeding it with all the context: my level, my goals, my vision.

Taking a step back to move forward: the power of analysis before action

Instead of rushing into development, I chose to pause. That may seem counterintuitive, especially when you’re excited to build. But it’s a productive pause: I analyze, I structure, I document. This phase opens up new perspectives, saves time long-term, and prevents me from diving into overly complex or premature directions.

It’s also a way to stay within a feasible, pragmatic scope, aligned with my current level. And from that clarity, the most useful implementations can emerge.

Building a first plugin with AI: tests, limits, and learnings

AI became my co-pilot. It helped me understand the basics of how a WordPress plugin works, the prerequisites, and the right tools (like Visual Studio Code or the PCP plugin for code validation).

I even created a small development guide for the AI, in the form of a text file, gathering coding conventions, available resources, and common pitfalls to avoid. This document acts as a kind of shared technical memory with the AI.

The result: a first working version of the plugin — simple, useful, functional. It detects the current admin menu in WordPress and shows a contextual link to the relevant WPDistrib documentation.

Among the first concrete results of this experiment, a working version of the plugin is already live. For example, when navigating to the menu of the Headers Security Advanced & HSTS WP plugin, a small contextual menu pops up. It indicates that documentation is available on WPDistrib, and offers direct links to related content (overview, review, alternatives… ).
This help only appears when relevant articles already exist on the topic.

Structuring your learning to make it actionable (and reusable)

The key is to analyze → document → execute.

Whenever I work on a topic, I start by asking: What am I trying to do? For whom? Why? Then, I document what I understand, the options I consider, and useful resources. Only after that do I move into execution.

To keep a trace, I use an online tool: Notion.so (free version). Its main advantage is flexibility: I can structure all my documentation, ideas, data — rearrange them easily, change views, transform content. And what I build in Notion is already compatible with Gutenberg: copy-pasting preserves blocks. It’s an excellent tool to manage and organize knowledge before publishing.

In fact, I currently have more information, notes, and structured content in my Notion space than on the WPDistrib site itself.

This process allows me to retain valuable information, build on it, and above all, create content for WPDistrib. Because documenting also means feeding a knowledge base that others can benefit from.

Building a living documentation base: why it matters at every level

Documenting your learning — even when imperfect — means building a professional knowledge base. It creates a space for reflection, transmission, and sharing. It’s also a way to “build in public” without overexposing. You reveal your logic, your challenges, your open questions.

And most importantly, it’s future-proof: each article adds value to the WPDistrib knowledge base, strengthens SEO, and guides other users along the way.

Exploring other types of plugins for different fields

What I started is focused on WordPress and documentation. But the same approach applies to other professions: a plugin can help a specific community improve its own practices.

Documenting real use cases, analyzing specific needs, designing a simple interface — any profession can benefit from custom tools created by those who know the field. That’s a promising direction for future WPDistrib plugins that are more field-specific.

🌀 Learn, document, test: a method for every WordPress creator

This article is the first in a long series. It marks the beginning of a process where analysis, documentation, and execution come together to shape useful, concrete solutions.

You don’t need to be a developer to bring value to WordPress. But you can structure your learning, define your scope clearly, and build useful tools — at your own pace.

And that’s exactly what WPDistrib aims to support: a living, free, interconnected documentation base… Especially useful where it matters most.