Every stat on this page is the voyager/pulse binding source at work: fifteen composite metrics computed from what this WordPress install actually contains — CPT counts, post dates, the pattern and block registries — not a stats file someone updates when they remember to.
The mechanics are deliberately boring: one get_value_callback, one compute function (voyager_demo_compute_pulse_data(), in this theme’s functions.php), one two-hour transient. Publishing velocity is a 90-day rolling window; freshness is the share of content touched in the same window. The blocks rendering these values are stock core blocks bound by key — the dashboard below has no custom block code at all.
Current limitation, stated plainly: Pulse self-queries this site, so the numbers are only as big as the demo. The roadmap moves the compute to a Portal-level fleet aggregate — same binding contract, bigger denominator. When that lands, this page won’t change a line of markup.
Ecosystem pulse
Built different. Measured live.
Every number on this page is computed from real WordPress data — CPTs, patterns, publishing velocity, and content freshness. No hard-coded stats.
164
AI abilities registered
In the Abilities API on this install — the registry counts itself
18
Binding sources
Live in the block bindings registry right now
44%
Content freshness
Percentage of content updated in the last 90 days
0.9
Avg posts/week over the last 90 days
0
New content pieces this month
3 weeks ago
Last content published
Published this month:
0
Patterns:
194
Days live:
989
Total content:
45