> For the complete documentation index, see [llms.txt](https://apg-software-solutions.gitbook.io/bubblebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apg-software-solutions.gitbook.io/bubblebase/best-practices/design/the-apg-naming-system.md).

# The APG Naming System

## Nomenclature

Nomenclature is the structured method by which we name everything in Bubble. A simple differentiation between database items and page elements is made to make searching up data sets and elements easy:&#x20;

* database items: use\_snake\_case&#x20;
* Page Elements do not use snake case.&#x20;

To streamline builds between developers, eliminate confusions, and make naming things really easy, it is recommended that you follow the APG Naming System as it's described.&#x20;

The APG Naming System is composed of the following guidelines

* [Naming Conventions](#naming-conventions) (i.e. how to name a group/element systematically)
* [The Element Naming Shorthand](#element-naming-structure) (e.g. naming all groups GP)
* [Standardizing Groups and Element Names](#standardizing-group-and-element-names) (as this can get messy)


---

# 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:

```
GET https://apg-software-solutions.gitbook.io/bubblebase/best-practices/design/the-apg-naming-system.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
