Question 1

How do you handle Sphinx major-version upgrades?

Accepted Answer

Sphinx major upgrades routinely break extensions and themes. Our Docs ops tier tests the upgrade on a branch, resolves extension incompatibilities and docutils deprecations, fixes theme breakage, verifies the build (HTML and PDF if you generate it), and ships it, so you stay current instead of pinned to an old version out of fear.

Question 2

What about Python dependency and extension compatibility?

Accepted Answer

Sphinx sites break most often on Python dependency drift and extension incompatibilities across releases. We pin and manage your Python environment, track extension compatibility (autodoc, intersphinx, myst-parser, and third-party extensions), and fix breakages before they reach your writers.

Question 3

Can you maintain our multiversion and Read the Docs setup?

Accepted Answer

Yes. Multiversion documentation, Read the Docs config, and custom build pipelines are all part of what we keep working across upgrades, including docutils deprecations that quietly break rendering over time.

Question 4

We are pinned to an old Sphinx because upgrading broke things. Can you unstick us?

Accepted Answer

That is the most common state we find. Being pinned is usually a symptom of one or two unmaintained extensions rather than Sphinx itself. We reproduce the build, identify which extensions actually block the upgrade, and either replace them, patch them, or absorb their behaviour into a small local extension you own, then move you onto a supported version.

Question 5

Do you maintain our autodoc and API reference builds?

Accepted Answer

Yes. Autodoc is the part most sensitive to Python changes, because it imports your code at build time, so a dependency bump in the documented package can break the docs build even when the docs did not change. We keep the docs environment pinned separately from the library, fix import and signature breakage as it appears, and keep intersphinx mappings resolving.

TechDocs

TechDocs

- Sphinx maintenance service

Sphinx upgrades break extensions and themes. We keep yours current.

Major-version upgrades

Python & extension compatibility

Theme & docutils-deprecation fixes

Multiversion & Read the Docs upkeep

Stay on a supported Sphinx, without breaking your extensions

Reliable, secure, proactive

Transparent, predictable costs

Expert support

Sphinx maintenance plans

Single site

Docs ops

Enterprise

You're in good company

Commonly asked questions

Keep your Sphinx docs building

TechDocs