Child pages
  • Default Homepages

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Document Properties Marker
overridefalse
Short DescriptionDocument type homepages in the index space serve as automatic homepages if the current space lacks a homepage for that document type.
Doctypetopichide
NameDefault Homepages
Short Name
Parent
Parent Property
property-nameName
hide
Audience
Name List
doctyperole
render-no-hits-as-blanktrue
propertyAudience
empty-as-nonetrue

Subject
Name List
doctypesubject
propertySubject

Categories
Name List
doctypecategory
propertyCategories

Tags
Tag List
propertyTags

Iteration

Iteration
valuefilledfinished

hide
Type
Name List
doctypetopic-type
render-no-hits-as-blanktrue
propertyType

Level of Experience
Name List
doctypeexperience-level
render-no-hits-as-blanktrue
propertyLevel of Experience

Expected Duration
Sponsors
Name List
doctypestakeholder
render-no-hits-as-blanktrue
propertySponsors

Sort Key00100-0050000400hide
Section
show-titlefalse
titleDescription

Document type homepages make it easier for authors to find the right location for a new document. Typically authors should store a new document dependent on invariant information of the document. That is related to information that will never change. Thinking about what information this could be it almost always boils down to a very limited number of metadata information: creation date (and maybe user) and the type of document.

All page wizards for projectdoc blueprints provide a tool to store a new document as a child to its document type homepage instead of the current page.

...