The Confluence, Tech Comm, Chocolate wiki has moved to a shiny new site

The Confluence, Tech Comm, Chocolate wiki is a companion to my book about technical communication, technical writers, wikis and chocolate. This week we moved the site to a shiny new Confluence OnDemand server. Please take a look, sign up if you like, and also please consider changing any external links you may have pointing to content on the site.

The new address of the Confluence, Tech Comm, Chocolate wiki is:

The old address was:

What does the move to Confluence OnDemand mean?

Confluence, Tech Comm, ChocolateConfluence OnDemand is Atlassian’s new hosted platform. Our site will now automatically get the latest and up-to-datest version of Confluence. It’s currently running an early version of Confluence 5.0! So we’ll be able to play with the latest Confluence features before anyone else. If you’re interested, keep a watch on the frequently-updated Atlassian OnDemand release summary.

My seat-of-the-pants feeling is that the new site is significantly faster than the old one. 🙂

The hosted platform restricts certain functionality, primarily add-ons and customisations of the wiki. I won’t be able to install add-ons or plugins that are not pre-approved by Atlassian. This won’t have a big effect on people using the site. We no longer have the awesome add-ons from K15t Software for creation of ePub and DocBook exports. The Copy Space plugin isn’t there either. Gliffy, for drawing diagrams, is available in Confluence OnDemand, along with the add-ons listed here: Atlassian OnDemand Plugin Policy.

Existing content, redirects, and external links pointing to the site

This bit is for the 77 people already using the wiki. 🙂 All your pages, blog posts, comments and other pieces of information are safely on the new site. Please let me know if you spot anything amiss.

Atlassian has put redirects in place. If you try to go to the old address, you should automatically end up on the new site. The old site will be decommissioned in a few weeks’ time. There’s no scheduled date for the shutting down of the redirect service, but it’s probably a good idea to update any external links you may have, to point to the new site.

The book

The book is called Confluence, Tech Comm, Chocolate: A wiki as platform extraordinaire for technical communication. It’s about developing documentation on a wiki. It’s also about technical communicators. And chocolate.

Do come and join the fun at the book’s wiki site: Confluence, Tech Comm, Chocolate wiki.

About Sarah Maddox

Technical writer, author and blogger in Sydney

Posted on 5 January 2013, in atlassian, book, Confluence, confluence tech comm chocolate, technical writing and tagged , , , , , , , , , . Bookmark the permalink. 2 Comments.

  1. Hi Sarah,

    I recently bought this book since I wanted to propose Confluence for technical documentation in my organization. However the issue that I am currently facing is that we have a suite of products (say A, B, C, D, etc) accessible through a single GUI. Our customers can subscribe to any combination of these products (A+B+C+D, A+C, B+D, etc). Currently I have created Online Helps for each of these products using RoboHelp (that is, one for A, another for B) but they are separate entities and do not provide a complete user experience to the customer for all the subscribed products. Is there a way in Confluence using which I can resolve this? Thanks!

    By the way, I really liked your book! Very well written!

    – Ritesh Pai

    • Hallo Ritesh

      Thanks for dropping by. I’m so glad you enjoyed the book. 🙂

      To solve your problem in Confluence, I’d do this:

      • Install a Confluence site for your product suite, and brand it for the suite to give a unified look and feel.
      • Create a space in Confluence for each product: space A, space B, space C and space D.
      • Create a group for each customer: customer 1, customer 2, and so on.
      • Put the users into the relevant groups: users for customer 1 in group customer 1, users for customer 2 in group customer 2, and so on.
      • Assign space permissions to the relevant groups. For example, if customer 1 has products A and C, assign space permissions to give that group access to space A and space C.

      This way, each customer’s users will see the docs for all the products they own, and only those products. They’ll have a unified experience, because all products are in one wiki i.e. one site.

      I hope that helps!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: