Categories allow to set document instance of different doctypes in a hierarchy.

ID
category
Suite
Core
Documentation Type
Q1 - Process
Categories
/ Organisation / Generic
Tags
Title Encoding
/

Categories allow to set document instance of different doctypes in a hierarchy.

Properties

The document type category provides the following properties:

Short Name

The name of the category includes the path to the root category which makes the names of categories quite unwieldy. Therefore the short name is just the last part of the category path.

CSS Style Information

Add the CSS to use with this document type when rendered as an element within the Name List Macro.

Sections

Description

Documents the semantics of the category.

Subordinate Categories

Categories are hierarchic. This is reflected by the name of categories, which include the path to the category root.

Documents

List of documents that are associated with this category.

Per default only documents within the same space are listed. If you want to reference

Notes

These are internal notes that are usually not exported and only visible to team members with write access.

But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.

References

For a document the references section contains pointers to resources that prove the statements of the document.

Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.

Resources

The resources section provides references to further information to the topic of the document.

This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.

Details

Title Encoding

Spaces are limited such that there can only be one page with a given title. Categories typically define an alternate view on a topic. There may be other documents with the same title, but of different document types. Therefore Categories prepend a slash ('/') separated by a space in front of the name. Therefore category names look like paths in a tree (or taxonomy if you like).

You may check the box on the wizard to create a new category to care for this conventional encoding.

Available since version 1.10.

Related Doctypes

Tags

Tags are also a means to add structure to documents. Other than with categories, tags are not (required to be) hierarchic. Therefore tag names have to be unique, even if they do not have the same ancestor path, categories do only have to be unique within their ancestor path.

Type-specific Types

Besides generic types projectdoc also provides types that are associated with specific doctypes only.

Name Short Description Set Target Types
Association Type
Categorize associations by a type.
Core
Association
Category Type
Categorize categories by a type.
Core
Category
Charter Type
Categorize charters by a type.
Core
Charter
Excerpt Type
Categorize excerpts by a type.
Core
Excerpt
Experience Level
Defines the context through which readers acquire skills. The level sets the expectation on the author's techniques to teach.
Core
Topic
Experience Level Type
Categorize experience levels by a type.
Core
Experience Level
FAQ Type
Categorize FAQs by a type.
Core
FAQ
Generic Type
Categorize generic documents by a type.
Core
Generic
Glossary Item Type
Categorize glossary items by a type.
Core
Glossary Item
Media Type
Resources are identified by their media type. This may be the MIME type, but also a human readable string, that identifies the syntactic format.
Core
Resource
Media Type Type
Categorize media types by their type.
Core
Media Type
Metadata Type
Categorize metadata documents by a type.
Core
Metadata
Module Type
Categorization of document modules for single sourcing.
Core
Module
Organization Type
Categorize organizations by a type.
Core
Organization
Person Type
Categorize persons by a type.
Core
Person
Profile Type
Categorize profiles by a type.
Core
Profile
Quote Type
Categorize quotes by a type.
Core
Quote
Relation
Organizes glossary items.
Core
Glossary Item
Relation Type
Categorize relations by a type.
Core
Relation
Resource Type
Resources are identified by their type. This is not the MIME type, but human readable string, that identifies the semantic, rather than the syntactic format.
Core
Resource
Role Type
Categorize roles by a type.
Core
Role
Section Type
Categorize sections by a type.
Core
Section
Space Index Type
Categorize space indexes by a type.
Core
Space Index
Stakeholder Type
Categorize stakeholders by a type.
Core
Stakeholder
Step Type
Categorize steps by a type.
Core
Step
Subject Type
Categorize subjects by a type.
Core
Subject
Tag Type
Categorize tags by a type.
Core
Tag
Topic Type
A topic type is a semantic type of the topic. It helps to set the expectations of potential readers.
Core
Topic
Version Type
Categorize versions by a type.
Core
Version

Resources

  • Employ the Autolist Feature with Categories - Categories, tags, and others allow to organize the pages in your wiki. First define categories pages with display table macros. Second tag your pages with these categories. With this two-step process it is easy to have multiple views to link to your information in your wiki.
  • Finding without Searching - applied! - A blog article on organizing Confluence spaces with the projectdoc Toolbox.