Do you only work on Docusaurus?
Docusaurus is most of the work, but we also build and maintain MkDocs, Zensical and GitBook sites, and we can help you decide whether a move between them is worth it.
Docs-site engineering and accessibility
Docusaurus development
This is for teams that already run a Docusaurus site, or are about to, and need someone who understands both the framework and documentation to build and fix it. We write the React components, configure search and versioning, set up CI, and handle the swizzling and upgrades that nobody on your product team has the time to learn properly.
Price
$75/hour or $560/day
Response
Reply within 1 business day
After delivery
30-day fix window
Who it's for#who-its-for
- Docs leads whose Docusaurus site has outgrown its defaults and needs real components: API reference layouts, tabs that remember a reader's choice, interactive examples.
- Engineering leads who want the docs site maintained properly without pulling a product engineer off the roadmap to do it.
- Heads of support whose help center moved to Docusaurus and now needs search that finds things, a feedback loop on every page, and layouts agents can link to with confidence.
- Teams stuck mid-upgrade on an old major version, with swizzled components that no longer match the theme they were copied from.
If your content still lives in a hosted help center or wiki, moving it is a migration project, priced by page count. This page covers engineering work on the site itself: building it, extending it and keeping it healthy.
What you get#what-you-get
Work is scoped as tasks, and each one ships as a reviewed pull request in your repository. Typical tasks include:
- Custom React and MDX components that match your design system, documented so your writers can use them without asking.
- Search: Algolia DocSearch, a local search plugin or a custom index, configured and tuned for how your readers actually search.
- Versioned docs with a release workflow your team understands, including when to cut a version and when not to.
- Theming and swizzling done conservatively, so future upgrades stay easy.
- CI: builds on every pull request, broken-link and anchor checks, preview deploys and publishing on merge.
- Performance and SEO: page metadata, sitemaps, structured data and image handling.
- Upgrades across Docusaurus major versions, including the MDX compatibility issues they tend to surface.
- Accessibility fixes to WCAG 2.2 AA, with a separate accessibility audit if you need the full picture first.
Every pull request includes a short note on what changed, how to test it, and anything your team should know before the next upgrade. Components come with usage examples in MDX, so writers can copy a working pattern instead of reading source code.
How it runs#how-it-runs
- Brief. You describe the task or send the issue. We read the repository and reply with an estimate in hours or days.
- Agreement. You approve the estimate. For open-ended work, we agree a budget cap and we report against it as we go.
- Build. We work in a branch, open a pull request with a preview link, and explain what changed and why.
- Review and merge. Your team reviews, and we address comments until the change is ready to merge.
- 30-day fix window. For 30 days after delivery, bugs in code we wrote are fixed at no charge.
For upgrades, we test the build and the most visited pages in a preview before merging, and list anything that changed visually so nobody is surprised after release.
We also build docs sites on MkDocs and on Zensical, the new generator from the team behind Material for MkDocs, which is now in maintenance mode. If you run Material for MkDocs today, we can help you weigh staying, moving to Zensical or moving to Docusaurus. The handbook page on CI/CD publishing describes the kind of pipeline we set up whichever generator you use.
Pricing#pricing
- Hourly
- $75 / hour
- about €69
- Daily
- $560 / day
- about €520
Work is billed at the hourly or daily rate against an estimate you approve first. Small fixes are billed by the hour; longer builds are usually better value by the day. You see the time spent on each task in the invoice. If a task turns out larger than the estimate, we stop and tell you before going past it.
What moves the estimate: how far the current site has drifted from the stock theme, how many swizzled components need updating, whether your design system has to be matched exactly, and how much of the work touches build and hosting infrastructure outside the docs repository. A clean, recent Docusaurus install is the cheapest place to start from.
If you want a larger piece of work done as a project, such as a full rebuild or a move from another generator, we can quote it as a fixed price instead. For content moves, see documentation migration.
Prices are in US dollars; the euro figures are approximate conversions for reference.
Frequently asked questions#faq
Can you work with our design system?
Yes. We build components against your design tokens and existing React components where possible, and keep theme overrides small so upgrades stay manageable.
Should we swizzle theme components?
As little as possible. Ejecting a component copies it into your repository, and every ejected component is something you maintain across upgrades. We prefer configuration, CSS and wrapping over ejecting, and we record every swizzle in the repository with the reason for it.
Can you take over a site someone else built?
Yes. We start with a short review of the repository, billed hourly, and send a list of what we would fix and in what order before any larger work begins.
How do we work together day to day?
In writing, mostly: pull requests, issues and email, with a call when a decision needs one. We reply within 1 business day.
Send us what you have
Send a link to your docs, an export, or a few lines on what needs to change. We reply within 1 business day with questions or a quote.