Some front-end features are not 1 injection. A popup is an HTML block for the markup, a CSS block for the styles, and a script that ties them together. They only work as a set, but without groups they sit in the list as 3 unrelated items, each with its own load rules to maintain and its own enable toggle to hit.
A group ties them together as one feature. You give the group a name and assign injections to it. From that point, they share a single set of load rules, enable and disable together, and read as a cluster in the list rather than as separate items.
Load order
Within a group, load order is explicit and editable. You set the sequence, so the CSS always lands before the script that depends on it. Outside a group, injections load in the order they were created. Inside a group, you control it.
Conflict detection
The conflict detector does not flag members of the same group against each other. Members are designed to coexist, so reporting them as conflicts would be noise. Everything outside the group is still checked normally.
Previewing a group
When you preview any member of a grouped injection, the preview assembles the whole group, not just the 1 piece you are editing. If you have unsaved changes in several members at once, all of them are applied simultaneously in the preview, so you see the full feature as it would actually run rather than 1 piece against saved siblings.
Membership
Group membership is stored on each injection. Renaming a group updates the display label everywhere, but the underlying key that ties members together never changes, so a rename cannot break anything. Groups survive export, import, and version history with the injections that carry them.
For the full injections reference, see Injections.
Open 6 to 2. The 8:14 still runs.
