Content reporting
Posts, authors and topics from the models your CMS already has, with bounded dimensions that say what went into Other rather than quietly dropping the tail.
Posts, authors and engagement
Name the Post model and its published-at, and posts over time, output per author, and engagement by category follow. If comments or reactions are models too, they are measures like any other.
It reports on what you published, not what was viewed
This reads your own database, so it knows what exists, who wrote it, and what state it is in. Page views come from a tracker on the page, and that is a genuinely different question. Most teams want both, and this is not trying to be the other one.
Drafts and scheduling behave
A draft is not counted as published, because the filter that excludes it is part of the description rather than something each report remembers to add. Declare it once and every block that reads that model inherits it.
A dashboard for people who never sign in
A share link gives an editor or a client the numbers with no account, from your own domain, and you can turn it off.
Report on what gets read
Publish and view events are enough for the first content report, and the CMS integration sends both already.
Start free