---
title: "Discussion on \"From 71 to 100%: What It Took to Make the Rootstock Developer Portal AI-ready\" | Hashnode"
description: "Discussion on \"From 71 to 100%: What It Took to Make the Rootstock Developer Portal AI-ready\". How we moved the Rootstock Developer Portal from 71 to 100% for AI agent readiness, what changed underneath the documentation, and what I learned."
url: "https://hashnode.com/posts/from-71-to-100-rootstock-developer-portal-ai-ready/6abf8375314a8a18e473a4cd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [From 71 to 100%: What It Took to Make the Rootstock Developer Portal AI-ready](https://blog.theowanateamachree.com/from-71-to-100-rootstock-developer-portal-ai-ready?utm_source=hashnode&utm_medium=feed)

How we moved the Rootstock Developer Portal from 71 to 100% for AI agent readiness, what changed underneath the documentation, and what I learned.

Oct 2 · 11 min read · blog.theowanateamachree.com  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#buildworldclassweb3docs](https://hashnode.com/tag/buildworldclassweb3docs)
-   [#developer-experience](https://hashnode.com/tag/developer-experience)
-   [#documentation](https://hashnode.com/tag/documentation)
-   [#web3](https://hashnode.com/tag/web3)
-   [#ai-readiness](https://hashnode.com/tag/ai-readiness)
-   [#rootstock](https://hashnode.com/tag/rootstock)
-   [#technical-writing-1](https://hashnode.com/tag/technical-writing-1)
-   [#docusaurus](https://hashnode.com/tag/docusaurus)

## Written by

[Owanate Amachree](https://hashnode.com/@owans)

@owans · United Kingdom

  
[View profile](https://hashnode.com/@owans)

Lead Technical Writer @RootstockLabs | Product Owner, Mently | Founder, Techrity Innovation Foundation

I’m Owanate Amachree, a Lead Technical Writer at RootstockLabs with 6+ years of experience in developer documentation and Developer Experience. I write about documentation systems, information architecture, machine-readable documentation, AI agent readiness, documentation health, and the tools and practices that help teams maintain better developer documentation.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.