In Confluence you can like pages, content and blogposts, but what if you don’t like them and want to report something? Consider the following situations, we’re pretty sure you can relate.
A new version of JSD was released yesterday and it’s clear it is gaining in maturity with every release. Here are some highlights of the new version 2.2.
Read on to find out how combining JIRA Service Desk and Confluence Team Calendars makes requesting time off easier than ever…
Collaboration, sharing, discussions, documents, knowledge, wiki, intranet. These are some of the keywords people use when talking about Confluence. Confluence started out as a wiki-like system but it goes a lot further than that these days. We’ve seen it (or installed it ourselves) in many different forms, like (social) intranets, public websites, knowledge bases or just a place to store documents. With Confluence it is easy to create content, to share it, to find it and to breathe life into it. Besides that, it’s easy to customize or extend Confluence and it’s openness allows you to do just about anything you like with it.
Here it is, the blog post I promised about the coolest new add-ons released during Atlassian Summit 2013. To be clear, these are the add-ons I personally found most interesting and also had time to look into.
They are either entirely new add-ons or they offer significant new features for the existing ones.
Today was the big day for Atlassian Summit 2013 with the opening keynote where all the big announcements were made. Co-founders and co-ceo’s Scott Farquhar and Mike Cannon-Brookes traditionally open the summit and this year they had yet again cool stuff to announce. Here is a brief overview of the all new things announced. More in-depth analysis of all the new stuff is coming over the next couple of days.
It has only been 1,5 months and Atlassian already released their next major version of Confluence. Confluence 5.1 is centered around page templates, which are known as ‘blueprints’ inside the application.
In previous versions of Confluence there were two types of content; pages and blogposts. When you created a new page or blogpost you started out with a blank page. With blueprints you don’t start with a blank page anymore. Instead you pick a type of page you want to create and you get a template for you page for free! Some blueprints even have a wizard where you have to fill in some information which will be used in the blueprint itself. You can of course still start with a blank page if you want.
In software development, it’s pretty normal to stage your deliverables from your Development environment to Test to Acceptation en finally to Production (DTAP). On it’s way to production your software meets different data sets, hopefully improving in quality and relevancy. Continue reading
About this post: This guest blog was written by Brigitte Meijer, Information Analyst & Requirements Engineer at BmIT. She is a valued collaborator of ours who we regularly hire for consultancy. We have asked her to share her views on our recently released plugin, the XSD Viewer for Confluence. This is what she wrote:
We are currently developing webservices and an ebMS interface for a customer. This involves making a lot of XSD’s…
Previously we wrote the functional and technical documentation for these interfaces in MS Word, made tables explaining the elements by hand and used a development tool to create schematic images. This was a lot of work and it was very difficult to keep the XSD and the documentation in sync.