Roadmap
What Reed does not do yet, stated plainly.
This page exists so that nothing on the rest of this site has to hedge. Everything documented elsewhere works today. Everything listed here does not.
No dates. A capability moves off this page when it ships, not when it is planned.
Client SDK generation
Section titled “Client SDK generation”Reed generates HTTP request snippets from your OpenAPI spec, in five languages. It does
not generate a client library, and there is no reed sdk command.
The ordering matters and is deliberate: documentation follows artifacts that provably
exist. Rendering npm install @acme/sdk for a package nobody published would be a
fabricated fact, so an SDK section renders only once a real published package resolves.
Until then, code snippets call the HTTP API directly.
Versioned documentation
Section titled “Versioned documentation”docs.json accepts a versions key and ignores it. There is no version switcher and
no per-version content tree.
Multi-version documentation is an architectural feature — routing, navigation, search
scoping and cross-version linking — not a few extra fields. Writing a versions block
today produces exactly one version of your site, silently, because nothing reads it.
Multiple languages
Section titled “Multiple languages”languages is accepted and ignored, on the same terms. There is no i18n routing, so a
second language cannot be served from one Reed site today; it would have to be a separate
build at a separate base.
Multiple products
Section titled “Multiple products”products is accepted and ignored, on the same terms.
Importers beyond Fern
Section titled “Importers beyond Fern”reed import --from fern is the only conversion path. --from accepts no other value.
Importing from other documentation platforms is wanted and not built. See Migrating from Fern for what the existing importer does and Known import gaps for what it drops.
A hosted platform
Section titled “A hosted platform”Reed today is a compiler you run — in your terminal, in your CI. There is no self-serve hosted product: no signup, no dashboard, no way to connect a repository and get a site built for you.
The site you build with the CLI is yours and complete, and that is not going to change; a hosted offering would be an addition, not a replacement.
Why these three reserved fields exist at all
Section titled “Why these three reserved fields exist at all”versions, products and languages are accepted by the schema so that a config
carrying them survives the strict unknown-key check — which otherwise rejects any key Reed
does not recognize.
That is the entire reason. Their presence is not a preview of behaviour, and their contents are not validated. If you are relying on one today, you are relying on nothing.