This has been a discussion long debated in our office. To be honest, most of us just dump 💩 a ton of text on a page which quickly dissipates into the ether.
Do you take the time to build formatted pages with tables that link to Jira, insert charts or diagrams, or embed Confluence pages within Confluence pages (Confluence-ception)?
I need to know... How do you and/or your co-workers make Confluence pages that are easy to read, understandable and referenced regularly by the org?
In my previous company I used to maintain a plugin. Technical writers used to use all sorts of tools. Writing text with pictures created with gliphy or using an external tool. For tables we had purchased a plugin at that time.
Our plugin would then generated a PDF and HTML bundle. That was then shipped with the product that the company was building. We used it for product documentation.
There were no references to Jira issues in our Confluence pages.
Have me write it?
Seriously, if you're gonna set up a straight line like that...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.