Open issuesSwitch filter

Please provide a way to fix the font on Confluence. The new font is major regression in readability, in particular lowercase "A" no longer looks like an "A", which makes technical documentation much harder to comprehend. It also fits less text on the page than before. Even if there is no plan to implement a fully customizable CSS, please at least allow users to set up Confluence to respect their OS and browser default fonts. It's an accessibility issue if nothing else.

See also: https://jira.atlassian.com/browse/CONFCLOUD-79312

It is hard to understand. We are also a customer of Zendesk, also a cloud ap. We can change the CSS to give a custom look, we even can modify the page templates to add more functionality or just to customize how our instance appears. Does not appear to be rocket science.

Same here (commented on this ticket back in 2023) ... I used to be a huge proponent of Confluence in my company, power user who crafted custom macro, CSS, etc. to encourage better experience/adoption. 

The cloud migration was the beginning of the end for me; after trying to get some traction with a few support tickets to Atlassian and seeing not much happening, I stopped investing my time in this product, and looked for as many alternative tools to use (in the right context) as possible since then.  Shame..  

I commented in support of this post in 2022. Very disappointing that nothing seems to have happened on this front. .  We're now moving 2 of our wikis off the platform, in part, for lack of creative control.

This ticket has been open for 13 years now.

Adding the ability for custom CSS is not difficult and would help us make our Confluence sites properly ADA and EU compliant. Can this please be made a priority? It's very difficult to use the site the way it is, there is little difference with headings, the expand component is inaccessible, there are so many issues that could be fixed with a bit of CSS.

Please add back this vital capability.

e83115ee9df5  of course, but not in this wide forum since it is intellectual property we are talking about (our product documentation). The new content renders with the new font, but I managed to find a workspace that still renders with the old one.  Let me know how we should do this.

**Update: a few minutes later the CSS was pulled onto the open workspace automatically, so now the last example I could show you to demonstrate the difference between the two UIs is now gone  

Maybe you could try to set the old fonts back in a test environment and compare it with another one using the new one?
(You'll need sg that has a 3-4 levels-deep page structure and childred display macro that displays a list of the child units in the parent page. )

The old look&feel is WAY tidier. This new one has no right browser page zoom level...it looks chunky and too wide on 90% as well as on 100%.  

Also, I agree, it is much harder to follow with the eyes when reading as well as when writing. Maybe the typography is good for marketing but for sw Documentation spaces - it is too heavy.

I don't have before/after comparisons - just impressions - but it feels like the new font is distinctly taller, and thus pages are ballooned into longer segments.  This is taking me back to the days when schools specified which font you had to use on your writing assignments so that you didn't meet the page requirements by using a particularly large or wide font.

I would say that the font is less readable not due to legibility on screen, but due to having to scroll a lot more and move the eyes faster to keep up with the reading.  If the editor had the ability to adjust font size for standard paragraphs (ie not using headings), that would help.  Otherwise, :shrug:.

bad92bfe054e Could you possibly share some screenshots of the places you find Atlassian Sans to be particularly problematic? We've heard a lot of positive feedback on it thus far so I want to make sure there isn't another issue happening on your pages unrelated to the new font. Thanks!

I'm crying inside....the Atlassian Sans looks way worse in Confluence Wiki than the one before - documentation spaces look as if they have just got a severe beating, in terms of UI visuals. Sorry designers, it may be a good decision on high level but not for the Confluence wiki (Cloud). 

Please, please add a switch that allows us to set the wikis back to the old fonts (for the Confluence Wiki product at least...)

The new font is not very readable on screen and it demands extra bits from the brain (at least from mine) when working with it.That is measureable in screen activity time btw....and in working hours
in the long run, due to the fatique factor.
The UI font for a tool (any sw that is used as a tool) is best if it does not demand extra attention, but it is smooth and easy to work with. The new one is visually more demanding, the wiki content looks squished and chunky and it seems that every character is bold.  It is like being presented with a set of Duplo as an "upgrade", when we have been playing with Lego for years. (well, just like the new editor's toolkit interface, sorry...) 

I'd like to have an option to set the old fonts for our Confluence wikis.
Please provide a toggle (switch) option among the Confluence site admin AND the space admin settings...

I and my team have been using small blocks of custom CSS in many of our Confluence Datacenter pages to format elements of the page for easier reading and flow, some of it text-options like colors, some of it background colors for some sections that aren't "info" or "warning" sorts, some (and this is a big one for us) to "float:right" some image- and info-boxes to one side (with text flow-wrapping around) as asides, etc.

Now that we've migrated to Confluence Cloud, I feel like we've been set back quite a ways in terms of options to reader-friendly format many of our documentation pages.

The "legacy" Cloud editor supports a "style" macro that does pretty much what we've been doing, it's just a bunch of unexpected work to migrate each page's existing macros to this one. However, some pages have (mostly unintentionally) converted to the "new" Cloud editor (and I don't see a way to switch back, and I'm guessing that all will eventually be expected to) which, as far as we can tell, supports nothing of the sort, and so there appears to be no way to do what we've been doing with custom CSS in our Confluence pages for years.

It feels like a serious functionality regression, and is extremely frustrating.

Why has support for custom "style" macros (and general insertion of custom CSS) been apparently discontinued? And how can we get it restored?