BubbleBase
  • Introduction
    • What is BubbleBase?
    • Why Use BubbleBase?
    • How BubbleBase Works
  • Getting started
    • 1. Installing & Setting Up BubbleBase
    • 2. Understanding the Folder & Page Structure
    • 3. How to Customize BubbleBase for Your Project
  • Best practices
    • Database
      • Database Naming Conventions
      • Iconography
    • Design
      • Designing Responsively
        • Responsive Group Settings
        • Breakpoints
        • Page/Group Structure
      • The APG Naming System
        • Naming Conventions
        • Element Shorthand
        • Standardizing Group and Element Names
          • Commonly Occurring Elements
          • Naming Groups Within Groups
    • Workflows
  • APIs
    • Stripe
      • Stripe Checkout (payment mode)
        • Stripe Checkout (payment + price id)
        • Stripe Checkout (payment + no price id)
        • Stripe Checkout (payment + price id + multi line items)
      • Stripe Checkout (subscription mode)
        • Stripe Checkout (Subscription with price id)
        • ⏳ Stripe Checkout (Subscription without price id)
      • Stripe Checkout (marketplace)
      • Stripe Customer Portal
      • Create Customer
      • Retrieve Charges
      • Delete Subscription
      • Retrieve Subscription
      • Retrieve Invoice
      • Retrieve Price
    • SendGrid
      • Send Email (standard)
      • Send Email (template)
  • Data
    • Data types
      • Essential Data Types
        • User
        • Dt_user_profile_images
      • Navigation Data Types
        • Dt_Sidenav
      • Functionality Data Types
        • Dt_Reviews
        • Dt_Notifications
        • Dt_Invoices
        • Dt_Line_Items
        • Dt_email
        • Dt_email_template
        • Dt_email_footer_link
        • Dt_charge
        • Dt_credit
        • Dt_contact_requests
        • Dt_API_logs
      • Kit Data Types
        • Dt_(Kit)_Jobs
        • Dt_(Kit)_AI_messaging_thread
        • Dt_(Kit)_ai_thread
        • Dt_(Kit)_comment data
        • Dt_(Kit)_company data
        • Dt_(Kit)_dashboard_metrics
        • Dt_(Kit)_FAQs
        • Dt_(kit)_form_questions
        • DT_(Kit)_form_answers
        • Dt_(kit)_listings
        • Dt_(kit)_messaging_channel
        • Dt_(kit)_messaging_thread
        • Dt_(kit)_pricing
        • Dt_(kit)_reviews
        • DT_(Kit)_Task List
        • Dt_(Kit)_Task Stage
        • Dt_(kit)_task_comments
        • Dt_(kit)_Tasks
    • Option Sets
      • Navigation Items
        • 🔒 os_navPage
        • 🔒 os_nav_Subpage
        • 🔒 Os_nav_Tab
      • User Roles and Actions
        • 🔒 os_user_types
      • Data Categorization
        • 🔒 os_record_interaction
        • 🔒 os_record_type
        • 🔒 os_action_type
        • Os_toast_type
      • App-Wide Settings
        • 🔒 System
  • Plugins
    • Google
  • Reusable Elements
    • UI Components
      • Authentication Page
        • Design
        • Workflows
      • Landing Page (index)
        • Hero
        • Features
        • Metrics
        • Call-to-Action
        • Pricing
        • FAQs
        • Testimonials
      • Dashboard Page (home)
      • My Profile
  • Popups
    • 🍿 PU_CRUD
    • 🍿 PU_Delete
    • 🍿PU_Action
    • 🍿 PU_Loading
  • App-Wide Components
    • 🔐 Security Redirect
    • ⚙️ Global Events
    • 📌 FG_Sidebar
  • Workflows
    • Frontend workflows
    • Backend workflows
      • delete_user (example)
Powered by GitBook
On this page
  1. Best practices
  2. Design
  3. The APG Naming System
  4. Standardizing Group and Element Names

Naming Groups Within Groups

Every group has a generalizable structure that we are going to use to further standardize the naming of groups within groups.

Below you will find a detailed outline of their different contexts and naming conventions:

Group Name
Context
Design Notes

GP {page} Container

This should be the first group on every page

This group should contain the base conditional logic that makes the whole page responsive.

GP {PG} Container

This group is primarily used as the first group label for any groups with multiple subsections or other complex groupings.

This group may not always be needed.

A good context for such a group is when you have multiple "pages" nested and hidden within a single page. E.g. GP Users Container, GP Admin Container.

GP {PGI} Content OR GP {PGI} {CG} Content

This group is used as the container for simpler groups that primarily display content (e.g. text, img)

This will likely get used in most groups, particularly ones with minimal elements. It is usually one of the first nested groups under the parent group.

GP {PGI} Head

This is the header, upper, or first section within a group.

"Head" is used to avoid confusion with headers when searching.

Common elements found in this group are: Titles/headings, helper text, icons, avatars/logos/images.

GP {PGI} Body

This is the main/central section within a group

Common elements found in this group are: repeating groups, plugins, reusable elements, long text sections, images, etc.

GP {PGI} Foot

This is the footer, lower, or last section within a group.

"Foot" is used to avoid confusion with footers when searching.

Common elements found in this group are: socials, icons, links, etc.

GP {PGI} Card OR GP {PGI} RG Card (when used in a RG)

A card contains all the information of 1 thing (e.g. user, pricing option)

Cards are typically used in repeating groups, but may be used elsewhere.

They should be the first group inside the repeating group.

They typically have a background and a border as styling.

GP {PG} Cell or GP {PG} RG Cell or GP {PG} TBL Cell

A cell contains all the information of 1 instance or data point (chat message, admin or finance data)

Cells are used in tables, appear commonly in repeating groups, and may be used elsewhere.

They should be the first group inside the TBL/RG/GP and pull data from databases or APIs.

They typically have no background and or border as styling, but may have styling in use cases like chat.

RG {PG}, or

RG {PG} {CG}

A repeating group is used to pull multiple data items.

Repeating groups should use predominantly transparent separators to create spacing between cards.

PreviousCommonly Occurring ElementsNextWorkflows

Last updated 2 months ago