Just make sure to delete any comments before publishing your page. Hint: In-line and page comments can be extremely useful during the documentation drafting process. When you share pages with reviewers for their feedback, make sure you change their restrictions accordingly. This might mean keeping draft content exclusive to select team members or restricting a public page to staff members until it’s ready to be accessible to the public. With that in mind, you should restrict permissions as soon as you create a new page. When pages are in draft state, half-finished or littered with comments, it’s best practice to keep them hidden not only from your external users, but also from internal team members who don’t need to input on them.
When you’re creating new pages, you’ll likely want to develop them over time, and often with the input of other team members and stakeholders. Step 2: Implement Confluence permissions to make content more (and less) accessible Hint: If you’re not familiar with Confluence, check out Atlassian’s documentation on getting started in Confluence Cloud. You can then name your space, add a description and set permissions. For organisations already familiar with and actively using the Atlassian suite, Confluence is a natural choice for documentation. Its intuitive interface and powerful editor makes it easy to create content, pages and spaces - and that’s before you start using Confluence macros.
#How to use confluence and jira together software
This allows technical writers, software developers and marketers to work in harmony for quicker, more accurate documentation creation.Ĭonfluence’s simplicity makes it ideal for users of all experience levels to create documentation worthy of an external audience. Couple this with the fact that it’s a web app and you’ve got a platform built for teamwork - no matter where colleagues are in the world. Why should you use Confluence for documentation?Ĭonfluence is extremely collaborative. That makes it even more important to focus on your documentation now and into the future.
%20(1).jpg "how to use confluence and jira together")
According to an SDL survey, 41% of millennials search for online tutorials, 33% search for technical documents and manuals, and 72% say that product information affects how they perceive a product. This is only set to increase with the millennial customer coming of age. Technical documentation plays an important role in the overall customer experience and can influence purchase decisions, renewal rates and customer satisfaction. It should be constantly updated to reflect technological and software updates, and good documentation will not only be correct, consistent and complete, but also navigable and user-friendly.
#How to use confluence and jira together how to
Documentation should display and describe what a product is, how it works and how to use it properly. What is documentation and why is it important?Īlso known as technical and/or product documentation, the term “documentation” covers a wide range of information, usually organised into - surprise! - documents. Here’s why you should use Confluence for your documentation and how you can make it as clear, user-friendly and interactive as possible. It can also be used to create technical documentation for external users of your products. Whether it’s used as a company wiki, department hub or co-working space to facilitate remote work, Confluence’s flexibility, accessibility and customisation potential makes it a go-to choice for teams all over the world.īut what about external use cases? Confluence’s adaptability doesn’t stop at peer-to-peer collaboration within organisations. Confluence is an incredibly versatile tool with a number of different applications.
0 kommentar(er)
