Roadmap
This section outlines the nearest product directions for One File Docs.
Import from HTML
HTML import will help bring in existing pages, articles, and legacy help materials from websites, landing pages, or exports from other systems.
This matters when published content needs to be migrated into One File Docs and maintained from one place going forward.
API support for other languages and REST services
This direction is about expanding the current API support, which is currently centered on C#, to other programming languages and external REST-based integrations.
That includes stable HTTP endpoints, predictable JSON request and response formats, examples for popular languages, and integration paths for backend services, CI/CD pipelines, content generators, internal portals, and other automations without hard coupling to a single stack.
This would make it easier to plug One File Docs into existing team workflows, connect outside systems faster, and use the product as a general-purpose documentation backend.
Import from OpenAPI and Swagger
OpenAPI and Swagger import would help teams assemble API Reference content and related documentation from existing specifications much faster.
The import should pull in endpoints, methods, parameters, request and response schemas, descriptions, error codes, and tag-based grouping so teams do not have to rebuild the same API structure manually.
This is especially useful for REST APIs, internal platforms, and public developer portals where the specification is already the source of truth and should become readable documentation with minimal manual cleanup.
Dynamic content from JSON
Dynamic sections now accept embedded schema 1.0 JSON and build their root page, nested pages, navigation, and reusable resources inside the exported viewer.
This is useful when the document structure is not fixed in advance: for example, an example atlas, integration catalog, case gallery, or entity reference whose pages change between exports.
Future work in this area can add more content formats beyond HTML while keeping the source and all resources embedded in the single exported file.
Plugin system for recurring tasks
A plugin system would make it easier to package repeated workflows into reusable extensions instead of rebuilding the same setup manually for every document.
This is especially useful for recurring tasks: standard onboarding blocks, repeated integration guides, branded templates, analytics setup, PrismJS, feedback widgets, embed scenarios, export presets, and other frequently reused configuration patterns.
That should make team workflows more consistent, speed up new document setup, and reduce manual mistakes in shared styles, scripts, and repeated configuration.
AI tools for text work
AI-assisted text tools would help users draft and improve content directly inside the editor instead of constantly switching between the document and external services.
The first useful set includes rewriting, shortening long sections, improving wording, restructuring content, generating draft sections, and adapting text for instructions, help articles, onboarding, or product documentation.
This is especially useful for teams that update documentation often, need a more consistent tone, or want to assemble a solid first draft quickly before manual review.