Wanted: Documentation Feedback

General
1

Hi folks :waving_hand:

I’m spending a cycle or two on our documentation platform at https://directus.io/docs. So I’m here asking for feedback to make sure we deliver a better experience.

Curious to get your opinions on our existing docs - what are the biggest offenders right now?
What’s frustrating? What do you hate? What do you like?

For context, here’s some of what I already have planned:

  1. Simplify language and labels – for example (Directus Automate is confusing because the module is called “Flows” and Directus Connect should be “APIs”
  2. Breaking some of our current Guides section down into two separate top level sections “Guides” vs “Reference” because we’re mixing a lot of these concerns right now and it just makes finding what you need much harder.
  3. Surface content by use case (think headless cms vs internal app) and framework (I use Nextjs or I prefer Nuxt)
  4. Better API reference with actual sample responses
  5. Better search UX with extremely relevant results (attaching a quick preview here)

image
image2412×1872 452 KB

2

Hi Bryan, always big thanks for you and Directus teams.
In this “AI era”, I still using Directus as my main backend stack. But the difference now, I almost not read official docs anymore. I let AI to answer my questions about Directus. And it 99.99% always solved.

So, IMHO, for official docs, maybe main orientation not for human anymore, but for AI? I believe, the model should read official accurate docs to give correct/accurate answers.

1 Like
3

Thanks! That’s certainly helpful feedback and we’re planning to add more stuff for AI agents as well like a MCP server and markdown content negotiation to make it easier for LLMs to learn and help folks build with Directus.

2 Likes