projectdoc is based on projectdoc documents. Creating a projectdoc document is easy: A projectdoc document is a Confluence page using document properties and sections.
projectdoc documents are usually defined as page blueprints by the Template Author.
Page Authors select the type of document that suits their requirements and simply add content. If they add new sections they are encouraged to use the Section Macro. But if the content is not meant to be transcluded, authors may decide to use simple HTML headers.
The document type supports authors in writing documents of a given kind. Due to the nature of the templates, readers only see those properties and sections which have meaningful information.
This we call "Guided Writing & clutter-free Reading".
What is Transclusion?
Transclusion is the inclusion of a document or part of a document into another document by reference.
Getting started with the projectdoc Toolbox is not easy. Some basic concepts are more than just good-to-know and the number of macros and doctypes may be simply overwhelming. This tip gives some advice on how to get started.
A gentle introduction to page blueprints provided by doctype add-ons. The page blueprints are grouped semantically to make it easier for users to build a conceptual mind map for them.
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.
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.
Provides a list of doctypes provided by various free add-ons. Doctypes define properties and sections for documents. They are essentially Confluence Blueprints that help to create pages in your wiki based on templates.