Basically what you need to do is defining a bunch of labels that express the status of the pages you want to monitor. These labels can be compared to statuses of a simple workflow. For example the label draft can be used for all the pages created but not yet reviewed - the label done for pages ready for review. Pages without a label are considered as reviewed and accepted.

To provide an overview of the state I created a page called _organisation and moved it parallel to the Home page. Doing so, the page will not appear in the navigation tree on the left. This approach is also useful to handle include libraries and additional management pages.

To set up the _organisation page for my two example labels, I created two headings reflecting their names - Done and Draft. Underneath these headings I inserted the Content by Label macro which is already bundled with Confluence. I configured the macros to filter out the pages defining the corresponding labels.

Last but not least I labeled all the pages which should be monitored on the _organisation page. As said before, I used the labels draft and done. Other more complicated labels are easy to maintain as confluence gives you suggestions as you start typing.

After navigating back to the _organisation page via Tools > View in Hierarchy the following result is displayed:

A page showing all the pages sorted by labels. Now it is easy to see what is already done and which pages still need a bit of authoring love.

Image Effects let you put cool effects to your images, screenshots or photos. With just one click on the image and one click on 'Effects' it is very easy to use and the results are stunning. read more

The new releases of all Scroll Wiki Exporters as well as Scroll Office allow you to use image effects in your publications. Of course the new versions also introduce a lot of other improvements and some bug fixes.

If you are interested how these image effects may look like in your publication check out the following screenshots or start evaluating our products today.

Scroll Office Word Exporter for Confluence:

Scroll Wiki PDF Exporter for Confluence:

Scroll Wiki EclipseHelp Exporter for Confluence:

Scroll Wiki EPUB Exporter for Confluence:

Scroll Wiki HTML Exporter for Confluence:

Scroll Wiki EclipseHelp Exporter for Confluence:

Team Calendars are a great tool for teams to schedule their leave, track their JIRA projects and plan events. The plugin has evolved in a great way over the past few months. To take a really close look at what has changed, check the Release Notes.

One of the major new features is the integration of Google Calendar into Team Calendars. This really is a step forward considering that many of us use Google Calendar to manage their daily business as well as their private dates. Google Calendar integrates now with one click.

By adding your teams leave-calendar to your personal Google Calendar you always know who is in the office and who is not. Are you using Microsoft Outlook? Good news for you as well. Use the provided link to subscribe to your People and Event Calendars. For further informations check out Subscribing to Team Calendars from Microsoft Outlook

To stay informed about where your people are at, it is very helpful to have a calendar about that. Leaving on an event with multiple people? Just add them to the same event.

Basically there are three different types of Team Calendars:

Event Calendars
Event Calendars are perfect for sharing any type of event - company milestones, team events, training sessions, or public holidays.
Put them on a calendar that everyone can see and subscribe to.

People Calendars
People Calendars give you an at a glance view of who is on-duty and which team members are on vacation.
Creating rosters, scheduling team leave, and planning travel just got a whole lot easier.

Jira Calendars
Communicating the release plans for your projects is quick and easy with JIRA Calendars.
Share when projects are shipping and view them alongside People Calendars to see how your team's availability will impact your release schedule.

Atlassian Team Calendars have the most of the functionality you know from Confluence Pages. The two most important to me are to be able to restrict or to watch a calendar.

Watching your mates calendar let's you know if you can meet him for lunch or not.

Are you planning a secret feature? Restrict your Team Calendar to your team.

The new features are a big benefit for every Confluence user out there. But especially for Technical Writers and Technical Communicators they are extremely useful.

Let's start with the Instant Autoconvert. It makes it so easy to bring a wide range of content to your wiki and let it look way better than it ever did. The Confluence Instant Autoconvert really automates your editing experience and by that, lets you get things done faster. 
Imagine you just copy and paste the URL of a Confluence page to another page and what you get is a Confluence-Link – no more broken links to Confluence content! That sounds really good to me, thinking about the lots of links in our documentation. This works as well with Jira issues, Flickr photos, YouTube and Vimeo videos, Google Maps and screenshots taken using Skitch.

The new Image Effects lets you put cool effects to your images, screenshots or photos. With just one click on the image and one click on 'Effects' it is very easy to use and the results are stunning. With Image Effects your product release notes and documentation is not only informative, but also very good looking.

Have you ever tried to find and replace a bunch of terms in your wiki? It's a pain right? But not any more! Confluence 4.1 has you covered here as well. The new Find and Replace let's you find and replace terms and phrases faster than ever. This is a big benefit for everybody using Confluence.

Check out this really cool page Atlassian made to show all the improvements on Confluence 4.1: Edit like a pro - Confluence 4.1

To make your documentation and exporting experience even better check out our products here and order a free evaluation license now!

Due to massive growth ;-) over the last weeks and months, we were thinking a lot about leaving our beloved office-community and moving to our own office. We had a very hard decision to leave the old office with all the nice friends and co-workers from different professions we had great times with. But we had no choice.

As already mentioned we were running out of space and had to find a bigger office. By chance we found this very lovely space not to far away from the old one. When we first visited the new location, we instantly fell in love with it. It is in the ground floor of a backyard building located in the west of Stuttgart. We moved last saturday and are still busy setting everything up and making it as cosy as the old one. Now we have approx. 970 square feet with a conference-room and a tiny little kitchen. Underneath it has a huge basement and we are not quite sure yet what to do with it. Maybe we'll use it for the next big release party.

The neighborhood is really convenient with some nice little places to eat and an awesome park to chill in the summer.

