Major-version upgrades
Assess and implement target-version changes on a branch; validate the agreed HTML, PDF, or other outputs.
Documentation engineering - Sphinx maintenance service
Plan Python and Sphinx dependency work, review extension and theme compatibility, and investigate publishing failures. Covered environments, output formats, monthly capacity, and operating responsibilities are agreed upfront.
Maintain the Sphinx environment your publishing depends on.
We plan compatibility reviews across Sphinx, Python, docutils, extensions, and themes. Your team receives tested changes, documented findings, and priorities for remaining work.
Python & extension compatibility
Reproducible environment configuration and checks for the named reference and content extensions.
Theme & docutils-deprecation fixes
Review build warnings and representative rendering for the agreed theme and docutils versions.
Multiversion & Read the Docs upkeep
Review active versions, Read the Docs configuration, and named publishing pipelines within the agreement.
Plan Sphinx upgrades around your extensions
Most Sphinx sites end up pinned to an old version because one extension refused to follow, and the longer that pin sits the more expensive the eventual upgrade becomes. We keep the extension set healthy so staying current stays routine instead of turning into a project.
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.
Sphinx maintenance plans
Published retainers describe different levels of capacity. Agree covered environments, outputs, active versions, priorities, and response terms. Larger upgrade remediation or new output formats 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
- Sphinx expert consultation
- Additional site: $240
- Custom development: $110/h
Docs ops
Active ownership of your Sphinx docs, upgrades, extension compatibility, and monitoring, not just break-fix.
$1,500–4,000/month
- Major-version upgrade assessment and scoped work
- Python dependency pinning & extension compatibility
- Theme breakage & docutils-deprecation fixes
- Selected content/release drift reviews
- Scoped agent-access and export checks
- Multi-version & multi-site 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
- Sphinx expert consultation
Documentation teams we have worked with
Commonly asked questions
We assess compatibility for your target Sphinx version, Python environment, extensions, themes, and named outputs. Docs Ops can include branch-based upgrade work and validation within agreed capacity. Larger extension replacements or output changes are scoped separately.
We review dependency pins, supported Python versions, and named extensions, including autodoc, intersphinx, and MyST where used. Reproducible builds and compatibility checks help identify failures; remediation priorities follow the agreed scope.
These can be included. We agree the active versions, hosting configuration, pipeline access, and output checks before work begins, then report compatibility findings and remaining risks.
We reproduce the build and identify upgrade blockers in the environment, extensions, theme, and source. We propose replacements or scoped patches, document tradeoffs, and agree the target version before implementation.
Autodoc can import your package during the build. We agree the package and documentation environments to test, investigate import or signature failures, and validate named intersphinx mappings. Generated reference quality also depends on the maintained source and docstrings.
Keep your Sphinx docs building
Partner with us for planned Sphinx maintenance, validated changes, and issue investigation within an agreed scope.