The page is totally empty. You need to add the Document Properties Marker Macro for the document properties and the Section Macro for each section required for your documents.

Some properties should be provided by all documents. These include a name and a short description. To organize you documents the properties subject, categories and tags should also be supported. There are a number of other properties that probably should also be supported. The same is true for sections: often a description and a summary helps readers to find the information quickly. References and resources point to further information at other places. Having the same basic set of properties and sections at the same location in all documents help readers to find what they are looking for.

Advice: Look for a template that supports basic properties and sections.

The projectdoc Blank Document Doctype is installed with the projectdoc Toolbox. It provides the standard properties and sections, but it does not assume that the Core Doctypes Add-on with the core doctypes like Subject, Category, Tag, Role, etc. are installed. Therefore the values (second column in the document properties table (inside the Document Properties Marker Macro) do not use the macros (like Name List Macro or Display Document Property Ref Macro) to create references to these organizing document instances.

Advice: Install the free Core Doctypes Add-on and take advantage of the organizing document types.

At smartics we learned that many users choose the Topic Doctype if they want to document something generic, where no other template seems to match their needs.

Choosing the Topic template is not recommended, since it provides a number of properties and sections that are not generic. The topic template is supposed to provide information on a given topic to a defined audience. Therefore properties like "Level of Experience", "Expected Duration" and sections like "Prerequisites" are provided that do not make sense if - for instance - you want to document a contract or a certificate.

Advice: Use a template with a minimal set of properties and sections.

The Generic template provides all properties and sections commonly used. Documents of this type are intended to be top-level, but they do not provide a homepage for the types of this document. There is an index page that lists all documents of this type.

You may replace the value of the Doctype Property with the name of your ad-hoc doctype. But this will not create a new doctype. Doctypes need to be implemented by blueprints. By changing the value of the doctype property only this value is changed. This may be useful to select your documents by a query (for instance with the Display Table Macro). But this selection can also be made possible by introducing a new document property.

Advice: Use the Generic Doctype for documents of generic type.

A document based on the Section template is similar in structure to document created with the Generic template. The only difference is the name of the doctype and the creation of the page title. A section document is supposed to be a sub-document and therefore the title of the parent document is appended to the sub-document's title. Since every page in a space is required to have a unique name, sub-documents typically have clashing titles, this way of title creation enforces an easy to use rule.

Most of the time sub-documents are generic. There are some exceptions, for instance the Excerpt Doctype or Alternative Doctype.

Advice: Use the Section Doctype for sub-documents of generic type.