sphinxcontrib-confluencebuilder v3 Planning | Cloud and Legacy Editor Considerations

[jdknight]

Atlassian has indicate full deprecation for the legacy editor to be on "April 2026". For more information on this, see the following:

Confluence Article (Upstream)
The Legacy Editor is being deprecated in Confluence Cloud: Here’s what you need to know

Taking this into consideration, this extension plans to focus on performing some non-trivial feature/maintenance work for a future v3.0 release planned for the start of year 2026. The planned change is that content generated and published to Confluence Cloud will only support using the v2 editor. For users who may experience issues using the v2 editor with their documentation:

1. If there is an limitation due to something missing in this extension, please feel free to create an issue outlining the use case.
2. If the issue is specific to Confluence, it is recommended to bring up any concerns in the discussion group
   Confluence Cloud Legacy Editor Deprecation (hosted by Atlassian).

This extension will try to look at the possibility of confirming Cloud targets when generating content set. However, there may be a requirement needing to explicitly indicate if the editor/target type in a project's Sphinx configuration. If such a change is needed, there will be information provided on how to configure. Users can pin to a version less than 3.0 if they are concerned with any disruption during the release.

Note that there is no plan to remove support for Confluence Data Center (/Server) targets. Users should still be able to generate and publish v1 storage-format content for their instances (until a time where Atlassian no longer supports the older editor on this edition).