Folder, group, rule — organizing 100+ rules
You keep five rules in your head. Fifty — not anymore. JustZix has a four-level hierarchy that scales from "one quick fix" to "a hundred rules across a dozen projects". Here is how to use it.
The four levels
- Folder — the top level. It has its own URL pattern and a three-letter floating-button label. This is where you keep a "project" or a "client".
- Group — sub-organization inside a folder. Every folder has at least one group. This is where you separate, say, "styles" from "actions".
- Rule — the actual CSS/JS unit. Belongs to one group.
- Action — a clickable button that runs JS on demand. Belongs to a rule.
A toggle cascades downward
The most important principle: turning off a higher level turns off everything below it. Turn off a folder — all its groups, rules and actions go silent, with one click. That lets you quickly "mute" an entire project without touching individual rules.
How to organize it — a pattern for 100 rules
- Folder = context. One folder per client, project or large site. The folder's URL pattern covers that whole context.
- Group = role. Inside a folder: a "cosmetics" group (CSS), an "automation" group (JS), a "QA" group (actions). Easy to disable a whole role.
- Rule = one job. One rule does one thing. "Hide ads" and "fix the table" are two rules, not one — easier to toggle and diagnose separately.
Why not one giant rule
It is tempting to dump a site's whole CSS into one rule. Do not: when one fragment breaks, you cannot disable it without disabling the rest, and diagnosis ("which of 200 selectors?") becomes a nightmare. Small rules mean precise toggling and an easy hunt for the culprit.
See also
- URL patterns — how patterns stack in the hierarchy
- How sync works — the hierarchy across devices
- JustZix for a QA team — the hierarchy as a unit of sharing
Install JustZix — and tame a hundred rules before they tame you.
Rate this post
No ratings yet — be the first.