# New Blog Post: Documentation that machines can actually read

**URL:** <https://community.nextw.com/t/new-blog-post-documentation-that-machines-can-actually-read/2172>\
**Category:** Nextworld Platform News\
**Created:** [August 11, 2026, 7:08pm UTC](https://community.nextw.com/t/new-blog-post-documentation-that-machines-can-actually-read/2172 "2026-08-11T19:08:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bryden](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/bryden/32/102_2.png) [@bryden](https://community.nextw.com/u/bryden)\
**Post date:** [August 11, 2026, 7:08pm UTC](https://community.nextw.com/t/new-blog-post-documentation-that-machines-can-actually-read/2172/1 "2026-08-11T19:08:49Z")

</div>

New on Frame/work: [It’s 2026. Do you know if AI can read your documentation?](https://nextw.com/tech-blog/its-2026-do-you-know-if-ai-can-read-your-documentation)

 ![Vintage green library card catalog](https://us1.discourse-cdn.com/flex001/uploads/nextworld/original/2X/6/62999c7838e423344d631f7e2b9ca0a903545cad.jpeg)

Carrie Sheaffer’s team built Nextworld’s documentation on DITA-inspired principles years ago: topic-based authoring, content types, tagged elements, metadata wrappers, single-sourced reuse. It made the docs better for the humans reading them. It also, without anyone planning for it, made them ideal for machine readers.

This post walks through the payoff: how the docs team rebuilt the retrieval behind Ed with clean, labeled structure to work from, and how the same tags and metadata translated straight into semantic HTML and [schema.org](http://schema.org) markup for a new external docs site. If you care about how structured content holds up in the age of retrieval and answer engines, give it a read and drop your thoughts below.