> 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/advanced/ui.md).

# UI

### Override Core UI Views

With this feature, you could fully customize every single view rendered from the CMS. For more practical purposes, lets look at a realistic use-case of wanting to override the default login page with your own designed login page.

All it takes in this example is creating a file at `/packages/Adaptcms/Site/ui/pages/Adaptcms/Auth/login.vue`&#x20;

That path can be used with anything. In the example above the full path to the Auth login view is `/packages/Adaptcms/Auth/ui/pages/login.vue` - so as you can see we snip out the `ui/pages` part, essentially taking the vendor, the package name, and the path within the pages folder.

The only exception to overriding views are ones with a vendor/package explicitly set in the controller, although this method is strictly used at the moment to render `Site` views from a different 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/advanced/ui.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.
