Best practices
This page includes best practices based on working with engineers, product owners, testers, and other Confluence users. Some best practices are directly associated with default platform features, while others are more process oriented. A single page is used for all best practices instead of a collection of child pages because the best practices are not associated with actions and statuses and a parent page is not needed to collect and display this summary information.
Writing guides
Every organization should adopt one of more writing style guides based on the team, project, company tone, and other factors. Many established guides are available and their guidelines should be adopted (or rejected) as needed.
For a technical audience the following guides are available free of charge from the tech community.
About this guide | Google developer documentation style guide | Google for Developers
https://redhat-documentation.github.io/supplementary-style-guide/
For a nontechnical audience the following guides are available with a subscription.
When a guide is adopted it might be useful to include a summary of the top guidelines to help writers focus on what’s most important. The following summary is from Welcome - Microsoft Writing Style Guide.
Rule | Description | |
---|---|---|
1 | Make every word count. Concise, clear sentences save space, are easy to understand, and facilitate scanning.
| |
2 | In second person, you write as though you're speaking to the reader. The second person often uses the personal pronoun you or your, but sometimes the word you is implied. It supports a friendly, human tone and helps avoid passive voice by focusing the discussion on the reader. Omit you can whenever the sentence works without it. | |
3 | Voice is either active or passive. Keep it active whenever you can.
| |
4 | Use sentence-style capitalization in most titles and headings: capitalize the first word and lowercase the rest.
| |
5 | Organize text into discrete components to support scanning. For example, replace complex sentences and paragraphs with lists and tables.
| |
6 | Be consistent in your use of numbers by following these guidelines:
|
Editorial workflow
Additionally, an editorial workflow should be established with at least one editor identified to enforce the guidelines - especially for external-facing documents. A typical editorial workflow in Confluence includes the basic steps described below.
Step | Description | |
---|---|---|
1 | Write | Create an initial version of the document.
|
2 | Review | Get feedback from key stakeholders.
|
3 | Approve (optional) | An approval is the final review.
|
4 | Lock (optional) | Prevent user from editing the page.
|
Searching content
Confluence does not always display search results in the order you expect. The main factors that effect search ranking are:
The content type of the matching item including pages, blog posts, and attachments.
The field type in which the matching term was found including title, body content, and labels.
The recency of the matching item based on when it was created or last modified.
For more information refer tohttps://confluence.atlassian.com/doc/ranking-of-search-results-1188406620.html. Note that this article applies to the latest installed version of Confluence and may not completely apply to the cloud version.
To increase the effectiveness of your search results, follow these steps:
Add keywords - Define keywords for each page and add them to the page title and body.
Use Advanced search - Search for exact matches, or search for keywords using logical operators or wildcards. Refer to https://support.atlassian.com/confluence-cloud/docs/confluence-search-syntax/.
Filter search results - Use the Advanced Search filters to get the most meaningful results. Refer to https://support.atlassian.com/confluence-cloud/docs/search-for-pages-and-posts/.
Reducing email notifications
When there’s a lot of activity in Confluence, you can be overwhelmed with email notifications. You cannot eliminate all email notifications. For example, you cannot eliminate notifications when @mentioned. However, there are two ways you can reduce email notifications.
Stop watching pages or a space - You can watch pages or entire spaces and you'll receive email notifications whenever the watched content is added to, edited, or deleted. To stop watchings pages or a space, refer to Watch pages, spaces, and blogs.
Modify your email settings - You get email notifications when you “watch” pages and spaces, and Confluence will then send you a notification whenever anyone adds or updates content on that page or space. To reduce email notifications, refer to Subscribe to email notifications.