> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/components/data-and-organisation/top-pages.md).

# Top Pages

Display an automatically updated list of top-level pages or folder contents

The Top Pages component automatically creates a list of site pages. Use it for simple navigation, a sitemap, or a set of links that stays in sync as your page structure changes.

{% embed url="<https://www.youtube.com/watch?v=izxsNWPrPe8>" %}

### How to Use Top Pages

You’ll find Top Pages under **Navigation** in the Components list.

1. Drag **Top Pages** onto the page.
2. Choose all top-level pages or select a folder.
3. Set the direction, alignment, justification, and gap.
4. Choose whether to show page icons and titles.
5. Style the title’s Default and Active states.

### Component Settings

#### Pages

**Show**

* **Top Level Pages** — Lists all pages at the root of the site. This is the default.
* **Folder** — Lists the pages inside the selected Folder link.

**Direction** displays links Horizontally or Vertically and defaults to Horizontal.

**Align** controls cross-axis placement and defaults to Centre. **Justify** controls main-axis placement and defaults to Start. **Gap** defaults to theme spacing 4.

**Icons**

* **Show** — Displays each page’s icon. It is off by default.
* **Layout** — Arranges the icon and title horizontally or vertically.
* **Alignment** — Positions the icon at Start, Centre, or End.
* **Size** and **Spacing** — Default to theme spacing 4 and 2.

**Page Titles**

**Show** is enabled by default. Font defaults to the Body font and Size to Base. Weight defaults to 400, letter spacing to Normal, and Italic is off.

Use **State** to style Default and Active titles independently. Configure Color, Opacity, Shadow, and Underline for each state.

### Accessibility

Use descriptive page titles and preserve a visible active state. Page icons should support the title rather than replace it unless their meaning is unambiguous.

### Related Components

* [Menu](/elements-docs/using-elements/components/navigation-and-interaction/navigation-standard.md) — Provides full responsive site navigation.
* [Tree](/elements-docs/using-elements/components/data-and-organisation/tree.md) — Displays expandable multi-level navigation.
* [Breadcrumbs](/elements-docs/using-elements/components/navigation-and-interaction/breadcrumbs.md) — Shows the current page’s position in the site.

| Common Control                                                                                                     | Description                                                             |
| ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
| [Link](/elements-docs/using-elements/components/common-controls/link.md)                                           | Link to a page, resource, anchor, email address, or website.            |
| [Layout](/elements-docs/using-elements/components/common-controls/layout.md)                                       | Control positioning, stacking, visibility, overflow, and isolation.     |
| [Sizing](/elements-docs/using-elements/components/common-controls/sizing.md)                                       | Set width, height, and responsive size constraints.                     |
| [Spacing](/elements-docs/using-elements/components/common-controls/spacing.md)                                     | Add responsive margin and padding.                                      |
| [Typography & Text Styles](/elements-docs/using-elements/components/common-controls/typography-and-text-styles.md) | Control fonts, text spacing, decoration, colour, and semantic wrappers. |
| [Backgrounds](/elements-docs/using-elements/components/common-controls/backgrounds.md)                             | Apply colour, image, gradient, SVG, video, and hover backgrounds.       |
| [Transitions](/elements-docs/using-elements/components/common-controls/transitions.md)                             | Choose what animates and set its timing curve, duration, and delay.     |
| [Effects](/elements-docs/using-elements/components/common-controls/effects.md)                                     | Apply shadows, opacity, and hover effects.                              |
| [Filters](/elements-docs/using-elements/components/common-controls/filters.md)                                     | Apply blur, brightness, saturation, shadow, and backdrop effects.       |
| [Transforms](/elements-docs/using-elements/components/common-controls/transforms.md)                               | Scale, rotate, move, and skew components.                               |
| [Borders](/elements-docs/using-elements/components/common-controls/borders.md)                                     | Set border style, colour, opacity, width, radius, and hover states.     |
| [Advanced](/elements-docs/using-elements/components/common-controls/advanced.md)                                   | Add CSS classes and IDs, or change supported HTML tags.                 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmacsoftware.com/elements-docs/using-elements/components/data-and-organisation/top-pages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.