I've been a Confluence user and admin since 2010 and am still bewildered at the lack of some basic included features that should have been there for 10 years already - despite innumerable requests and incredulous questions from end users - which would make the product so much easier for end users, and less of a drain on IT / developer people who have to provide so much assistance due to lack of these basic features. many other CMS platform already have many of these features - it's time for Atlasssian to catch up.
Below is a list of basic features that in my opinion need to implemented ASAP to ensure end user adoption and frustration reduction. Please vote up this post and add any additional missing standard features you've found to be critical for your end users and maybe we can get Atlasssian to take notice.
Media / Attachments
That's just not the case I found across multiple instances for multiple companies for the past 10 years. End users are very frustrated and view Confluence very negatively as they struggle to create or edit content and perform basic tasks. I personally use every developer level tool, language, macro, add-on as I need to - it's not about me it's about regular people who find the lack basic features infuriating.
So you are discounting custom CSS to address many of these issues, either site-wide or space level? As a tech writer, I want to control the look and feel for the entire site, and not end up with a hodge-podge of users styles. Many of these items I set with CSS or a combination of user macro and CSS.
Just asking for another perspective.
Thing is, it's a wiki, for people to share and collaborate on content. Styles in Confluence have been kept basic and standardised because that's what it's for - standardised content delivery with the contributors not having to think about formatting. It's not a web page layout tool, it's about the content.
Like @Bill Bailey I would use custom css to standardise on the organisation's desired layouts, and then concentrate on the content.
On some of the specifics:
This is specifically about the usability of the platform for end users who are not going to learn CSS, HTML, macros, add-ons etc. etc. just to write and collaborate on content. I spend an inordinate amount of time supporting people to do very basic tasks that should be included and obvious to end users.
I think you're missing the point that Bill and I are trying to get across - it's a content tool. Not a content formatting tool. Most users don't need or want all the things you are asking for here, because 99% of the content simply doesn't need it.
That's not my experience with it - the overwhelming majority of my users are interested in content not formatting. So Confluence works for them. The stuff you're asking for is not "basic", it's complex formatting that most people find pointless.
Having been a confluence admin for the past 5 years but also a tech writer using Confluence to develop customer documentation, it is a feature not a bug that the formatting is controlled via CSS. How else can you control the look and feel to match corporate style/brand standards? And if management tells me tomorrow "Comic Sans is the way!" It takes me one week of explaining why that is a bad idea and 15 min to actually change it for the entire site.
If groups with their own spaces want to go a different path, I will give them my source CSS and tell them how to change it for their spaces.
There is already a plugin for numbered headings. Column and section flowing would be REALLY hard to do – for that type of layout I use FrameMaker or InDesign.
Easier capping options would save me a ton of time.
On tables, there is already cell merging, so not clear on your comment there .And I have a very simple nowrap user macro that users can use to control the min width of the table column, but that is a kludge (but effective).
Now preset table styles would be really nice.
Bottom line, I agree with most of your table options. And better attachment management would be good.
It just goes to show that there are a wide range of use cases for Confluence. Many companies are equally concerned with the look and branding of the intranet content. I use custom CSS, Theme Press and other custom code and have hired third party Confluence developers for soup to nuts customizations and overall style and branding control - that's not what I'm talking about. I'm talking about the same kind of content control that you find in any decent word processor or presentation tool which is exactly what Confluence is.
In general it's a fantastic tool but it could be so much better for end users tasked by their company to contribute and manage content with some long overdue additions.
And yes I know there is table cell merging - I left that on the list by mistake.
Call it what you want but the basic features for END USERS that Confluence does and doesn't have appear to be arbitrary and frustrating to the end users I deal with on a daily basis. Through this thread I'm just calling attention to it so I really appreciate your participation and valuable comments.
Yes, I see that, it's just that much of what you're asking for is absolutely not "basic". They're advanced formatting that most users of a content system don't need (or want. No-one I've worked with needs any of that stuff. They want to write and have their content delivered)
Note that I'm not disagreeing with you on the attachments stuff - the functions that Confluence provides there are basic already and good enough, but the additional suggestions, while not "basic", would be quite handy.
The original question is a very valid one.
I have an idea about the minimum requirements a tool should fulfil if it is to be used in technical documentation. This includes:
Now, how much of the above is available in Confluence right out of the box?
It is, although it does miss the point that a wiki is not an authoring tool.
I'm not sure that automatic numbering is that useful for a wiki, as generally you're reading it online, and numbers don't add a lot. Off the shelf, you need an add-on for the headings.
The other three items are all there in Confluence - macros for toc, gallery, tables, cross-referenced links, and page properties.
Well it already auto generates a ToC, both in the left-hand side and on the page with ToC macro (and can be saved in a template for user use).
Numbering I disagree with – so 1990s. Numbering really has no meaning with online documentation. If you want numbering in print, you can do that with Scroll PDF (and some CSS).
You can add a link to any item now. Headings are easy to do, the rest, you have to insert an anchor (or did as I did, and write macros to style and add an anchor to table and figure titles).
The variables are already there, but you have do some programming to get them to appear on page export. But much easier with Scroll PDF (still requires knowledge of Velocity and CSS).
Bottom line with Confluence, just like FrameMaker or InDesign, you have to learn the tool to be able to generate professional-looking results
That's because it's aimed at being an active collaboration tool, not for static dumps of (potentially obsolete as soon as you click print) information. I'd agree it's not great at that, but it's not what it is for. And the weaknesses are patched over by add-ons for the people do need it.
Of course an advanced wiki like Confluence IS for authoring and ongoing editing and collaboration. Excellent tools like the Scroll add-ons provide excellent output in addition to the many incredibly useful tools provided by third parties. My issue is that Atlasssian really needs to cover the basic features much better to simplify the work for end users who are not programmers and just want the write an edit content without having to become programmers.
It's still the idea that these are "basic features" that is a bit odd to me. They're not basic, they're advanced layout and formatting things that most authors do not need or care about.
I never used any of them before I started using wikis, and I certainly don't use them now. In fact, I used to remove them when I found them in documents. (and yes, technical author has be a large part of many of my roles for years)
I do care what my content looks like. I have no time to spend on learning every nuance of CSS. I think @Clinton Bradley makes a good argument. I hate that it takes so long to get a result that I am really happy with. I need to be able to format content for lots of reasons. I respect what @Nic Brough says, but, personal style/prefs might be playing a part in his opinion.
I care about it too, but consistency, ease of reading and use, and, most importantly, content, are far more important than the layout and attempts to be visually clever.
My personal preferences are not good for most people, so I've completely ignored them in this conversation. My second choice is for clear and standardised text that I can simply write without having to worry about complex formats, and far more importantly, the audience can read easily. Changes in style, font, layouts, colours and so-on distract from the ease of reading. Yes, they make it a bit boring to glance at, but again, Confluence is about content, not style.
And no, I won't "boo" you for suggesting mediawiki. If it's the better option for you, go for it! (And, IMHO, it's very good software too)
p.s. if I were to make changes to the Confluence editor, there are three things I'd do - remove italics, build in contrast checker to block people using bad colours, and hard-code something to override any attempt to use comic-sans as a font in the css.
@@Nic Brough [Adaptavist] Thanks for being a good sport. I agree with the ban on comic-sans and bad colors my company is looking at a few ALM tools. Atlassian is the front runner but I am constantly shocked at some of the areas where features are lacking. (like importing projects from JIRA server and cloud to a JIRA cloud instance - I can import redmine data easier than I can JIRA data and that just mystifies me).
I'll bite. I'm a somewhat long-time user. I'll be up front, I'm with the popular opinion here: This is not for content formatting. This is for content generation and collaboration. They do not claim to compete with 'office suites.'
Word processors like Microsoft Word and software that competes in functionality with it are focused on allowing you to do anything at all with coloring, fonts, size, shape, boxes, etc and so forth. Microsoft Excel does something very special (plus they give you all the formatting options to hang yourself with ) and this collaboration tool isn't out to change that. Unfortunately much business time is wasted creating insane XML structures in Word and Excel documents.
I've had good luck with Confluence and it's PDF export customizations but maybe I'm just a wizard. image2016-1-27 19:16:18.png
More and more people are building their careers with Atlassian, and we want you to be at the front of this wave! Important Dates Start the Certification Prep Course by 2 April 2019 Take your e...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs