3 posts tagged with "Documentation strategy"

How I turned documentation strategy into agent design

I recently had the opportunity to move from thinking about AI for documentation to actually designing documentation agents.

The context was a large Confluence knowledge base covering technical and product documentation for Marketing Mix Modeling (MMM). Its users included Data Scientists, Data Engineers and consultants working across Data, Modeling, Insights and Simulations.

As often happens in my freelance assignments, I was entering a domain I did not know yet. Before thinking about AI, I first had to understand the business domain, the documentation ecosystem, its authors and its users.

That is part of the job.

🎬 Previously, in Episode 1...

In Part 1, I explained why the usual approaches for managing structured data in Docusaurus eventually reach their limits: duplication, fragile maintenance, and complex multilingual setups.

Even with best practices such as @graph, the core problem remained: structured data lived next to the content instead of being a natural extension of it.

In this Part 2, we move from diagnosis to solution.

I'll show how this reflection led me to design a Docusaurus plugin, built from the ground up to:

• rely on front matter as a single source of truth,
• automatically generate JSON-LD compliant with schema.org,
• handle multilingual content cleanly,
• and remain maintainable over time.

How my work on structured data eventually turned into a Docusaurus plugin

In my previous article, "I Took Control of My Metadata", I explained how I explored two different ways of injecting structured data into Docusaurus.

That work led me to a simple conclusion: for a bilingual, content-rich website designed for modern SEO (including SEO, GEO, and generative engines), none of the existing approaches were sustainable in the long run.

At that point, I had a choice: accept growing complexity… or change my approach entirely. That's how a third method emerged — and eventually, a plugin.