You are always welcome to drop by and have a cup of coffee with us.

Have a look:

So tell us, how do you like the new office? 

A great solution for managing approval workflows have been Comalatech's Ad Hoc Workflows: Set-up workflows for certain pages to control the publication of content in your Confluence Wiki. It also comes with built-in task management to let users keep track of required actions.

However, when you needed to export content (i.e. for archiving as PDF), the built-in PDF export of Confluence would not export the approved versions but the latest, non-approved versions of the content. Now there is rescue - the Scroll Wiki Exporters (which export to PDF, EclipseHelp, static HTML, and more) will only export those versions that have been approved. If a page has a non-approved version, the resulting exports will contain a notice about that.

And all this is as simple as clicking a check box during export. If the check box 'Only published versions' is checked, the Scroll Wiki Exporters will only export the latest published version of the exported pages.

If you still would like to export the document with all the draft pages in it, uncheck the 'Only published versions' option. This will give you the document with all the regular pages in it and the ones still waiting for approval. The draft pages output only the Name of the page and the warning message.

Ad hoc workflows works with all Scroll Wiki Exporters: PDF, EclipseHelp, EPUB, HTML.

UPDATE: We got a few requests, whether this feature is also available for Scroll Office. The answer is: Not yet! But the upcoming Scroll Office 3.0 will. So, stay tuned.

When writing process documentation or project documentation it is a common use case to reference additional information such as presentations, very large diagrams or other native documents. So far this information was referenced by a hyperlink in the exported Word document pointing to your Confluence Wiki.

To share this information with the target audience of your exported Word documentation we introduce a new feature in Scroll Office Enhanced Word Exporter 2.4.

Now, the UI offers a new option called Export Attachments. Enabling this option a ZIP file is generated. This ZIP file contains both the exported document as well as the referenced attachments.

All attachments are referenced by relativ hyperlinks in the Word document and opened on click.

For more information please refer to the official release notes or just give it a try.

Scroll Wiki Enhanced PDF Exporter is the 3rd plugin we release for Confluence 4. This release mainly focuses on Confluence 4 compatibility, but also fixes some issues with IE browser compatibility. We are looking forward to introduce new features in the next versions.

For more information please refer to the official release notes.

The final releases of our other exporter plugins will be available in the next few days.

Scroll Office is the 2nd plugin we release for Confluence 4. The release of Scroll Office 2.3 mainly focuses on Confluence 4 compatibility, but we are looking forward to introduce new features in the next versions.

For more information please refer to the official release notes.

The final releases of our other exporter plugins will be available in the next few days.

The good news first: Confluence 4-compatibility will be coming soon.

We already have completed the migration of Scroll Office and Scroll Wiki Exporters to Confluence 4 successfully, and are currently ironing out the remaining bugs. We expect the final release to be available in the next few weeks.

In order to be updated about Confluence 4 compatibility of the plugins, please go to our forums and subscribe to the forum for the plugin you are interested in. You will then get automatically get an email, when a Confluence 4-compatible version of the plugin has been released.

Scroll Office 2.2: Table Styles and new Pricing Model

The new Scroll Office 2.2 is almost our of the door: It will finally be possible to use table style and define the design of tables such as background-colors, borders and more. This has been one of the most wanted feature on our forums and we are proud to have an implementation, which will cover all use-case.

Starting from Version 2.2 we will introduce a new pricing model: The prices for Scroll Office will now start at $240 for 25 Users and will go up to $3600 for unlimited users (that is roughly 30% of the license cost of the matching Confluence license). Also, we will office 10-user starter licenses. The change in the license model is, that Scroll Office licenses will now be bound to the Confluence license. We have done this to better align with Atlassian's licensing scheme, and also we had technical issues with named users on Confluence systems using Crowd for authentication.

Scroll Wiki Exporters

Our initial product Scroll Wiki Exporter will be split up into multiple plugins - each for every export format. We do this in order to allow our users to select the functionality they actually need.

In the first step we will offer the following plugins

• Scroll Wiki PDF Exporter
• Scroll Wiki EPUB Exporter (Codegeist Winner)
• Scroll Wiki EclipseHelp Exporter
• Scroll Wiki HTML Exporter

We will introduce the individual plugins with all their features separately in the coming weeks/months. They all have in common a completely redesigned user interface.

All Scroll Wiki Exporters will be available from $240 for 25 users up to $3600 for unlimited users (which is more or less 30% of the cost of the matching Confluence license).

Scroll Wiki Forms for Confluence 4

The Scroll Wiki Forms are a new extension based on the new Confluence 4 editor for defining forms on pages. The intention of Scroll Wiki Forms is to keep the content on a page structured.

Confluence 4 will be released in the next 2-3 months. Soon after that we will release Scroll Wiki Forms.

Zen-Editor for Confluence 4

The Zen-Editor is an extension the new Rich-Text-Editor of Confluence 4. Built as a so-called Speakeasy extension, it hides all UI-components from the UI, except the editing area and by that lets the author really focus on what he/she is writing.

Zen-Editor requires Confluence 4 and the Speakeasy extension, which both will be available later this year.

The Scroll Wiki EPUB Exporter leverages the Scroll Wiki infrastructure to export single pages or complete pages trees to the EPUB format and download it to your iPad, iPhone or any other EPUB capable format.

The Scroll Wiki EPUB Exporter is currently in beta and will be generally available later this year. If you want to try it out yourself now:

Download the beta version from the Atlassian Plugin Exchange
Email sales@k15t.com to get a free 30-day trial license.