docs(other): add blog post on AI features shipped in May-July and the AI roadmap - #351
Merged
Conversation
h0pped
force-pushed
the
blog/ai-features-2026-summer
branch
from
July 28, 2026 13:50
2880ee8 to
ceafac3
Compare
RomanHotsiy
reviewed
Jul 28, 2026
h0pped
marked this pull request as ready for review
August 13, 2026 13:46
Contributor
There was a problem hiding this comment.
marketing-site AI Review: 🟢 Completed
Redocly Agent has reviewed your changes and found 5 potential issue(s).
Note
Low Risk
This PR introduces new blog content and author metadata without affecting application logic, operational systems, or deployment configurations.
Overview
Adds a new blog post covering customer-facing AI features shipped between May and July 2026 (including Docs MCP updates, llms.txt improvements, agent discovery, and the Reunite AI Assistant) alongside the upcoming AI roadmap (Gateway MCP, custom tools, and more). Additionally, registers Illia Nykonchuk as a blog author in blog-metadata.yaml and includes their profile image.
| MCP is one door into your docs; [`llms.txt`](https://redocly.com/docs/realm/config/seo) is the other, and we made what's behind both doors better: | ||
|
|
||
| - `llms.txt` output now includes **OpenAPI code samples and response samples**, and correctly renders `oneOf` and discriminator schemas: exactly the parts of an API description agents used to trip over. | ||
| - Custom Markdoc tags can define their **own LLM rendering** with `renderForLlms`, with locale support. If you built a custom component, its content is no longer invisible to AI. |
Contributor
| MCP is one door into your docs; [`llms.txt`](https://redocly.com/docs/realm/config/seo) is the other, and we made what's behind both doors better: | ||
|
|
||
| - `llms.txt` output now includes **OpenAPI code samples and response samples**, and correctly renders `oneOf` and discriminator schemas: exactly the parts of an API description agents used to trip over. | ||
| - Custom Markdoc tags can define their **own LLM rendering** with `renderForLlms`, with locale support. If you built a custom component, its content is no longer invisible to AI. |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What/Why/How?
Blog post covering the customer-facing AI features shipped in May-July (Docs MCP, llms.txt, agent discovery, AI Assistant in Reunite) plus the roadmap (Gateway MCP, code mode, custom MCP tools, Maintainer, embeddable AI Assistant).
Also adds Illia Nykonchuk as a blog author (metadata entry + photo).
Do not merge before the next stable Realm release: token refresh, MCP server card / A2A agent card, agent skills, and
renderForLlmslocale support are currently in0.136.0-nextonly.Reference
Testing
Check yourself
Security