We've been working through Docsio from the first website import to the moment you hit Publish. The result is Docsio v2, with a new look for the sites you create and a lot of work on the parts you use to get them there.
New docs sites now use Fumadocs. The agent has better instructions for building and editing them. We've tightened up imports, worked through the manual editor and plan mode, and made publishing and GitHub sync more resilient when something goes wrong.
There's also simpler pricing: $10/month per site, with every feature included and a seven-day trial that doesn't need a credit card.
New sites, built with Fumadocs
This is the change you'll notice first. New Docsio projects use a Fumadocs template, with a cleaner reading experience, responsive navigation, light and dark themes, and full-text search built into the site.
We wanted the first draft to feel like documentation you'd be happy to share. That meant working on the details around the content too: page titles, section navigation, code examples, mobile layouts and how your brand carries through the site.
Your logo, colors and fonts still come with you. The new template gives them a better starting point, and you can keep refining the design in the editor.
Existing sites keep their current template and content. This release doesn't automatically rebuild or replace a site you've already published.
An agent that knows the site it's working on
The editing agent now has instructions specifically for Fumadocs, including its page structure, navigation files, components and styling. It can work with the actual template instead of reaching for conventions from a different docs framework.
We also changed how it handles longer tasks. It carries forward the context it needs, keeps track of saved work, and spends less of its conversation repeating old file contents and build output. If a run stops, changes already saved are kept.
Plan mode and editing have clearer boundaries. Use plan mode to work through an approach before applying changes. When you're ready to make them, the agent can edit the files and show you the result in preview. You can still open a page and make a small correction yourself.
Better imports, closer to your source
Getting a useful first draft matters. We've tightened the URL-import workflow so an error page isn't treated as successful source material, and improved the instructions that guide how source content becomes documentation.
That includes preserving the meaning of your steps and examples, keeping track of import coverage, and avoiding unsupported additions when a source is sparse. We also fixed duplicate page headings that could appear when imported Markdown and the template both rendered the same title.
You'll still want to review an import against your product. The work here is about giving you a stronger draft to review and fewer things to untangle afterward.
More confidence when you publish
We've worked on the awkward cases around publishing: overlapping requests, interrupted deployments, incoming GitHub changes and restoring an earlier version.
Publishing now does a better job of keeping the selected files and settings together throughout the build. GitHub deliveries have a durable queue, and incoming changes preserve a conflicting editor draft so you can recover it. We've also tightened GitHub authorization and the checks around who can connect a repository.
Publication history lets you inspect and restore a saved published snapshot. Named documentation versions let you keep an older product edition available alongside your current docs. Both have been checked with the Fumadocs setup, including version navigation and search.
Search, chat and MCP that fit the new template
Fumadocs already has a good search experience, so that's the one we use. There's no second legacy search bar layered over it.
The AI chat widget works alongside search for visitors who want to ask a question. Reader MCP gives their AI tools access to your published documentation. Both use published content, so an unfinished editor draft doesn't become the answer your readers see.
Author MCP remains the private connection for your own AI tools to edit a project. We've checked its permissions and token controls as part of this release too.
A cleaner platform around your docs
We went through the everyday screens as well: project settings, the manual editor, team invitations, version controls and the subscription flow. We checked keyboard navigation, smaller screens, loading states and error paths, and fixed the rough spots we found.
Feedback now lives directly in Docsio. Choose Share feedback, pick a feature request, bug or issue, and tell us what's on your mind. It goes into our own feedback system.
We've also cleaned up the public site and rewritten the help pages that had fallen behind the product. Pricing, feature descriptions and setup instructions now reflect what you can use today.
One subscription per site
For new accounts, the seven-day trial starts when you sign up. It includes one site, every feature and no Docsio branding. No credit card is needed to get started.
After the trial, a site subscription is $10/month. Each additional site has its own subscription, and collaborators don't need a separate paid seat to work on an accessible site.
If a trial or subscription ends without payment, that site's editing access is locked and its published site is temporarily taken offline. The documents stay saved. Subscribing restores access, while other paid sites on the account stay available.
Existing grandfathered accounts keep their current access and limits for now. Existing paying customers keep their current subscription terms. You don't need to migrate your site because of this announcement.
You can find the details on the pricing page and in our updated billing docs.
Try the new setup
This release includes work behind the scenes that won't show up in a screenshot: database checks, recovery paths, access controls, and tests for the ways these features interact. We ran real import and publishing rehearsals alongside the local and browser checks, then verified the production signup, trial and checkout flows.
If you've used Docsio before, open your dashboard and take a look around. If you're starting fresh, try Docsio for seven days and build your first site with the new template.
And if something feels off, use Share feedback. A page that didn't import, a confusing setting, a change you'd like the agent to handle better: those details help us decide what to work on next.