Use a Page Hierarchy as a Template

Last modified by Eleni Cojocariu on 2026/10/13 17:57

Steps

A template can be a branch of the wiki rather than a single page: when the template page has children, creating a page from it copies the children too, so your users start from a ready-made structure instead of one empty page. Page Templates explains how a template is offered in the first place.

  1. Build the hierarchy you want copied under a single non-terminal page. Everything below that root is copied, at any depth.

    The navigation tree showing the Project Template page, with Meeting Notes and Specification below it and Requirements below Specification

  2. Create a template provider and set its Template to use field to the root of that hierarchy, not to one of the pages below it.
  3. Create a page from the template, and let the first save finish: the pages are copied by a job, so a progress notification runs at the bottom of the window and the save button stays disabled until the copy is done.

    The bottom of the edit form during the first save, with the Done button disabled and a Saving 33.3 percent notification below it

  4. The new page now holds a copy of the whole hierarchy, one page per page of the template, under the name and the location you chose in the wizard.

    The navigation tree showing the new Apollo page under Projects, with the copied Meeting Notes, Specification and Requirements pages below it

FAQ

Can a terminal page be the root of a template hierarchy?

No. A terminal page cannot have children, so there is nothing below it to copy. Only a non-terminal page carries a hierarchy.

What are the copied pages called?

The same as the pages below the template root. Only the new page itself takes the title and the location you entered in the creation wizard.

Related

Get Connected