> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vexaris.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom pages and FAQ

> Publish extra pages with their own address, and build the FAQ block that answers the questions that block a sale.

## Custom pages

**Marketing → Custom Pages** publishes standalone pages such as About, How it works or a refund guide. Each page gets its own address on the store.

| Field | Notes |
| - | - |
| Page title | Heading of the page and the default browser title |
| URL slug | The path, for example /about. Generated from the title when left empty |
| Meta description | Used by search engines and link previews |
| Editor mode | Rich text, or raw HTML for embedded layouts |
| Status | Draft or published |

**1. Create the page**

Use **Create New Page** and give it a title.

**2. Write the body**

The rich editor handles headings, lists, links, images and tables. Raw HTML mode is for anything the editor cannot express.

**3. Publish**

Draft pages stay reachable only from the admin panel.

**4. Add it to the menu**

Custom pages are not added to navigation automatically. Link them from **Appearance → Header Editor** or **Footer Editor**.

> [!WARNING]
>
> Raw HTML is sanitised on save. Script tags, inline event handlers and embedded frames are removed, so paste markup that relies on them will look different than expected.

## FAQ

**Marketing → FAQ** builds the question and answer block that appears on the landing page and, when enabled, on product pages.

| Field | Notes |
| - | - |
| Question | Shown as the accordion row |
| Answer | Revealed when the row is opened, supports links and lists |

**1. Add a question**

One question per row, written the way a customer would ask it.

**2. Answer it plainly**

Two or three sentences. If the answer is long, link to the full page instead.

**3. Reorder**

Put payment and delivery questions first, they are the ones that block a purchase.

## Which questions to write

* How is the product delivered, and how fast
* Which payment methods work in which currency
* What happens if a key does not work
* Is there a refund policy, and where is it written
* Do you offer support, and in which language

> [!NOTE]
>
> The FAQ block also emits FAQ structured data, which can earn extra space in search results. Keep every answer honest and specific, generic answers are ignored by both customers and search engines.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.