Redocly / Redocly/redoc

CE Redoc 3.x

Open
#2,829 0 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

p0 planned Type: Enhancement
Dominant language
TypeScript
Stars
25.9k
Forks
2.4k
Avg merge
13h 10m
Merged PRs (30d)
4

Description

Redoc 3.0 is coming — one renderer for OpenAPI 3.2, AsyncAPI, GraphQL, and MCP

Learn what's coming in Redoc 3.x →
Blog post: What's coming in Redoc CE 3

Hi all! 👋

Here's a quick update from the team. Since September 2025, we've been working hard on a complete overhaul of Redoc, and Redoc 3.0 is almost ready for release.

It's not just an incremental update — it's a whole new codebase! ✨ Here's a brief overview of the changes:

  • ⚡ A new rendering engine that renders on demand, so huge specifications no longer slow down the page
  • 🧩 Support for more than just OpenAPI:
    • GraphQL
    • AsyncAPI
    • MCP
  • 🌙 Redesigned UI with a proper dark mode
  • 🎨 Theming via CSS design tokens instead of the old JavaScript theme object
  • 🔍 Faster search on large specs
  • 🔗 Real URLs for operations, tags, and schemas instead of hash fragments

It stays MIT-licensed and self-hostable, same as always. ❤️
More details can be found here: https://redocly.com/redoc-ce

Regarding the open issues and PRs 🧹

Honest answer first: we haven't had time to look at them. 😬 Everyone's been busy with the rewrite since last September, and 2.x maintenance slipped. We apologise for this, as many of you took the time to report bugs and open PRs 🙏

As 3.0 has a different codebase, most of the open issues and PRs simply don't apply to it anymore. Rather than leaving them open, we're going to close most of them.

If an issue you reported still occurs in version 3.0, please open a new issue (or reopen the old one). These reports will be addressed. ✅

Thanks for sticking with the project. More news soon. 🎉

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or code entry points are identified in this announcement. Read the linked Redoc CE page and blog post first; there is no implementation change or completion criterion specified, and the issue says that most 2.x work no longer applies to the 3.0 codebase.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.