Today we released version 1.17 of the projectdoc Toolbox for Confluence!
projectdoc supports agile teams creating and maintaining project documentation. It provides templates and tools to improve the collaboration of team members.
This release provides
- Templates for a Display List
- Templates for the Tour Macro
- and 26 smaller features, enhancements and bugfixes
For detailed information on changes, please refer to the release notes.
Especially note that all doctype add-ons and the Web API and Bookmarklets Extension needs to be updated.
projectdoc Toolbox
If you want to learn more about the projectdoc Toolbox and how it helps to create good project documentation, please refer to the introduction video!
The following image is a link to a video on YouTube. When you click the link your browser will serve a page from youtube.com.
Very interesting, but way too fast?
Step through at your own pace with with our Prezi Presentation (external link to prezi.com)!
In the Online Manual you’ll find additional video material that introduces you in the concepts of the projectdoc Toolbox.
Refer to use cases and show cases for information on how to use the projectdoc Toolbox.
Today we released the first beta of the History Manager for Confluence.
Our requirements are that we do not want to have these long list of page and attachment version histories. We need a tool to remove this information from spaces and whole Confluence instances.
We found some add-ons that can be used to remove this information per page, but we needed to address whole spaces.
The add-on is intended to be used by users of the projectdoc Toolbox along with the Web API Extension.
Private Release
The beta release is currently not available on the Atlassian Marketplace.
We want to give us some time to settle with the API before we make a public release.
If you are interested in using this add-on for Confluence server instances, please get in touch!
Today we talk about principles and practices to support team collaboration in Confluence at the Munich Atlassian User Group.
This talk introduces three principles of software development adapted to the topic of agile documentation.
Each principle is explained by a documentation practice.
- Dynamic Links
- Frequency of Change (Document vs. Record)
- Keep a Journal
- No Noise
An example shows the practice in action on Confluence.
The slides for the talk are available for download. The organizers of the Atlassian User Group also uploaded the video of the talk.
Add-ons for Confluence
Have a look at the projectdoc Toolbox for Confluence or the free Project Documentation Macros for tools that support these principles and practices!
We are happy to announce our new space on agile documentation!
Within this space we provided information about values of good documentation. We list principles that support theses values and practices that make those principles actionable. The practices are shown in pattern form and therefore include both, advantages and disadvantages that come with the application of the practice.
The values for readers are described in the book Developing Quality Technical Information by Gretchen Hargis, Michelle Carey, Ann Kilty Hernandez, Polly Hughes, Deirdre Longo, Shannon Rouiller, and Elizabeth Wilde.
Most of the principles we list are well known by software developers and people with an agile mindset. Some principles are used by technical writers.
We also link to tools, especially macros and doctypes (aka blueprints), from our projectdoc Toolbox for Confluence that support a given practice. This may give users of this add-on an alternative approach to learn how to use these tools.. But the information on values and principles, and most patterns is not tool-specific and therefore may be used with any tools.
If you have comments or suggestions, please let us know!
