> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/components/app-bar/abc-center.md).

# Θ ABC - Center

App Bar Control (ABC)

Collection: The App Bar Container (ABC) is a collection of the content that is in the center (horizontally) of the app bar. This content can be informative or actionable depending on the type of app bar.

[Styleguide Link](https://zpl.io/2vjgx55)

* Parent: [App Bar Top & Bottom](/core/components/app-bar.md)
* Children: [ABC - Pieces](/core/components/app-bar/abc-pieces.md)

## Properties

### Type

The general theme for the collection of controls, most often this type will be the same as the central (most centered) object in the collection. These "Types" are supplied by the abc-pieces collection.

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2Fe9OwEb3cLfkdm9Hc65dk%2FABC%20-%20Center.png?alt=media&amp;token=5092e280-42e9-4821-ad3f-26a2611ecf82" alt=""><figcaption></figcaption></figure>

**Title** (default)- Informational content to give the user the name/action of the screen they are on.

**Wordmark/Logo** - Normally for branding purposes with the wordmark just being a wider reserved width of 21:9 and the logo set to a 1:1 ratio.

**Search** - When one of the primary abilities of the screen is to search its contents we will opt to show the search field as opposed to hiding it behind a search icon.

**Toggle** - When the contents of the screen can be divided into sub sections we can drop in a toggle button group.

**Tab Bar** - The ability to navigate to the primary areas of the application in a side-scrollable (optional) grouping of tabs.

**None** - Of course the app bar could also set the center area to nothing at all.

## Functionality

The ABC - Center expands to fill the full width of the App Bar, where the Leading and Trailing sections hug their contents.


---

# 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://able.bucca.com/core/components/app-bar/abc-center.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.