> For the complete documentation index, see [llms.txt](https://learn.adaptcms.com/adaptcms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.adaptcms.com/adaptcms/core-packages/pages.md). # Pages Pages are essentially static parts of your public website, such as a home page or an about page. By default, a page has a title, a URL and status. The URL defines where the user will be able to access the page relative to the website domain. To help non-tech users better be able to manage the content that appears on pages without doing any coding themselves, fields may be attached to a page creating a `PackageField`. Utilizing this feature a developer, for example, could define hero fields, content sections using the `FieldRichText` field, basically enabling the user to go into the admin and modify the content in these fields. The developer would then modify the page template to display these values in the appropriate places. To customize the Vue component for a page, you will find it in this path: ``` /packages/Adaptcms/Site/ui/pages/pages/{name}.vue ``` Please note also that you can customize the data that is passed to the view by modifying the `PagesController` which is also in the `Site` package. --- # 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://learn.adaptcms.com/adaptcms/core-packages/pages.md?ask=&goal= ``` `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.