the current OpenAPI workflow uses Fumadocs to generate many Markdown files that embed custom React components; devs then have to move those files around and occasionally tweak code by hand. the proposal is to replace that setup with a single <APIPage /> component.
devs now just feed it a raw openapi.json file and declare which endpoint to display, eliminating the file-shuffling and manual edits.
• much simpler, declarative integration—one component, one JSON source of truth—resulting in a cleaner developer experience.
Note: because each endpoint must still be declared in code, newly added endpoints won’t appear automatically; they remain invisible until the code is updated. An upcoming Fumadocs release is expected to address this gap.
the current OpenAPI workflow uses Fumadocs to generate many Markdown files that embed custom React components; devs then have to move those files around and occasionally tweak code by hand. the proposal is to replace that setup with a single
<APIPage />component.devs now just feed it a raw
openapi.jsonfile and declare which endpoint to display, eliminating the file-shuffling and manual edits.• much simpler, declarative integration—one component, one JSON source of truth—resulting in a cleaner developer experience.