Why is Confluence our tool of choice when it comes to documenting UX design concepts and why should you use it? The answer: collaboration, flexibility and a single source of truth.
Posts tagged with Confluence
Confluence is a leader in the content collaboration tool space, allowing entire organizations to access and contribute to information within a single centralized knowledge hub. Sometimes however, Confluence users need to export this documented knowledge as PDFs to fulfill business requirements. Here are four important factors to consider before choosing a Confluence PDF exporter.
No one knows what the future of technical writing looks like. You can however get a pretty good idea if you have a look at the characteristics and philosophies of the people who are newly entering the profession. As a teacher of technical writers, I get to see generation Y in action all the time and perhaps my observations about their ideas and reactions to different editorial systems are an indicator of what is to come.
The time of wikis' widespread popularity are long gone. And yet, the enterprise wiki Atlassian Confluence is more popular than ever. Our guest author found six reasons why this isn't a contradiction and may have unearthed the secret recipe behind Confluence's trend-bucking success.
If you're a Confluence user you have probably tried to create a template for blog posts. Unfortunately, Confluence doesn't support them. Don't worry though, I came up with a solution that everyone can implement.
There are multiple tools that export Confluence pages to Word. I examined how Confluence's built-in exporter compares to the Scroll Office add-on. There are four major differences.
Matt Reiner, content strategist at NimbleUser, explains why he championed the transition from writing technical documentation in DITA to writing with Confluence and Scroll Versions in this guest blog post.
K15t proudly introduces Scroll ImageMap 2.0, a handy add-on that brings Confluence images to life with multiple clickable link areas and mouseover tooltip regions. With its intuitive graphic editor, ImageMap makes it easy to define circles, rectangles, or complex polygons as clickable regions, and make your Confluence images an engaging, informative experience.
Im Durchschnitt vergeudet ein Mitarbeiter 60 % des Tages mit unnötigen Aufgaben, ineffizienten Meetings und der Bearbeitung hunderter E-Mails. Dies belastet die Produktivität enorm. Es ist höchste Zeit für eine Veränderung.
Scroll Versions 3.0 is live in the Atlassian Marketplace, and it boasts a range of new features and functionality. Today, we'll examine some features that give you unprecedented control over your content management: version-based editing permissions, modular configuration. . .
Our most popular exporters just got a flexibility upgrade, allowing the exporting of Confluence content in two new ways: task list export in all Scroll Exporters, and table cell highlighting in Office.
A big thank-you goes out to all who joined us for the Scroll Versions 3.0 webinar. A complete video and all of the submitted questions and a...
Available now in the Atlassian Marketplace We're proud to announce Scroll Versions 3.0, a major release of the best version management tool ...
Atlassian Summit Survey Results Are In It's no secret that Confluence is a powerful platform for documentation collaboration. At Atlassian S...
“No one reads documentation, and nobody gives feedback on it.” This phrase is bad news for technical communicators – but it’s not the whole story. What actually happens in reality hinges on the way we manage and distribute technical content. (Protip: Host it on the web and invite everyone to get involved). This is the second part in our blog post series https://www.k15t.com/blog/2015/07/feedback-please-why-technical-writing-shouldn-t-be-a-one-way-street about the benefits of crowd-enabled documentation using a collaborative approach. In this post you’ll learn how to get readers’ feedback on documentation easily by building collaborative web-based help content that allows technical communicators to elevate the quality of their work to the next level.
For a long time, technical writing was like driving down a one-way street. We’ve sent information into one direction, and nothing came back. But since the age of the Web 2.0, this approach is no longer a best practice. Today, being a technical writer means to communicate and to interact with everyone involved – including our readers. Building documentation heavily depends on feedback, and it’s an iterative process – more like a traffic circle. New processes require new technology – it’s time to move from publishing tools to collaboration platforms. This blogpost is part of a series about feedback in technical communication, In this article, read why receiving feedback is crucial to create helpful technical content and how a web-based collaboration platform can enable both internal feedback and customer feedback.
Today, I'd like to share with you a little secret about Scroll Translations. It’s the Confluence add-on which lets you manage Confluence content in multiple languages within a single space. This makes it simple to add page translations. But how about page templates and blueprints? Does the same apply to them? The answer is yes. It's not only possible to create multilingual page templates – it’s easy. In this blogpost, I'll show you how to modify the troubleshooting blueprint (or any other page template) and make it speak in foreign tongues.
Today, we’re going to settle the question once and for all – which is superior? Documentation in a plain-text editor using Markdown, or creating content in a rich-text editor the WYSIWYG (what you see is what you get) way? How will it be decided, you ask? A good, clean head-to-head fight!
Bringing people together in a collaboration platform like Atlassian Confluence also means transferring your legacy content from multiple information silos. These repositories often contain important information that you can’t afford to leave by the wayside when building a new corporate knowledge base. In many cases, legacy content is only available as HTML files, such as online help resources or intranet pages. Is there a way to bring these assets into Confluence efficiently? Yes – but there is no one-size-fits-all method. There are three main approaches to importing a collection of static HTML pages. Your individual needs will determine which is best for you.
What would you call the image on the right? A ‘drop-down list’? A ‘pull-down’ or ‘select list’? A ‘drop-box’? I recently discussed this very issue with one of our Atlassian Expert consultants. It seems everyone – from customers to consultants, developers and tech writers – has their own name for this UI element. We constantly refer to it in meetings, specs and technical documentation, but often do so in different ways. Consistent wording is key to delivering clear, readable documentation. But when larger groups of authors collaborate to write documentation, they tend to use different words for the same things – such as jargon, or incorrect or obsolete terms. This is where terminology management comes to the rescue. This blog post describes how you can build a glossary in Confluence to ensure terminology consistency. What’s more, I’ll show you a way to check your Confluence content for terminology and writing style.