For Admins
Categories & Point Rules (Admin)
Two small config tables drive the entire pay system. Both are data, not code — change them in the admin panel, no deployment needed.
URL Categories (/admin/categories)
The categories engineers pick when submitting URLs. Each has a key, label, colour and display order, and can be deactivated (existing URLs keep their category; it just disappears from the picker).
Special categories created by the system's bridges — keep them active:
- Campaign Post — auto-created from campaign submissions.
- Social Post — also fed automatically by Daily Posts ticks.
Activity Point Rules (/admin/point-rules)
Each rule prices one category: category_key → point value. The salary calculator multiplies the month's submissions per category by the rule's current value.
Rules to remember:
- A category without an active rule earns 0 — the salary pages show a warning listing unpriced categories. Add a rule rather than letting work silently earn nothing.
- Changing a value re-prices open months instantly (they recompute live) but never touches locked months — locked salary snapshots are immutable.
- The featured_engagement rule prices the daily engagement award (currently 30). It works like any category: award days × current value.
The live values are published to the team at Points Reference — worth keeping that mental model: the reference page always reflects whatever you configure here.
Designing values
A sane structure prices effort and value: long-form (Article, Blog Post) above quick actions (Comment, Forum Post), and scarce/high-effort formats (Video) wherever you want behaviour to go. Expect engineers to optimise for exactly what you price — that's the point.