> For the complete documentation index, see [llms.txt](https://docs.civictheme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.civictheme.io/content-authoring/components/list-components-and-cards/cards-for-lists/navigation-reference-card.md).
# Navigation reference card
### Summary
The Navigation reference card is a Navigation card that links to previously created content. This component is ideal if you wanted to create a list of content that's displayed as Navigation cards.
This article shows you how to add a Navigation reference card to the Manual list component.
Below is an example of a Navigation reference card
### Step 1 - Add the Navigation reference card
Within the Manual list component under List items, click on the dropdown and select Navigation reference card as shown below.
### Step 2 - Fill in the various fields
There are only 2 fields.
1. Reference - This is an autocomplete text field that will suggest **Page content type** titles as you type.
2. Theme - Select whether you want light or dark theme settings.
The screenshot below shows what happens as you type the first character into the Reference text field. The site will automatically search page titles containing the typed character.
---
# 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.civictheme.io/content-authoring/components/list-components-and-cards/cards-for-lists/navigation-reference-card.md?ask=&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.
