I found it helpful in thinking about code and the approach for my current project:

https://github.com/WillAdams/gcodepreview

In particular, it made it seem obvious to split up the documentation between:

- Overview --- readme.md

- Tutorials --- handled in various template files

- How to Guides --- embedded in the Literate Program code

- Reference --- the indices and Command Glossary

Ive been aware of diataxis for a while, but i hadnt considered such an approach. Will definitely keep it in mind for when im ready to generate some sort of docs. Thanks!

With tutorials, I’ve been enjoying handing my agent a directory of screenshots, talking out the process, then having it organize it all into a guide.

Huge fan of Diataxis over the years!

Agreed, a couple months back, I got cf to crawl the site and created a block of skills around it for personal use.

same, it’s great for first pass LLM docs

You clearly do see the point!

I used past tense for a reason ;)

Ah, fair! English can be so precise and yet still ... not quite :)

yeah, the urge to turn this page into a skill and then just let it run loose on all my random vibe-coded side projects is very, very strong. seems great for that kind of thing.