> 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/standardizing-group-and-element-names/naming-groups-within-groups.md).

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

<table><thead><tr><th width="198">Group Name</th><th width="207">Context</th><th>Design Notes</th></tr></thead><tbody><tr><td>GP {page} Container</td><td>This should be the first group on every page</td><td>This group should contain the base conditional logic that makes the whole page responsive.</td></tr><tr><td>GP {PG} Container</td><td>This group is primarily used as the first group label for any groups with multiple subsections or other complex groupings.</td><td><p>This group may not always be needed. </p><p></p><p>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.</p></td></tr><tr><td>GP {PGI} Content       OR<br>GP {PGI} {CG} Content </td><td>This group is used as the container for simpler groups that primarily display content (e.g. text, img)</td><td>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.</td></tr><tr><td>GP {PGI} Head</td><td>This is the header, upper, or first section within a group.</td><td><p>"Head" is used to avoid confusion with headers when searching. </p><p></p><p>Common elements found in this group are: Titles/headings, helper text, icons, avatars/logos/images.</p></td></tr><tr><td>GP {PGI} Body</td><td>This is the main/central section within a group </td><td>Common elements found in this group are: repeating groups, plugins, reusable elements, long text sections, images, etc.</td></tr><tr><td>GP {PGI} Foot</td><td>This is the footer, lower, or last section within a group.</td><td><p>"Foot" is used to avoid confusion with footers when searching. </p><p></p><p>Common elements found in this group are: socials, icons, links, etc.</p></td></tr><tr><td>GP {PGI} Card              <br>OR<br>GP {PGI} RG Card (when used in a RG)             </td><td>A card contains all the information of 1 thing (e.g. user, pricing option)</td><td><p>Cards are typically used in repeating groups, but may be used elsewhere. </p><p></p><p>They should be the first group inside the repeating group. </p><p></p><p>They typically have a background and a border as styling.</p></td></tr><tr><td>GP {PG} Cell              or GP {PG} RG Cell or GP {PG} TBL Cell              </td><td>A cell contains all the information of 1 instance or data point (chat message, admin or finance data)</td><td><p>Cells are used in tables, appear commonly in repeating groups, and may be used elsewhere. </p><p></p><p>They should be the first group inside the TBL/RG/GP and pull data from databases or APIs. </p><p></p><p>They typically have no background and or border as styling, but may have styling in use cases like chat.</p></td></tr><tr><td><p>RG {PG}, or </p><p>RG {PG} {CG}</p></td><td>A repeating group is used to pull multiple data items.</td><td>Repeating groups should use predominantly transparent separators to create spacing between cards. </td></tr></tbody></table>