WordPress report goal audit
This page maps the current WordPress Community & Adoption Health report back to the active goal.md file. It is a quick proof map: what is covered directly, what is covered with public proxies or snapshots, and where the refresh metadata lives.
Report sections
Participation, Project Load, and Market Position.
Decision answers
Covered in the main report and the decision brief.
SQLite evidence
Includes 20 hashed source files and fetched public-source tables.
Partial signals
Stored in SQLite and shown in the source coverage pages.
Requirement Coverage
Summarize what has been done so far.
progress_summary.html summarizes the work and links the current report, companion views, source inventory, and refresh docs.
Explain community involvement, project workload, and market position.
index.html contains the three main views, a relevance scorecard, a Goal Coverage Map, Source Coverage, and a final Decision Readout.
Do not treat tickets as the whole community.
The report separates ticket-derived signals, ecosystem signals, and adoption/demand signals at the top of the page.
New, closed, net flow, reporters, first-time, repeat, newcomer return cohorts, maintainer split, response, close time, reopen, stale share, concentration, drive-by vs sustained.
65.0k Core tickets, 32.1k Gutenberg issues, and 12.1k wordpress-develop PRs are loaded. The report uses quarterly Core, Gutenberg, PR, timeline, response, reopen, concentration, and depth tables.
Show bugs, feature requests, and all tickets/issues separately where useful.
The classification trend contains 716 quarterly category rows, with separate Core and Gutenberg category charts plus open-backlog category summaries.
Props, committers, Make/Core, WordCamps, Meetups, plugins, themes, translations, Five for the Future, support, dev notes.
The report includes release credits, committers, Make/Core posts/comments/dev notes, WordCamp records, Events/Meetups, Translate snapshots, Five for the Future, support answer summaries, archived support-view estimates, plugin/theme directory activity, plugin and theme search breadth, Composer package snapshots, and a stale popular-plugin sample.
Installed share, CMS share, newly detected sites, traffic tiers, peer builders, demand signals, plugins, WooCommerce, enterprise.
Installed-share and CMS-share evidence is direct. Newly detected sites, search interest, and broad job demand are presented with public proxies, including compact new-site choice, query-intent, search-interest, and attention/demand summaries, and clearly labeled as partial.
Prefer quarterly time series where the data supports it.
Core, Gutenberg, PR, classification, Make/Core, dev-note, archived support-view estimates, support snapshot buckets, Stack Overflow, Wikimedia, HN hiring, quarterly WordPress Jobs board snapshots, plugin downloads, and many market/demand charts use quarterly or monthly-to-quarterly series where available.
Enough metadata to refresh without rediscovering the model.
data_inventory.html lists table counts, local source hashes, and partial-source gaps. source_gap_plan.html turns those gaps into a collection order. refresh_runbook.html records the refresh path.
End with community health, project load, and market position.
The main report ends with a Decision Readout, and decision_brief.html provides a shareable one-page version with seven visual answer cards.
Partial Signals Stored In SQLite
These are the remaining source areas where the report already has a labeled proxy or snapshot, but the ideal historical source would make the decision view stronger.
Stack Overflow, Wikimedia, npm downloads, Packagist Composer package snapshots, GitHub PRs, GitHub review comments, repository-interest snapshots, and GitHub topic-search breadth are in.
Best next sourceAdd one broader developer-community source if a stable public source is available.
HN hiring threads, Remote OK and Remotive current jobs, and annual plus quarterly WordPress Jobs board snapshots are in.
Best next sourceAdd a broad hiring-platform export.
BuiltWith current pipeline and HTTP Archive proxies are in.
Best next sourceAdd a true first-seen site cohort.
Wikimedia, Stack Overflow, and current autocomplete query-intent proxies are in.
Best next sourceAdd Google Trends or a similar search-provider export.
Current support queues plus quarterly Wayback support-view estimates are in.
Best next sourceAdd full topic and reply history if a stable export is available.
Useful Entry Points
Use the full report for charts, the decision brief for sharing, project load for workload decisions, market position for adoption decisions, contributor depth for participation shape, ecosystem activity for non-ticket community channels, the data inventory when checking source coverage, and the source gap plan when choosing the next import.