- Created by Robert Reiner, last modified on 11. Mar 2020
A document type (doctype) defines the properties and section for document instances. It also provides home and index pages. In Confluence these doctypes are implemented as page blueprints, usually with one template. This template is used to create new pages in Confluence.
- Short Name
- Doctype
- Relation
When information needs to be written down immediately two questions arise.
- Where do I put this new document?
- How do I structure the information in this document?
Authors should not need to think hard to answer these two questions. They should focus on the content, the information that needs to be published and be made available to stakeholders.
Naturally the structure of a document also supports to deliver the information. Therefore authors are allowed to change the structure to fit their needs.
The goal of document types is to provide a structure that fits most use cases and which may be good enough for the communication with stakeholders.
A document type (doctype) defines the properties and section for document instances. It also provides homepages and index pages. In Confluence these doctypes are implemented as page blueprints, usually with one single template. This template is used to create new pages in Confluence.
Specializations
- Entity Document Type
- Instances of this type provide information on an entity of the domain.
- Organizing Document Type
- Instances of this type organize documents by providing metadata.
Resources
- Document Types and Templates
- Document types (or doctypes for short) define a set of properties and sections. Each doctype matches at least one Confluence Page Blueprint. Confluence Page Blueprints are a collection of templates, but often the collection contains only one element.
- Doctypes
- Doctypes define properties and sections for documents. They are essentially Confluence Blueprints that help to create pages in your wiki based on templates.
- Document Instance
- A projectdoc document instance is based on a document type. Documents are created using page wizards provided by blueprints.
- Doctypes Overview
- List of all doctypes provided by add-ons. Provides an overview over doctype IDs and blueprint keys.
The projectdoc Toolbox provides a number of document types as separate doctype add-ons.
Some of the blueprints listed here are not yet publicly available. Please check the doctype add-ons for actual availability!
| # | Name | Short Description | Suite |
|---|---|---|---|
| 1 | Access Information | Credentials for development systems where the password is known to all who have access to the Confluence wiki. | Service Management |
| 2 | Access Information Type | Type-specific category for access information. | |
| 3 | Alternative | This documents a possible option for a decision. Choose this document type to describe the alternative for a decision in more detail. This is typically a subpage of a decision document. | Project Management |
| 4 | Alternative Type | Group your alternatives by a self-defined type. | Project Management |
| 5 | Announcement | Announcements are a way to communicate an important piece of information with your team. | Agile Team |
| 6 | Annual Vision | Describe your vision for one year. You plan will help you stay focussed to accomplish your goals. | Developer Diaries |
| 7 | Annual Vision Type | Categories for annual visions. | Developer Diaries |
| 8 | App | Document your app for your users and customers. | App |
| 9 | App Component | Provide more detailed information about a component of a tool. | App |
| 10 | App Component Type | Document the purpose and usage of the components of this type. | App |
| 11 | App Extension | Document your extension for your users and customers. | App |
| 12 | App Extension Type | Document the purpose and usage of the extension of this type. | App |
| 13 | App Macro | Document the purpose and usage of the macro. | App |
| 14 | App Macro Type | Document the purpose and usage of the macros of this type. | App |
| 15 | App Parameter | A parameter is a configuration option. Parameter exist on different layers. Wizard and macro parameters are configuration options. Use | App |
| 16 | App Parameter Type | Document the purpose and usage of the app parameters of this type. | App |
| 17 | App Platform | Document a platform for apps. | App |
| 18 | App Platform Type | Document the purpose and usage of the platforms of this type. | App |
| 19 | App Service | Document a service provided by an app. | App |
| 20 | App Service Type | Document the purpose and usage of the app services of this type. | App |
| 21 | App Tool | Document a tool provided by an app. | App |
| 22 | App Tool Type | Document the purpose and usage of the app tools of this type. | App |
| 23 | App Type | Document the purpose and usage of the apps of this type. | App |
| 24 | Application | Applications provided functions required by services. Applications may be hosted on one or more systems. | Service Management |
| 25 | Application Type | Type-specific category for applications. | |
| 26 | arc42 Template | The blueprint of the arc42 Template creates a tree of pages in the Confluence space. | arc42 |
| 27 | Architecture Alternative | Document a possible option for an architecture decision. Choose this document type to describe the alternative for a decision in more detail. This is typically a subpage of an architecture decision document. | Software Development |
| 28 | Architecture Alternative Type | Group architecture alternatives by their type. | Software Development |
| 29 | Architecture Aspect | Document an aspect of your architecture. Something orthogonal or cross-functional like logging, exception handling or configurability. | Software Development |
| 30 | Architecture Aspect Type | Group architecture aspects by their type. | Software Development |
| 31 | Architecture Constraints | The second chapter of the arc42 Template with information on constraints and conventions. | arc42 |
| 32 | Architecture Decision | Document a architecture decision for an option. This is useful to state the reasons and the options that have been evaluated. Later other team members will have it easier to understand the decision. | Software Development |
| 33 | Architecture Decision Type | Architecture decisions are group by their types. A commonly used decision type is 'Architecture'. | Software Development |
| 34 | Artifact | Document requirements you impose on artifacts. Artifacts are created by processes defined and used by the team. This includes assemblies created by the build process, source code artifacts or reports. | Software Development |
| 35 | Artifact Type | Artifact types categorize artifacts. | Software Development |
| 36 | Asset | Explain an asset of your work. Add this document to a day in your diary. | Developer Diaries |
| 37 | Asset Type | Categories for assets. | Developer Diaries |
| 38 | Association | Associates two documents. | Core |
| 39 | Association Type | Categorize associations by a type. | Core |
| 40 | Assumption | Document assumptions to assess risks and opportunities for the project. | Risk Management |
| 41 | Assumption | Assumptions document what you think about your product, customers, and partners. Once you start identifying assumptions, it will become clearer what other beliefs you hold about how you plan to build, design, distribute, and create value with your product. Making assumptions explicit allows to publish them and discuss them with other stakeholders. | Lean |
| 42 | Assumption Resolution | Assumptions can be resolved in different ways. Define what each resolution implies. | Lean |
| 43 | Assumption Resolution Type | Type-specific category for assumption resolutions. | Lean |
| 44 | Assumption Type | Assumptions are grouped by their type. | Risk Management |
| 45 | Assumption Type | Type-specific category for assumptions. | Lean |
| 46 | Blackbox | Describe as a Blackbox the elements of a view where only the externally visible properties are relevant. | Software Development |
| 47 | Blackbox Type | Group blackboxes by their type. | Software Development |
| 48 | Blank Document | The blank template simply provides a minimal integration with projectdoc features. It is a quick starting point to use projectdoc. | Native |
| 49 | Bookmarklet Editor | The bookmarklets editor is a simple page that allows teams to create their bookmarklets more easily. It also provides access to some standard bookmarklets provided for the projectdoc Toolbox. | Bookmarklets Extension |
| 50 | Building Block View | The fifth chapter of the arc42 Template with information on the local building blocks, and their dependencies and relationships. | arc42 |
| 51 | Category | Categories allow to set document instance of different doctypes in a hierarchy. | Core |
| 52 | Category Type | Categorize categories by a type. | Core |
| 53 | Change | Document a single change to configuration items or assets. | Service Management |
| 54 | Change Severity | Add an severity to classify changes. | Service Management |
| 55 | Change Status | Add a status to categorize changes. | Service Management |
| 56 | Change Theme | Add a theme to group changes. | Service Management |
| 57 | Change Type | Type-specific category for changes. | Service Management |
| 58 | Charter | Describes an information need and use this description as a basis to create and maintain a document. | Core |
| 59 | Charter Type | Categorize charters by a type. | Core |
| 60 | Cheat | A brief solution to a problem. | Developer Diaries |
| 61 | Cheat Type | Categories for cheats. | Developer Diaries |
| 62 | Check-in | Document the result of a OKR check-in. | Objectives and Key Results |
| 63 | Check-in Type | Type-specific category for OKR check-ins. | Objectives and Key Results |
| 64 | Checklist | Checklists allow to run manual tasks in a defined manner. It guides the user of the checklist through a process and helping to not forget a step. | Teamwork |
| 65 | Checklist Type | Categorize checklists by type. | Teamwork |
| 66 | Code | Describe the codes that are part of the product's API. | Software Development |
| 67 | Code Type | Code types categorize codes, used in logging or exception handling. | Software Development |
| 68 | Component | Components are part of a view on a system. A component may refer to a enclosed element or to a complete system of its own. | Software Development |
| 69 | Component Type | Component types categorize components. | Software Development |
| 70 | Configuration Item | Configuration items (CIs) may be (sub-)systems or components. Whatever may change and needs to be tracked may be documented as a CI. | Service Management |
| 71 | Configuration Item Status | Signals the status of an IT system, application, or a configuration item. | Service Management |
| 72 | Configuration Item Type | Type-specific category for configuration items. | Service Management |
| 73 | Cross-cutting Concepts | The eighth chapter of the arc42 Template with conceptional information about the system. | arc42 |
| 74 | Cycle | Add cycles to group cycle phases. | Core |
| 75 | Cycle Phase | Cycle phases define phases that are bound to a cycle, such as lifecycles or iterations. | Core |
| 76 | Data Type | Document a data type for properties and codes. | Software Development |
| 77 | Data Type Type | Data type types categorize data types. | Software Development |
| 78 | Dataset | Datasets are used as the input and output of processes. | Service Management |
| 79 | Dataset Type | Type-specific category for datasets. | Service Management |
| 80 | Day | Store relevant information discovered today in your developer diary. | Developer Diaries |
| 81 | Day Type | Categories for days. | Developer Diaries |
| 82 | Decision | Document a decision for an option. This is useful to state the reasons and the options that have been evaluated. Later other team members will have it easier to understand the decision. | Project Management |
| 83 | Decision Type | Group your decisions by a self-defined type. | Project Management |
| 84 | Deployment | Deployments provide information about updates on services and systems to users. | Service Management |
| 85 | Deployment Record | Record a deployment to a IT system. | Service Management |
| 86 | Deployment Record Type | Type-specific category for deployment records. | Service Management |
| 87 | Deployment Type | Type-specific category for deployments. | Service Management |
| 88 | Deployment View | The seventh chapter of the arc42 Template with information about how the system is deployed. | arc42 |
| 89 | Design Decisions | The ninth chapter of the arc42 Template that explains the architecture decisions that led to the system. | arc42 |
| 90 | Diary | The homepage of a developer's daily diary pages. Consider to add your diary to your personal space! | Developer Diaries |
| 91 | Diary Type | Categories for diaries. | Developer Diaries |
| 92 | Doctype | Document the usage of a doctype for your users. | App |
| 93 | Doctype Type | Document the purpose and usage of the doctypes of this type. | App |
| 94 | Document Property | Document the usage of a document property for your users. | App |
| 95 | Document Property Type | Document the purpose and usage of the properties of this type. | App |
| 96 | Document Section | Document the usage of a document section for your users. | App |
| 97 | Document Section | Document the purpose and usage of the sections of this type. | App |
| 98 | Environment | Document logical or physical groups of nodes. | Software Development |
| 99 | Environment Type | Type of an environment used by the project to deploy the application or the solution. | Software Development |
| 100 | Event | Associated an event with a day. A event is a collection of associated information for your later reference. Information may further be organized by subject, tags, categories, and audience. | Developer Diaries |
| 101 | Event Type | Categories for events. | Developer Diaries |
| 102 | Excerpt | Excerpts are abstracts of information found in a resource, such as a book. If you want to go into more detail for a given resource, there may be multiple excerpts as subpages of the resource document. | Core |
| 103 | Excerpt Type | Categorize excerpts by a type. | Core |
| 104 | Experience Level | Defines the context through which readers acquire skills. The level sets the expectation on the author's techniques to teach. | Core |
| 105 | Experience Level Type | Categorize experience levels by a type. | Core |
| 106 | FAQ | FAQs help to record an answer to a frequently asked question concerning the project, the product, the system or the process. | Core |
| 107 | FAQ Type | Categorize FAQs by a type. | Core |
| 108 | Feature | Documents a feature of the product. The top features define the main aspects of the product. | Software Development |
| 109 | Feature Type | Feature types categorize features. | Software Development |
| 110 | Generic | Generic Documents provide information where no other doctype matches. | Core |
| 111 | Generic Type | Categorize generic documents by a type. | Core |
| 112 | Glossary | The last chapter of the arc42 Template lists terms of the domain and explains them. | arc42 |
| 113 | Glossary Item | Glossary items are part of the domain glossary for the project. Glossaries support the team to use terms of the domain consistently in conversations and documentation. | Core |
| 114 | Glossary Item Type | Categorize glossary items by a type. | Core |
| 115 | How | Describe how the impact will be pursued. | Impact Mapping |
| 116 | How Type | Type-specific category for hows. | Impact Mapping |
| 117 | Hypothesis | Write your problem hypothesis. This is the hypothesis that you will either validate or (probably) come back and revise. | Lean |
| 118 | Hypothesis Status | Type-specific category for hypotheses based on status. | Lean |
| 119 | Hypothesis Status Type | Type-specific category for hypothesis status. | Lean |
| 120 | Hypothesis Type | Type-specific category for hypotheses. | Lean |
| 121 | Impact | Publish an impact you want to achieve. Share this information with your colleagues. | Lean |
| 122 | Impact Map | Publish impacts you want to achieve. Share this information with your colleagues. | Impact Mapping |
| 123 | Impact Map Type | Type-specific category for impact maps. | Impact Mapping |
| 124 | Impact Type | Type-specific category for impacts. | Lean |
| 125 | Improvement | Improvement proposals help to start the conversation within the team for process improvements. | Agile Team |
| 126 | Interface | Interfaces document how elements of the system communicate with elements of this and other systems. | Software Development |
| 127 | Interface Type | Group interfaces by their type. | Software Development |
| 128 | Introduction and Goals | The first chapter of the arc42 Template with information on requirements, quality goals, and stakeholders. | arc42 |
| 129 | IT Activity | IT Activities define activities for processes. | Service Management |
| 130 | IT Activity Type | Type-specific category for IT activities. | Service Management |
| 131 | IT Asset | IT Assets define assets required or produced by processes. | Service Management |
| 132 | IT Asset Type | Type-specific category for IT assets. | Service Management |
| 133 | IT Function | Functions are specialized organizational units to support business processes. | Service Management |
| 134 | IT Function Type | Type-specific category for IT functions. | Service Management |
| 135 | IT Procedure | IT Procedures define procedures for processes. | Service Management |
| 136 | IT Procedure Type | Type-specific category for IT procedures. | Service Management |
| 137 | IT Process | Processes organize activities to create a defined business value. | Service Management |
| 138 | IT Process Type | Type-specific category for IT processes. | Service Management |
| 139 | IT Service | IT Services provide business relevant services for customers. | Service Management |
| 140 | IT Service Classification | Classifiers to categorize services. | Service Management |
| 141 | IT Service Classification Type | Type-specific classification for IT services. | Service Management |
| 142 | IT Service Status | Signals the status of an IT Service. | Service Management |
| 143 | IT Service Type | Type-specific category for IT services. | Service Management |
| 144 | IT System | Systems are part of environments where products are deployed to. | Service Management |
| 145 | IT System Type | Systems are categorized by their type. These types may be quite concrete since systems by nature reference a hard- or software system usually by their IP address or DNS name. Therefore a system type may be 'Artifact Repository' or 'Virtual Server. And types may build hierarchies. | Service Management |
| 146 | Iteration | Document an Iteration that may be linked from JIRA. Allows the team to set the goal and add notes relevant to a particular iteration. | Agile Team |
| 147 | Key Result | Publish key results to achieve in order to pursue an objective to share with your colleagues. | Objectives and Key Results |
| 148 | Key Result Type | Type-specific category for key results. | Objectives and Key Results |
| 149 | Lifecycle | Add lifecycles to group lifecycle phases. | Service Management |
| 150 | Lifecycle Phase | Lifecycle phases define phases that are bound to a lifecycle. | Service Management |
| 151 | Location | Locations provide information about the whereabouts of assets, configuration items, and systems. | Service Management |
| 152 | Location Type | Type-specific category for locations. | Service Management |
| 153 | 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 |
| 154 | Media Type Type | Categorize media types by their type. | Core |
| 155 | Metadata | Metadata documents provide tables of simple key/value pairs. This information can be used as an aspect or as additional space properties to be available for reference on your wiki. | Core |
| 156 | Metadata Type | Categorize metadata documents by a type. | Core |
| 157 | Minutes | Record the action items of a meeting. | Project Management |
| 158 | Minutes Type | Group your minutes by a self-defined type. | Project Management |
| 159 | Mission Statement | Define a mission for your company or product. | Business Strategy |
| 160 | Mission Statement Type | Type-specific category for mission statements. | Business Strategy |
| 161 | Module | A documentation module is a fragment which is usually transcluded by other documents. The lifetime of a module document is independent of the lifetimes of the documents that reference it. | Core |
| 162 | Module Type | Categorization of document modules for single sourcing. | Core |
| 163 | Month | Plan and run a retrospective for your month of work. | Developer Diaries |
| 164 | Month Type | Categories for months. | Developer Diaries |
| 165 | Node | Nodes are part of environments where artifacts are deployed to. | Software Development |
| 166 | Node Type | Node types categorize nodes. | Software Development |
| 167 | Objective | Publish an objective to share with your colleagues. | Objectives and Key Results |
| 168 | Objective Type | Type-specific category for objectives. | Objectives and Key Results |
| 169 | OKR Priority | Category to organize strategic themes, objectives, and key results. | Objectives and Key Results |
| 170 | Open Issue | Open issues document what the team needs to know to proceed. | Project Management |
| 171 | Open Issue Severity | Open issues are grouped by the severity of their impact on the project. | Project Management |
| 172 | Open Issue Status | Open issues are grouped by the status. | Project Management |
| 173 | Open Issue Type | Group your open issues by a self-defined type. | Project Management |
| 174 | Opportunity | Document and track identified opportunities for the project. | Risk Management |
| 175 | Opportunity Type | Opportunities are grouped by their type. | Risk Management |
| 176 | Organization | Information about organizations that take a part in the project. You may collect common information here for all persons that belong to an organization, such as address or homepage. | Core |
| 177 | Organization Type | Categorize organizations by a type. | Core |
| 178 | Out Item | Out Items record topics that are out of the scope of the project. This is useful for project inception and for reference in the future. | Software Development |
| 179 | Out Item Type | Out item types categorize out items. | Software Development |
| 180 | Outcome | Products used by customers intend to make a change. This change is called outcome. | Lean |
| 181 | Outcome Type | Type-specific category for outcomes. | Lean |
| 182 | Output | The output is the artifact created to be employed by user for a specific outcome and - on the long run - may make an impact. | Lean |
| 183 | Output Type | Type-specific category for outputs. | Lean |
| 184 | Page Blueprint | Document the purpose and usage of a page blueprint. | App |
| 185 | Page Blueprint Type | Document the purpose and usage of the page blueprints of this type. | App |
| 186 | Pattern | Patterns provide solutions for problems in a given context. Patterns are usefull in multiple areas such as design, architecture, documentation, or process. | Teamwork |
| 187 | Pattern Domain | Patterns are divided into different domains to group patterns. | Teamwork |
| 188 | Pattern Type | Categorize patterns by type. | Teamwork |
| 189 | Person | Provides information about a person. This includes contact information (important if the person is relevant for the team) or information about the competences (if the person is an author about a topic relevant for the project). | Core |
| 190 | Person Type | Categorize persons by a type. | Core |
| 191 | Problem | Document problems as a means to communicate the details and to use the information for reviews and retrospections. | Risk Management |
| 192 | Problem Type | Problems are grouped by their type. | Risk Management |
| 193 | Process Impact | Impacts define how the results of processes affect the world. | Service Management |
| 194 | Process Impact Type | Type-specific category for impacts. | Service Management |
| 195 | Process Outcome | Outcomes define the results of processes. | Service Management |
| 196 | Process Outcome Type | Type-specific category for outcomes. | Service Management |
| 197 | Product Backlog | Product Backlogs are means to collect user stories. | Agile Team |
| 198 | Profile | Profiles provide views on documents via delegation. | Core |
| 199 | Profile Type | Categorize profiles by a type. | Core |
| 200 | Project Constraint | Project Constraints limit the options of a project. | Software Development |
| 201 | Project Constraint Type | Project constraint types categorize project constraints. | Software Development |
| 202 | Project Rule | Project Rules are defined by the team to enhance the collaboration and to define project standards. | Teamwork |
| 203 | Project Rule Type | Categorize project rules by type. | Teamwork |
| 204 | Project Vision | Frame the vision for a project or iteration. | Software Development |
| 205 | Project Vision Type | Types to categorize vision statements for projects. | Software Development |
| 206 | Property | Properties are part of the configuration options of a system. | Software Development |
| 207 | Property Type | Property types categorize properties of products, such as parameters or configuration options. | Software Development |
| 208 | Quality | Qualities describe desired aspects of the product. | Software Development |
| 209 | Quality Requirements | The tenth chapter of the arc42 Template that lists scenarios to systematically evaluate the architecture against the quality requirements. | arc42 |
| 210 | Quality Scenario | Quality Scenarios document required qualities. | Software Development |
| 211 | Quality Scenario Type | Quality scenario types categorize quality scenarios. | Software Development |
| 212 | Quality Target | Documents a quality target for a product. | Software Development |
| 213 | Quality Target Type | Group quality targets by their type. | Software Development |
| 214 | Quote | Quotes relevant for the project. Allows to store the content and metadata to the quote. | Core |
| 215 | Quote Type | Categorize quotes by a type. | Core |
| 216 | Relation | Organizes glossary items. | Core |
| 217 | Relation Type | Categorize relations by a type. | Core |
| 218 | Release | Releases document the changes that are applied to a published version of a service. | Service Management |
| 219 | Release Note | Document changes provided by a release of a product. | Project Management |
| 220 | Release Note Type | Group your release notes by a self-defined type. | Project Management |
| 221 | Release Type | Type-specific category for releases. | Service Management |
| 222 | Report | Reports document what the team has decided or done. This is a generic document. | Project Management |
| 223 | Report Type | Group your reports by a self-defined type. | Project Management |
| 224 | Requirement | Documents requirements of a product. | Software Development |
| 225 | Requirement Type | Categorization of requirements for a product. | Software Development |
| 226 | Resource | Resources are books, webpages, videocasts relevant for the project. Add important information to your project about resources that lie outside the control of your team. | Core |
| 227 | 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 |
| 228 | Retrospective | Record the discussion of the team about their last iteration. | Agile Team |
| 229 | Review | Plan and run your review meeting. | Agile Team |
| 230 | Review Act | A single act to show on the review. Use this only if you have a lot to show or you want to reference the review results later. Often a simple numerated list is sufficient. | Agile Team |
| 231 | Risk | Document and track identified risks for the project. | Risk Management |
| 232 | Risk Action | Document actions to prevent or reduce the negative impact on exceptions on a project. | Risk Management |
| 233 | Risk Action Type | Risk actions are grouped by their type. | Risk Management |
| 234 | Risk Phase | Risks are grouped by the phase of their impact on the project. | Risk Management |
| 235 | Risk Probability | Risks are grouped by the probability of having impact on the project. | Risk Management |
| 236 | Risk Severity | Risks are grouped by the severity of their impact on the project. | Risk Management |
| 237 | Risk Target | Document targets of risks. | Risk Management |
| 238 | Risk Target Type | Risk tagets are grouped by their type. | Risk Management |
| 239 | Risk Type | Risks are grouped by their type. | Risk Management |
| 240 | Risks and Technical Debts | The eleventh chapter of the arc42 Template lists risks and technical debt. | arc42 |
| 241 | Role | Defines a role with its responsibilities, tasks and requirements. Roles are incorporated by stakeholders who take interest in the project. The are also used to define the audience for documents. | Core |
| 242 | Role Type | Categorize roles by a type. | Core |
| 243 | Runtime View | The sixth chapter of the arc42 Template with runtime information about the architecture. | arc42 |
| 244 | Section | Sections of a document are typically part of a document. But the size of sections may vary. To support a team to write collaboratively on the documentation, a larger document may be subdivided into external section documents. | Core |
| 245 | Section Type | Categorize sections by a type. | Core |
| 246 | Service Announcement | Announcements communicate with stakeholders information about a service. | Service Management |
| 247 | Service Announcement Type | Type-specific category for service announcements. | Service Management |
| 248 | Service Level | Describe a service level for a service. | Service Management |
| 249 | Service Level Agreement | Provide information about a service level agreement (SLA). | Service Management |
| 250 | Service Level Agreement Type | Type-specific category for service level agreements. | Service Management |
| 251 | Service Level Requirement | Describe a requirement in terms of a service level. | Service Management |
| 252 | Service Level Requirement Type | Type-specific category for service level requirements. | Service Management |
| 253 | Service Level Type | Type-specific category for service levels. | Service Management |
| 254 | Solution Strategy | The fourth chapter of the arc42 Template explains the solution idea. | arc42 |
| 255 | Space Blueprint | Document the purpose and usage of a space blueprint. | App |
| 256 | Space Blueprint Type | Document the purpose and usage of the space blueprints of this type. | App |
| 257 | Space Index | Compile other documents, yet space indices are themselves projectdoc documents. So they can be tagged and grouped. | Core |
| 258 | Space Index Type | Categorize space indexes by a type. | Core |
| 259 | Space Property | Space properties hold metadata of a space. They may be inherited by delegate spaces. | App |
| 260 | Space Property Type | Document the purpose and usage of the space properties of this type. | App |
| 261 | Stakeholder | A party that takes interest in a project. The stakeholder is either a real person, an organization or group, or represents a class of individuals, groups or organizations. | Core |
| 262 | Stakeholder Type | Categorize stakeholders by a type. | Core |
| 263 | Step | Describes a single step of an activity. A step is a generic document that is associated with a document that describes a process. It may be a test log or a howto. | Core |
| 264 | Step Type | Categorize steps by a type. | Core |
| 265 | Strategic Theme | Publish a strategic theme to group objectives and to share them with your colleagues. | Objectives and Key Results |
| 266 | Strategic Theme Type | Type-specific category for strategic themes. | Objectives and Key Results |
| 267 | Strategy | Defines a strategy for an organization or product. | Business Strategy |
| 268 | Strategy Type | Type-specific category for strategies. | Business Strategy |
| 269 | Subject | Subject documents allow to set document instance of different doctypes in a common context. | Core |
| 270 | Subject Type | Categorize subjects by a type. | Core |
| 271 | SWOT | Work on strengths, weaknesses, opportunities, and threats. | Business Strategy |
| 272 | SWOT Type | Type-specific category for SWOTs. | Business Strategy |
| 273 | System Scope and Context | The third chapter of the arc42 Template with information on context and external interfaces. | arc42 |
| 274 | Tag | Document the semantics of a tag. May also be used to document Confluence labels. | Core |
| 275 | Tag Type | Categorize tags by a type. | Core |
| 276 | Team Process | Document processes defined and used by the team. | Teamwork |
| 277 | Team Process Type | Categorize team processes by type. | Teamwork |
| 278 | Technical Debt | Technical Debts track issues to be paid back. | Software Development |
| 279 | Technical Debt Type | Technical Debts are grouped by the area they address. | Software Development |
| 280 | Test Case | Document a test case of your project. | Software Development |
| 281 | Test Case Type | Test case types categorize test cases. | Software Development |
| 282 | Test Charter | Defines a charter to run an exploratory test session. | Software Development |
| 283 | Test Charter Type | Test charter types categorize test charters. | Software Development |
| 284 | Test Data | Document data used for test cases. | Software Development |
| 285 | Test Data Type | Test data types categorize test data. | Software Development |
| 286 | Test Report | Documents the results of a test session for the sponsoring stakeholders. | Software Development |
| 287 | Test Report Type | Test report types categorize test reports. | Software Development |
| 288 | Test Session | Defines a document to collect information during a test session. | Software Development |
| 289 | Test Session Type | Test session types categorize test sessions. | Software Development |
| 290 | Todo | Add a todo note to your developer diary. | Developer Diaries |
| 291 | Todo Type | Categories for todos. | Developer Diaries |
| 292 | Tool | Document tools used by the team. Add information about how to fetch, install and best practices using it. | Teamwork |
| 293 | Tool Type | Categorize tools by type. | Teamwork |
| 294 | Topic | A description of a given topic. A topic may describing or explaining a concept, a task to accomplish or a reference. There are a couple of topic types that set the expectations for the reader. Instances of the topic doctype usually have independent lifetimes from any referencing documents. | Core |
| 295 | Topic Type | A topic type is a semantic type of the topic. It helps to set the expectations of potential readers. | Core |
| 296 | Tour | Guided tours through existing information. This allows to aggregate topics for a given question or audience, thus providing a view on a topic. | Core |
| 297 | Trigger | Triggers define signals for activities and processes. | Service Management |
| 298 | Trigger Type | Type-specific category for triggers. | Service Management |
| 299 | Use Case | Defines a use case of the product. | Software Development |
| 300 | Use Case Type | Use case types categorize use cases. | Software Development |
| 301 | User Character | User Characters are the actors of user stories. They include personas and extreme characters. | Software Development |
| 302 | User Character Type | User character types categorize user characters. | Software Development |
| 303 | User Story | User Stories document a requirement of a stakeholder with a specific business goal. It also provides an acceptance test. It is a representation of a unit of work. | Agile Team |
| 304 | Version | Document a version of a product or service. | Core |
| 305 | Version Type | Categorize versions by a type. | Core |
| 306 | View | Different views on the product help to document the system and its architecture. Typical views are building block, runtime, or deployment. | Software Development |
| 307 | View Type | Groups the views at a system. | Software Development |
| 308 | Vision | Describe your vision for your career. | Developer Diaries |
| 309 | Vision Statement | Define the vision for your organization or product. | Business Strategy |
| 310 | Vision Statement Type | Type-specific category for vision statements. | Business Strategy |
| 311 | Vision Type | Categories for visions. | Developer Diaries |
| 312 | Week | Plan and run a retrospective for your week of work. | Developer Diaries |
| 313 | Week Type | Categories for weeks. | Developer Diaries |
| 314 | What | Describe the (high-level) deliverables (aka outcomes and outputs) required to achieve the impact. | Impact Mapping |
| 315 | What Type | Type-specific category for whats. | Impact Mapping |
| 316 | Whitebox | Describe as a Whitebox the elements of a view where only the relations of internal elements are relevant. | Software Development |
| 317 | Whitebox Type | Group whiteboxes by their type. | Software Development |
| 318 | Who | Describe who is involved in the impact. List the stakeholders that will support the impact. There may be stakeholders who will work against it. Also specify the stakeholders taking advantage or taking disadvantage even if they do not have power to influence the outcome. | Impact Mapping |
| 319 | Who Type | Type-specific category for whos. | Impact Mapping |
| 320 | Why | Describe why this impact is useful for your business. State the problem to be solved. | Impact Mapping |
| 321 | Why Type | Type-specific category for whys. | Impact Mapping |
| 322 | Work Instruction | Work Instructions define procedures for processes. Provide the most detailed information here how tasks are to be executed. This includes best practices. | Service Management |
| 323 | Work Instruction Type | Type-specific category for work instructions. | Service Management |
| 324 | Wrap-up | Track what you have achieved and the reasons why. Check what you have learned and find areas where you can improve. | Objectives and Key Results |
| 325 | Wrap-up Type | Type-specific category for OKR wrap-ups. | Objectives and Key Results |
| 326 | Year | Create a year in your Diary. | Developer Diaries |
| 327 | Year Type | Categories for years. | Developer Diaries |
