projectdoc-quote-external |
---|
render-anonymous | false |
---|
source | projectdoc teaser |
---|
|
Lost in wiki space? Blank-Wikipage-Syndrome? Where to add? How to find? No fun anymore?
|
Image AddedOur claim is that projectdoc enhances your documentation experience as a team. projectdoc is based on projectdoc documents. Every projectdoc document defines A projectdoc document is a Confluence page using document properties and sections. This is contrary to starting every page with the Confluence blank page.
If you consider to use projectdoc to enhance your documentation experience as a team - as is our tagline - you may ask:
, which seems fast and easy.
Section |
---|
Panel |
---|
Column |
---|
| You now may wonder – Panel |
---|
titleColor | white |
---|
titleBGColor | darkred |
---|
|
|
|
| Does this additional effort actually pay off? |
|
Column |
---|
| We say – Panel |
---|
titleColor | white |
---|
titleBGColor | #14892C |
---|
title | Our Answer |
---|
|
|
| |
Let's check our arguments ... (TL;DR)- and here are our arguments!
Section |
---|
|
Let's first have a look on what your investment is. Who has to do what at which time? Section |
---|
title | Who's work Work and when? |
---|
| The page author usually selects a page template with a blueprint wizard. So there is no need to add the properties or section macros manually. The template author adds the properties and sections at the time she defines designs a template. This is a one time effort and employing macros instead of simple text makes not much difference. If the page author adds a property, this is a new line in an existing table. Nothing to worry about. If the page author wants to add a new section, she may choose to not use the Section Macro. In this case the content cannot be transcluded. That's all. If the author wants to support transclusion, she has to select some macro anyway. So there is no difference in using projectdoc macros or macros provided by other vendors. So we think the additional effort on using projectdoc macros to define projectdoc documents is quite low. |
Section |
---|
title | Everybody's Darling? |
---|
| You have to invest into in learning projectdoc. If your authors like to invent a new document structure for each document they write and feel limited by the use of templates, then projectdoc might not make them very happy. projectdoc leaves room to adjust documents to present the information. It does not demand to follow a defined template. To the contrary, the template is a best practice to write documents of a given kind. So adding new properties and sections and not adding specifying ever property and filling out every section is fine. Actually it is the responsibility of the author to decide which information makes sense. But if an information is required to meet the reader's expectation, the template defines where she expects it to be found. So if you think templates make the task of documenting for collaborating teams easier – and you won't be alone with this assumption – projectdoc is for you! |
|
Section |
---|
title | Payoff - the FeaturesThe Impact on your Work |
---|
|
Once you build your documentation with projectdoc documents, you can rely on the following features. Transclusion |
---|
taget-heading-level | 2 |
---|
document | PDAC1:projectdoc Document |
---|
ids | Select Documents |
---|
| |
The impact of this feature on your work is better navigation, since links that refer to related information are collected and displayed easily. New pages that match the constraints will be added automatically without having to edit the referring page. This increases maintainability! Transclusion |
---|
taget-heading-level | 2 |
---|
document | PDAC1:projectdoc Document |
---|
ids | Transclude Sections and Properties |
---|
| |
The feature impacts on easier collaboration. Smaller documents are more easily written and maintained independently. This supports teams to create documentation collaboratively. In addition to that information fragments may be transcluded at multiple locations, which again supports maintainability since changes are applied at one location. |
Section |
---|
|
We showed that the The investment in time to define properties and sections to create projectdoc documents is rather small and the benefits are automatic lists and the ability to support modular documentation using transclusion. Furthermore most of the time effort is spent once at design time by the template author. The investment in time to learn projectdoc, especially the to learn about macros involved to render automatic lists and to use transclusion, is probably much larger. Fortunately this is also a one-time investment. What you gain: - Automatic lists of matching documents
- making navigation and maintenance much easier - Support for modular documentation based on transclusion
- making collaboration and reuse much easier
We think the reward is larger than the investment. Do you agree? |
Section |
---|
|
For more information on projectdoc, please visit Tour |
---|
render-as-definition-list | true |
---|
replace-title-with-name | true |
---|
| |
|