Please provide a replacement for allowing us to add classes to content blocks. This is critical for us when we export our Confluence pages to our publishing tool. 

It doesn't even have to be a proper div, but please let us add classes to blocks. 

I'm very disappointed in this decision to deprecate the style module. When we switched to using confluence we wanted to preserve the two levels of delineation like we had with Zendesk Guide. That wasn't easy to achieve in confluence, and we were only able to successfully achieve the way to organize information in a readable way by using the style macro to style the children display macro. The stated reason for deprecation was performance, but I'm happy to have my pages load just a little bit slower so that I can insert a few lines of CSS. Please reconsider deprecation, even if that macro comes with a warning or is opt in to turn on or something.

We are using DIV and STYLE Macro to show excerpts in an overview page in a dynamic formatted way. This is not possible with layout function and gallery macro.

We use the DIV macro to include content that is hidden when printed using a css class to Not print in pdf. 

So, we can create pages in confluence with content for internal use, and when printing for the client that internal content is not included.

What can we use instead of a div?

Why was basic HTML functionality removed?

It is so useful...

Aurélien. In the new editor, Atlassian has removed your ability to flexibly customise your output. Please don't ask why this has been done—Atlassian is entitled to reduce product functionality and usability if it wishes.

Please try to remain positive about being unable to do your job properly. If necessary, you can find another job. Atlassian doesn't care about you or your working practices that rely on a product it is determined to phase out.

We are using the style macro to customize the table of content look, how can we handle it now ?

I overlooked the handful of templates we use for creating standard look-and-feel documents. They are stuffed full of DIV macros, so they will all fail when migrated to the new editor. And there was me thinking Confluence Cloud was as bad as it could get.

We use the span macro with specific styles to look like the buttons we have in our software and insert these styled span macros into tutorial texts. As an alternative way we could use the status macro but in the new editor this macro has only 30 characters possible and to less colors. We don't want to use buttons as graphics within the text.

For inline explainations of words or definitions of some terms we use the span macro with a title which is shown on mouseover like a tooltip. The hovered text has a dashed border at the bottom. Is there a possibility to add an inline help in another way?

For all those who want to throw Confluence in the garbage because Atlassian ignored its customers and removed the facility to insert a page break in PDF output (among a plethora of other annoying retrograde developments), try the following workaround.

Use the Table of Contents macro as follows:

Insert a Table of Contents macro where you want a page break, and apply the following:

1. Minimum Heading Level = 7
2. Maximum Heading Level = 7
3. Select the Printable option (else it won't have any effect in the PDF output)
4. Add the following CSS to the PDF stylesheet: .toc-macro {page-break-after:always;}

As long as you restrict your headings to levels 1 through 5, the Table of Contents will be invisible in the online version of the page, but it will produce a page break in the PDF at exactly the place(s) you require.

10 points to me for persevering and finding a workaround. Zero points to Atlassian for ignoring the issue and/or playing it down in the hopes that we will simply change our working practices, settle for a reduced-functionality product, or migrate all our content to a competitor.