Docvora Documentation
Docvora Website Features Pricing Contact Us
Content & Editing IconContent & Editing

Page Nesting

By Docvora Assistant 2 mins 3

Page nesting allows related pages to be grouped underneath a parent page. This creates a clearer structure within a space without changing the URL of the nested pages.


Parent and child pages

A page can be assigned a parent page when it is created or edited.

Pages placed underneath another page become child pages. Child pages are displayed within an indented dropdown beneath their parent in the space page list.

Nesting can continue across multiple levels. Docvora has been tested with page structures up to six levels deep.

A child page can be moved to another parent at any time by editing the page and selecting a different parent. Selecting no parent returns the page to the top level of the space.

Changing or moving a parent page does not automatically move its child pages. Any required changes to child pages need to be made separately.


Page URLs and nesting

Page nesting is used for organisation and does not change the page URL.

Pages continue to use the standard structure:

/:space/:page

This means a child page can be accessed directly without including its parent pages in the URL.

Changing the parent of a page also does not change its URL.


Reordering content

The order of pages within a space is controlled by the Page sorting order configured for that space.

Changing the sorting setting changes how pages are arranged within the space navigation.

Parent and child relationships are separate from the sorting order. Nesting determines which pages appear underneath a parent, while the space sorting setting determines the order in which pages are displayed.


Structuring documentation

There is no required structure for documentation in Docvora.

Spaces can be used for broader areas of documentation, while parent and child pages can be used to group related topics within each space.

For example, a larger feature area may be represented by a parent page with individual guides nested underneath it.

The structure can be adapted to suit the documentation being created, whether it is a knowledge base, product documentation, internal documentation or another type of content.