The documents of a given doctype are organized in homepages. Most of the doctypes have a homepage where the central documents of their types are stored. For each doctype that provides a homepage, the blueprint wizard to create a document provides a checkbox to store the new document as a child of the doctype homepage.

Confluence index pages collect each document created with a given blueprint wizard. Homepages of doctypes reference only those documents that are send to them. There are two kinds of documents that are not stored on the homepage:

1. documents that are children of a document of the same type (with their root parent being a child of the doctype homepage)
2. documents that are children of documents a different type

While the first imposes a natural organization of documents and subdocuments (think of roles where the subdocuments document refer to specialized roles of their parents), the second usage implies a close relationship between the documents. This second close relationship implies defines that the subdocument has to be deleted if when the parent document is deleted. That is: they have the same lifespan.

Homepages may change their structure over time. Some doctypes will only contain a very limited number of documents (e.g. their are typically only a few roles in a small project), but others may have large numbers (e.g. the minutes of meetings may get plenty for larger teams). Therefore expect that the homepage may have subpages that collect documents that match to organize documents matching certain criteria. The documents will always be stored to as children of the type homepage.

Some documents are relevant to more than one space. If you have a large project with multiple large components you may want to have a space for each component to you describe. Each component team may share the same roles and topic types. So there is no need to have them copied around spaces but instead . Instead have them stored in a commonly collaboratively used delegate space. The index space is by definition a default delegate space. But you may declare any space as the delegate space of a given space by adding the space property delegate-space.

Once you have one (or more) delegate space(s) declared, you may remove the homepages of those document types you want to store in the delegate space. If a user selects as the target location of a new page via the "Send to Homepage" parameter, projectdoc automatically selects the homepage from the nearest delegate space.

The search space is defined by the search-space space property. It defines for all projectdoc query macros provided by projectdoc the spaces to search for documents. Per default the search space is the same as the delegate space. You may change that by the use of the space property use-default-delegate-space-as-search-space.

If you want to list all documents with some criteria of a given doctype, then all documents from the spaces listed as search space that match these criteria are in the result set.