Version & framework upgrades
Target-version assessment, branch-based implementation, and checks for the agreed configuration, MDX, and components.
Documentation engineering - Docusaurus maintenance service
Plan dependency work, review theme and plugin compatibility, and investigate publishing failures with a documentation engineering partner. Covered components, monthly capacity, and operating responsibilities are agreed upfront.
Planned upgrades and documented build health.
Most Docusaurus maintenance is the same handful of failure modes, upgrades, dependency drift, and plugin breakage. We plan upgrades and compatibility checks, investigate failures, and report unresolved risks.
Dependency & build health
Review dependency changes and run agreed build checks, with findings and remediation priorities reported to your team.
Plugin, theme & search upkeep
Compatibility review and scoped fixes for named plugins, theme components, and search configuration.
Content drift & AI-readiness
Where included, review selected content against release changes and test structured exports or agent access against agreed questions and versions.
Stay current with Docusaurus, without the upgrade scramble
Teams usually postpone Docusaurus majors until something forces the issue, and by then the jump spans several breaking releases at once. We review dependency updates on a branch, test the publishing path, and schedule upgrades around your team’s requirements.
Reliable, secure, proactive
We review dependency and build risks, schedule agreed checks, and report issues that require an owner or additional scope.
Transparent, predictable costs
Agree monthly capacity, priorities, and approval for additional work before implementation.
Expert support
Work with a documentation engineering partner who reviews changes with your platform and content owners.
Capacity and support scope
Scheduled maintenance, consultation, and issue investigation use the included monthly hours. The agreement specifies covered components, contact channels, working hours, and any response targets. Additional work is approved separately; incident coverage and resolution commitments require an explicit agreement.
Docusaurus maintenance plans
Published retainers describe different levels of capacity. Agree covered sites, components, priorities, and response terms. Upgrade remediation, content review, and new features use that capacity or require an additional approved scope.
Single site
Ideal for teams needing stable, ongoing maintenance on a single doc site.
$350/month
- Up to 3 hours/month (no rollover)
- Monthly dependency updates
- Email triage; response terms agreed
- Named extension upkeep within capacity
- Named pipeline upkeep within capacity
- Chat and email support
- Docusaurus expert consultation
- Additional site: $240
- Custom development: $110/h
Docs ops
A planned engineering backlog for your Docusaurus platform, with capacity and review cadence agreed in the proposal.
$1,500–4,000/month
- Major-version upgrade assessment and scoped work
- npm/React & MDX dependency management
- Selected content/release drift reviews
- Scoped agent-access and export checks
- Plugin & theme compatibility upkeep
- Multi-site & multi-brand coordination
- Broken-link & build-health checks
Enterprise
Custom capacity for complex sites and multi-language portals. Any service levels or incident coverage are defined in the agreement.
Custom pricing
- Custom retained hours
- Monthly dependency updates
- Email triage; response terms agreed
- Named extension upkeep within capacity
- Named pipeline upkeep within capacity
- Chat and email support
- Docusaurus expert consultation
Documentation teams we have worked with
Commonly asked questions
We assess the upgrade against your configuration, MDX, components, plugins, and active versions. Docs Ops can include upgrade work within agreed capacity. We test on a branch, document remaining incompatibilities, and submit changes for review; larger remediation is scoped separately.
We reproduce the failure, review dependency and configuration changes, and agree the remediation priority. Dependency controls and build checks help identify regressions. Response windows and available engineering capacity are set in the agreement.
We review named plugins, theme components, and search configuration against the target Docusaurus version. Changes to unsupported integrations can require replacement or additional development; we report those decisions before implementation.
Ejected components copy upstream internals and need compatibility review. We inventory customizations, compare them with the target theme, and assess wrappers or smaller overrides where appropriate. Both wrapped and ejected components are tested for the agreed upgrade.
We agree the active versions and locales to validate, then check builds, sidebars, and representative pages for those targets. Archiving decisions remain with your product and documentation owners.
Keep your Docusaurus site building
Partner with us for planned Docusaurus maintenance, validated changes, and issue investigation within an agreed scope.