Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence Builder Sphinx Extension with Legacy (v1) and Modern (v2) Editors

James Knight
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 30, 2025

Maintainer for the Confluence Builder Sphinx extension. Over the years, been trying to support the various API, macro and editor changes. With respect to the editor, the extension currently defaults to producing `v1` editor content due to a subset of additional Sphinx features that can be rendered versus when using the newer editor. The extension provides a means to use the `v2` editor for users who do not require features that may be impacted by the switch. I imagine over time, we will be adjusting the extension to default to `v2` for Confluence Cloud targets when required.

If it helps, the following lists known limitations when attempting to render Sphinx-capabilities. To my knowledge, the following is up-to-date as of 2025-06-30.

  • Confluence does not support applying a code line offset (v1, v2).
  • Confluence does not support disabling code lines (see above ref).
  • Enumerator lists do not support explicit styling (v1, v2).
  • Images cannot be inlined with expected sizes (v1, v2). While changes in CONFCLOUD-68501 looked to address this, later changes made inlined images to have a non-configurable height-restricted to a line.
  • Confluence does not support indenting block types. For example, an indented paragraph with a list will always have the list rendered without an indentation (v1, v2).
  • Confluence does not allow image offset alignments in a paragraph (v1, v2).

In addition, not having the ability to disable table borders prevents emulating certain unique structures (e.g. horizontal lists).

I am not sure if any of these may be part of any existing roadmaps or are not part of Atlassian's goals for support in the new editor. This post is mainly for informational sake.

1 comment

Comment

Log in or Sign up to comment
Joni Vanderheijden
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 1, 2025

Thanks for reaching out James,

While I'm not across the details of each of these feature requests, we are actively looking at all feature gaps between legacy and cloud editor as part of the deprecation again. If they are reflected under Confluence Cloud suggestions on jira.atlassian.com they are on our radar.

Voting and watching those public suggestions is the best way to keep on top of any changes that happen in supporting these features in the cloud editor.

I think a lot of the gaps you mentioned rely on custom styling. Allowing that in the cloud editor is not on the roadmap at this point in time.

I really appreciate you taking the time to reach out and flag these gaps to us in such a well structured way!

 

Joni

TAGS
AUG Leaders

Atlassian Community Events