nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Add a Section Macro- Doesn't Jive with Version Documents and Users are Asking

Jeff Lapsley

Good afternoon community,

We are on Confluence cloud after migrating from server version. One of our PMs is complaining about the ADD SECTION MACRO where it no longer has the ability to move sections, or add sections. he took a screenshot of the current Confluence documentation when I told him of the editor changes a short while back, so I am looking for confirmation on what the actual current state of things is RE the add section macro.

The actual toolbar no longer includes any of the wording, and only has 5 icons for layout... nothing for moving or adding. Screenshots to follow.

What the documentation toolbar looks like-

And what we see in reality-

What is the real toolbar? If the new one is the smaller one, how do I tell users to move sections around?

Thanks!

Accepted answers

Dan Winkler_0y432l

@Jeff Lapsley This is an intentional feature of the new editor, and it's been discussed a bit elsewhere, including a response from the Atlassian team.

All comments

Dan Winkler_0y432l

@Jeff Lapsley This is an intentional feature of the new editor, and it's been discussed a bit elsewhere, including a response from the Atlassian team.

Jeff Lapsley

Thank you Dan. I had come across some of this discussion RE the new editor, it was that the current documentation does not reflect this. We try to have our users do SOME looking on their own before engaging support, so we got some complaints on this one due to docs not matching.

Thanks for the confirmation!

Jeff

Dan Winkler_0y432l

Hey Jeff, makes sense, I did see your reference to documentation and meant to add this thought which I forgot to do at the time.

My thought was, without speaking for Atlassian, I wonder if they're trying to maintain documentation for the old editing experience while they're rolling out the new. Like you, I've recently seen documentation for the old experience, including pages that refer to macros (the Panel macro, for example) that are deprecated in the new experience. I can absolutely understand the confusion that your PM experienced.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud