> For the complete documentation index, see [llms.txt](https://docs.findable.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.findable.au/create-pseo-pages/page-design.md).

# Page Design

Before you send your pages live, you’ll need to design them. This is the same process if you’ve built a page in Webflow before.

The Webflow CMS uses page templates to standardise how content is displayed across all items in that CMS collection. You’ll only need to design the page once to publish every item you’ve synced!

If you’re familiar with the ins and outs of designing with Webflow’s CMS, it’s still worth checking out these sections to ensure you’re using your Findable pages to their full potential.

{% hint style="info" %}
If you’re new to the Webflow CMS, [Webflow University’s courses on CMS design](https://university.webflow.com/courses/cms-and-dynamic-content) are a great place to start.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.findable.au/create-pseo-pages/page-design.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.