The left-hand page tree nav bar just disappeared from my space, and I can't find any way to navigate other than searching. There doesn't seem to be a page tree anywhere in the Space Tools.
I can't find the admin tools to log a support issue, either.
OK, probably I didn't get the difference between some JIRA Tickets mentioned elsewhere in the discussion an Support Tickets. No problem.
This sounds familiar... Is it where Confluence adds a blank line before and after lots of macros? You can delete them but they immediately reappear?
Anyone found a way to change the colour of anything?!
The old UI enabled me to change the colour of the navigation bar across the top of the space. While it was only a tiny bit of customization, it meant I could see quite quickly whether I was in the right space or not. Now all my spaces look the same at a glance. If I go to Look and Feel -- Themes, I have no 'themes' to choose. It seems that I have to install an add-on from the Marketplace. The only applicable add-on (RefinedSpaces for Confluence Cloud) gets really bad reviews, nor is it free. At this point, I don't want to pay another penny (cent!) for the tool.
Is this another thing that's been taken away?
All I've been able to keep is my customized colored headings. I used to add a picture in the navigation bar, lost too...
For your answer, I did receive this mail from Liron. Didn't you ?
Space colors and the new ConfluenceHi Bruno,My name's Liron, and I'm a product manager on the Confluence team.You may have heard we're rolling out a shiny new version of Confluence, and there are some big visual changes. As part of the process, I'm writing to let you know that we've decided to remove the ability to set a color scheme for each space. Our analytics show that one or more of the spaces on your site are using a custom color scheme.We're removing custom color schemes for spaces to provide a consistent experience for Confluence users, where the colors of text, links, headings, and navigation items don't negatively affect readability or accessibility. You can still have an avatar for each space, and brand your Confluence site by adding a logo, title, and color for the global sidebar. To provide an easy transition, we'll automatically migrate existing logos and header colors (if you have them) to the new sidebar for you.
Seems our custom templates have broken as well. This inability to brand the pages makes it now unsuitable for external use.
Is this something that will also be implemented on the self-hosted version or shall we start looking for something else that integrates with Jira?
@Martin Sauter and @Helen Griffith: Check below the same page in "old" and "new" experience. (I had to shrink new page to show all the extra spaces - have added arrows to highlight.) Old experience is compact - new one too sparse!
Hi - is it your custom page creation templates that have broken? That would really be a huge problem for us... or just the site look template?
These changes are going in entirely the wrong direction.
Rather than constraining configurability and functional extensibility, Atlassian should be enhancing configurability, enabling site administrator/developers to totally customize the look, layout and what functionality is presented on different sites, spaces and pages in Confluence (and JIRA, for that matter).
Yes it should come 'out of the box' with one (or more) slick, fully functional UI look, layout, color scheme, and presented functionality that a significant portion of the customer base will use with few changes.
But, the same way that we use many custom page templates with page layouts and interacting sets of macros, the entire site and individual spaces should be fully configurable. Some customer teams may then create radically reconfigured solutions for entirely new use cases which could benefit you when shared with the community.
Totally agree with Helen - sometimes you want spaces to be instantly recognizable, not 'all the same for consistency'.
IFF you've implemented with a clean separation of responsibilities architecture (model-view-controller...) you should end up with a toolkit of functionality that the Atlassian devs use to configure the 'default' site - just expose that to the user admins.
Two of the best things about Confluence have been the macro extensibility and the REST API. Why not extend that to full site configurability?
I believe both "consistency" and "configurability" should be within reason. Both should be kept simple. While I will vote for allowing different colours for spaces as a SIMPLE configurability option (even if it compromises "consistency", if you will) - but for nothing fancier than that. Similarly, content is the key artifact in Confluence, so I agree with Atlassian that configurability should be limited.
(I have some new users complaining that Confluence editor is not as rich as Word! Of course, I tell them. It is there for collaboratively creating content - not for creating industrial strength webpages and documents.)
Atlassian's notion that spaces should be consistent demonstrates a profound lack of knowledge about how some people use Confluence.
Or maybe they do know, but don't think it's enough customers to bother with, especially when third-party plugin vendors may pick up the slack.
Point taken.
The thing is, Confluence is now so feature- and capability-rich that it spans the gamut from being used in the original spirit of wiki-wiki, with the focus on simple collaboration through basically formatted text and image content, all the way up to enterprise documentation and integration with other tools.
It has transcended wiki-wiki and is getting closer to being usable as a fully collaborative hypermedia knowledge capture and creation space.
This is something some of us have been envisioning for years - if it can be bent (configured...) to our evil will (cue maniacal laughter...). With page content serving as input front ends or live outputs from other tools, using labels/page properties/reports to auto-index content, using Comala Workflows for traceable CM of content, etc., the potential utility is massive.
Something like Sharepoint or other 'content managers' are not even comparable because they are still totally mired in the "dead tree" document paradigm of managing files, not actual hypermedia content. Old school notions of "documents" need to be replaced by versioned slices through versioned atomic elements of the hypermedia space... and those nodes may themselves be portals into other spaces or functionality or actually reflect executable processes.
Having UI configurability available helps enables this: site and space layout, where the menu elements are, how they look (icon, font, size, color, default pop-out state) and which of the items available on that menu element are displayed (icon, font, color, order, spacing, etc) should be configurable, as should be the default page layout, fonts, etc.
Perhaps I'm asking for too much...
But... 20 years ago I was fully documenting and executing GN&C design and validation processes in an early hypermedia environment.
@Bruno Miretti - no, I didn't get the email from Liron... @Liron, is there any chance I can keep my different spaces' colors?
@Abhay Patil - wow, that's a lot of whitespace... I've not noticed that (yet).
In the name of good aesthetics please vote for the bug https://jira.atlassian.com/browse/CONFCLOUD-57204 !
This might be off-topic, but I can't find the Search bar on top anymore either. Since searchability is one of the key features the 'selling-to-business' is based upon, this is key.
Is anyone experiencing the same?
I strongly agree with your statement, Susan.
The search box is now hidden behind the magnifying glass icon in the new sidebar on the left hand side. Another UI change which I deeply regret.
Yes, so I'd noticed, thanks. I just didn't perceive that to be a realistic replacement for the search bar because it offers less functionality.
What if a product positioned itself as a knowledge base tool and has KB templates in its product and was previously delivering search results in the search box, yet now isn't anymore?
I am afraid I might be agreeing with a fair amount of the comments on this page about the UI changes recently, it not being the best of changes.
It's aboslutely horrible, I was just getting the hang of using Confluence, telling my staff to move on to it. Now I really regret it.
This is the most unintuitive layout/ UI I have ever seen. There 's nothing like hunting for your important information and not finding them where they used to be.
Whoever suggested this is a sadist.
A real killer when it comes to improving customers' life.
Count me in. I don't care if was not pretty but the new layout is neither pretty or useful.
I've voted for your ticket... Please vote for mine https://jira.atlassian.com/browse/CONFCLOUD-56932 (it's a problem with fonts with the Page Tree macro).
I swtch between jira and confluence quite a lot and now this switch is at the bottom of the left hand sude, and takes a lot longer than before to actually do the switch. Anybody else experienced this?
I have now also noticed a scroll bar underneith the side menu-bar. I don't think this should be there.
If you expand the side menu to it's full extent it takes up quite a lot of real estate on the screen. Focus should be on content, in my opinion.
Quick, obvious access to effective Search is one of the most important features and advantages to an integrated, hypermedia environment. It is always the first thing I tell neophyte users to rely on.
The loss of the single-click easy to use search box that is always available and immediately obvious at the top of the page is a totally regressive change.
I forsee a lot of work creating custom navigation pages and page templates with search and pagetree on them so our user base doesn't get confused. In other words, recreating what Atlassian has taken away or made hard to find.
Atlassian will probably tell you that the new UI still offers a single-click search. The problem is not the number of clicks; the problem is
a) that the searchbox is hidden behind an icon
b) that the search icon is at an akward position (search is usually top right)
But for the rest I fully agree with you.
Yes, and I've gotten that response - which is technically correct - but its the problem you more precisely describe that confuses users!
Hi Stéphane - you are quite correct! That horizontal scroll should not be there. It is in fact a bug that we're working to resolve right now. Thank you for raising this issue - a fix should be out shortly.
@Martin Sauter not to disregard your point – just thought I'd mention you can press the " / " key to jump straight to the search both in the old and new design if you weren't already aware. Hope it helps
Please bring back the page tree by default. For my users it's the most important feature of your product.
Please bring back a simple search box to all pages on confluence. For my users it's the 2nd most important feature of your product.
Thanks
Hi Caroline,
Thanks for looking into that and confirming that this is a bug. Good luck fixing it. I would however also look into the necessity of a vertical scroll bar as well.
From UIX perspective a vertical scroll bar in a side menu is difficult to 'aim' for on a PC or a Mac, let alone a mobile device.
It looks like you're new here. Sign in or register to get started.
