> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/design-and-structure.md).

# Pages and components

A brief overview of design and structure.

Applies to **Classic App Builder**. Screens and recordings in this section show the Classic interface.

Build an interface from pages, layouts, and components, then connect it to data and actions.

## Choose a reference

* [Customize pages](/classic-app-builder/design-and-structure/pages.md) for page structure and navigation.
* [Components](/classic-app-builder/design-and-structure/components.md) for the component reference.
* [Generate a record page or dashboard](/classic-app-builder/classic-tutorials/ui-in-seconds.md) for an initial interface.
* [Field values](/classic-app-builder/design-and-structure/column-values.md) for displayed values.
* [Nested filters](/classic-app-builder/design-and-structure/nested-filters.md) and [Advanced filters](/classic-app-builder/design-and-structure/advanced-filters.md) for data selection.
* [Sort](/classic-app-builder/design-and-structure/sort.md) and [Group](/classic-app-builder/design-and-structure/group.md) for presentation.
* [Dropdown popups](/classic-app-builder/design-and-structure/dropdown-popups.md) for additional controls.

## Change an existing page

1. Identify the component and the resource it uses.
2. Review its displayed fields, filters, and selected-record behavior.
3. Adjust the relevant settings.
4. Test with a populated result, an empty result, and a different selection.
5. Check the page with the intended user role before publishing.

Continue with [Data binding and variables](/classic-app-builder/binding-and-values.md) when the component needs another component's value.

## Visibility and authorization

[Visibility rules](/classic-app-builder/design-and-structure/visibility-rules.md) and [Conditionals](/classic-app-builder/design-and-structure/components-visibility.md) control presentation. Hiding a component does not by itself establish that its underlying data request is forbidden. Use [App and data permissions](/access-and-sharing/app-and-data-permissions.md) to review enforcement.


---

# 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.jetadmin.io/classic-app-builder/design-and-structure.md?ask=<question>&goal=<user_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.