Database Naming Conventions

To keep everything organized, searchable, and consistent, follow these naming conventions when creating database types, option sets, page names, and reusable elements.

1ļøāƒ£ Use Snake Case

āœ… Always use snake_case (lowercase with underscores) for naming:

  • Database types

  • Option sets

  • Pages

  • Reusable elements

šŸ”¹ Example:

  • āœ… dt_user_profiles (Good: Easy to read & search)

  • āŒ UserProfiles (Bad: Harder to search)


2ļøāƒ£ Prefix Your Names for Clarity

To quickly identify different types of data, use these prefixes:

Prefix
Meaning
Example

dt_

Data Type

dt_email, dt_settings

os_

Option Set

os_navigation, os_status

šŸ“Œ If an abbreviation already exists (e.g., API), you can keep it capitalized: dt_API_logs.


Why Use This Naming Standard?

āœ… Easier to search in Bubble's editor āœ… Keeps everything structured and predictable āœ… Prevents confusion when working with large apps

By following this simple and clear convention, your BubbleBase app will remain scalable, organized, and easy to maintain.

Last updated