> For the complete documentation index, see [llms.txt](https://bubble.citizendev.io/bubble-convention/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bubble.citizendev.io/bubble-convention/naming-conventions/element-naming/other-notations.md). # Other notations ## Notation of state, data & clickable We figured out that elements with custom states, data source or clickability usually required a lot of attention. Without notations, you would need to memorize the elements or painfully search for them in workflows or the element tree. Hence, we recommend adding notations in front of the elements names: * **\** or **\** for elements with custom states. * **\** or **\** for elements with custom data sources (parent elements only, no need to mark child elements that inherit the data). * **\** or **\** for non-input elements that are clickable (e.g. texts, groups).

An example of using notations

This is very efficient while using Bubble's search function, as the < and > differentiate the elements from other elements. In the case of having multiple notations, you can order the notations however you like, alphabetically for instance. It would be preferable to use shorten forms of the notations though. ## Elements grouping The meaning of *grouping* here transcends the traditional meaning of nested groups and elements. Instead, please understand this *grouping* as an umbrella term for element nesting, element classification and categorization according to usage, placement, etc. In this case, the use of a **\[Tag]** in front of the elements is recommended. An example of this is the case of having 2 identical groups of elements with close usage, yet for a reason you cannot merge them into one. Having tags helps differentiate an element from its identical counterpart in the other group, as well as to perform search for elements better. Below is an example of 2 forms with identical elements but used for different purposes.
[Onboard] Group Form[Invite] Group Form
[Onboard] Text Title[Invite] Text Title
[Onboard] Input Name[Invite] Input Name
[Onboard] Button Submit[Invite] Button Submit
## Notation of order Groups, data fields, option set fields, etc when related to ordering (e.g. steps in an onboarding process, indicated by an option set) should come with a number indicator (`no_`) before the name. Example: `1_onboardingStep`; `2_onboardingStep` The number should always come before the name to help with sorting. --- # 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://bubble.citizendev.io/bubble-convention/naming-conventions/element-naming/other-notations.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.