Naming Conventions

To create consistency across apps and make elements easier to find in workflows, please using the following naming conventions.

Naming different Groups or Elements

For Parent Groups:

{Element Shorthand} {Describe Parent Thing}

For Example: "GP review listing"

For Organizing Groups:

{Element Shorthand} {Parent Group Initials} {Organizing Group Name}

These are explained in more detail in the Naming Groups Within Groups Section, but put simply, you should break up each page (and where necessary, complex groups) into three sections:

Head = top/first

Body = Middle

Foot = Bottom/last

For Child Groups:

{Element Shorthand} {Parent Group Initials} {Organizing Group Initial} {Describe Child Thing}

For Example: "TXT RL H date"

NOTE: you can continue to chain on child group names as is appropriate as you nest deeper, however if you use organizing group initials consistently, this should become less necessary.

For Reusable Elements:

{Reusable Element Name} {Page Name}

To avoid confusion when using a reusable element multiple times replace Bubble's automatic "A", "B", "C" with the page name.

If you use the same reusable multiple times on a page, simply follow the standard naming conventions.

{Reusable Element Name} {Page Name} {Parent Group Initials} {Organizing Group Initial} {Child Thing}

Try to make it only as complex as it needs to be, usually parent group initials will be enough.

Here is an example of a simple page layout using the APG nomenclature and design principles:

Resolving Naming Conflicts

By using the {Parent Group Initials} and {Organizing Group Initial}, you should avoid 99% of conflicts. However, if conflicts occur between similar groups or elements, they will likely occur:

• Within the same parent group:

  • In this case, please differentiate by creating {Sibling Group} names and using the following structure:

{Element Shorthand} {Parent Group Initials} {Organizing Group Initial} {Sibling Group name/initial} {Describe Child Thing}

Wherever possible try to avoid using numbers, as this can get confusing in workflows for those unfamiliar with the app (however, use your judgment, as there may be times when this makes the most sense).