WordPress relevance report progress

This is the working state as of June 14, 2026. The active direction is the WordPress Community & Adoption Health report, not the SQLite benchmark runner. The public report opens with a decision scorecard, a Decision Questions checklist, an Evidence Map, visible data-source strength, a SQLite-generated decision brief, and this SQLite-generated progress summary.

Database

108 tables

SQLite stores imported ticket data, fetched ecosystem data, theme breadth, npm, Packagist, GitHub topic snapshots, job-board snapshots, source hashes, generated summaries, and known source gaps.

Ticket records

97k items

65k Core Trac tickets plus 32k Gutenberg GitHub issues are loaded for quarterly analysis.

Evidence Map

8 rows

Decision-question evidence rows label each answer as direct, mixed, or proxy-backed.

Support archive

135 rows

Quarterly Wayback support-view estimates add rough history beyond the current queue snapshot.

Package signal

21.0M Q2 2026

Tracked @wordpress npm package downloads add developer/package activity beyond help-question volume.

Known gaps

5 of 5 partial

Remaining ideal sources are true new-site history, search-provider data, broad hiring demand, full support topic/reply history, and another stable developer-community source.

Relevance scorecard Short decision view: still in a good place, with softer momentum. Decision Questions Seven plain-English answers mapped to the exact questions from goal.md. Evidence Map Decision answers labeled as direct, mixed, or proxy-backed, with next-source guidance. Goal coverage map Separates strong quarterly evidence from snapshots and proxies. Project load Compact flow, backlog age, response, closure, and category readout. Contributor depth Drive-by, repeat, regular, and sustained participation readout. Market position Installed-share, current new-site proxy, runtime context, and demand direction readout. New-site choice Current newly found-site, recurring crawl, and traffic-tier readout. Developer interest Help-seeking, public attention, npm and Packagist packages, GitHub topic breadth, hiring proxies, PR flow, and review-comment activity. Search interest Wikimedia pageviews, Stack Overflow questions, and autocomplete query-intent snapshots. Job demand HN hiring mentions, Remote OK and Remotive current jobs, quarterly WordPress Jobs snapshots, and jobs-board categories. Ecosystem activity Non-ticket community channels, plugin and theme breadth, and current ecosystem snapshots. Support load Current support queues, archive estimates, age buckets, and major-plugin support counts. Decision brief SQLite-generated one-page summary for quick sharing and review. Goal audit Maps goal.md requirements to report sections, evidence, and source gaps. Data inventory SQLite tables, source hashes, and partial-source gaps. Source gap plan Visual collection order for the five remaining partial signals. Refresh runbook How to refresh safely, including low-disk constraints.

What has been done

Plan

Wrote goal.md: a visual report on WordPress participation, project load, and market position.

Tickets

Built quarterly Core Trac and Gutenberg GitHub metrics for new/closed flow, backlog, reporters, first-time reporters, newcomer return cohorts, bug/feature mix, response time, closure time, stale share, and contributor concentration.

Classification

Loaded bug, feature request, documentation, support, and other classification outputs into the SQLite-backed pipeline.

Ecosystem

Added Core release credits and committers, Make/Core posts and comments, dev notes, WordCamps, events, translation snapshots, Five for the Future, support snapshots, archived support-view estimates, plugin/theme directory samples, plugin and theme search breadth, major plugin stats, and enterprise case studies.

Adoption

Added W3Techs, HTTP Archive, BuiltWith, WordPress.org runtime stats, Stack Overflow, Wikimedia, autocomplete query-intent snapshots, Packagist Composer package snapshots, GitHub topic-search breadth, Hacker News hiring threads, Remote OK and Remotive current jobs, annual and quarterly WordPress Jobs snapshots, compact new-site summaries, and attention/demand proxy summaries.

Companions
Decision brief

Added make_decision_brief.py so installed share, current new-site proxy, closure ratios, first-time reporter retention, backlog age, contributor concentration, npm package downloads, and theme sample counts regenerate from SQLite.

Evidence map

Added decision_question_evidence, a SQLite-backed map that labels each decision answer as direct, mixed, or proxy-backed evidence.

Progress summary

Added make_progress_summary.py so this progress page is regenerated from SQLite counts and the current report artifact list.

Refresh

Updated refresh_report_artifacts.py so the main report, focused companion pages, generated decision brief, generated progress summary, source gap plan, goal audit, and data inventory can be rebuilt and validated in order.

Publishing

Published the GitHub Pages report as index.html, with community_health.sqlite.gz for the supporting database export.

Current report coverage

Strong local evidence

  • Quarterly Core Trac history since 2003.
  • Quarterly Gutenberg GitHub issue history.
  • Bug vs feature request trends for Core and Gutenberg.
  • Contributor concentration, first-time vs repeat reporters, and maintainer participation.
  • Top-level evidence lanes, an Evidence Map, and a visual decision readout with direct answers to the seven goal questions.
community_health.sqlite final_report.html index.html community_health.sqlite.gz Decision Questions Evidence Map decision_question_evidence make_decision_brief.py make_progress_summary.py scorecard coverage map project load market position contributor depth ecosystem activity goal audit data inventory
Ticket participation Implemented with quarterly charts.
Project load Implemented with flow, backlog, response, closure, reopen, and age charts.
Market position Implemented with all-site/CMS share, HTTP Archive, BuiltWith, traffic tiers, competitor signals, and compact demand summaries.
Decision evidence 8 Evidence Map rows stored in SQLite.
Refreshability Generated companion pages, source metadata, source gaps, and a compressed database export.

Goal coverage checklist

This maps the current artifacts back to goal.md. Items marked partial are present in the report, but rely on proxies or snapshots rather than the ideal broad historical source.

Covered Three report views

Participation, Project Load, and Market Position sections in index.html.

Covered Ticket-derived participation and load

Quarterly Core Trac, Gutenberg, and wordpress-develop PR charts for flow, reporters, newcomer return cohorts, response, closure, reopen, stale share, and concentration.

Covered Bug, feature request, and all-ticket views

Separate Core and Gutenberg line charts plus open-backlog category summaries.

Covered with snapshots Community outside tickets

Release credits, committers, Make/Core, WordCamp, Events, Translate, Five for the Future, support snapshots, archived support-view estimates, plugin/theme directory, plugin and theme search breadth, stale popular plugins, and enterprise case studies.

Covered with proxies for new-site and demand history Market position and adoption

W3Techs installed share, HTTP Archive origin and tracked-share trends, BuiltWith pipeline/tier data, plugin install/download history, WooCommerce, and compact new-site plus attention/demand proxy summaries.

Covered Decision questions

Seven plain-English answer cards plus the Evidence Map backed by decision_question_evidence.

Covered Short visual decision readout

Relevance Scorecard, Evidence Map, Goal Coverage Map, generated Decision Brief, and final Decision Readout.

Covered Refresh metadata

SQLite source hashes, source_gaps, generated data inventory, generated decision brief, generated progress summary, generator scripts, cached public-source tables, and compressed DB export.

Partial by design Remaining ideal sources

True multi-year new-site cohorts, Google Trends or equivalent, multi-year labor-market exports, full support topic/reply history, and another developer-community source if a stable public source is available.

Next report work

The next useful work is to deepen the partial-source areas. The current report labels those areas as proxies or partial coverage, and the source gap plan records the target tables.

Next: true new-site history Next: search-interest data Next: broader hiring demand Later: full support topic/reply export Decision brief Source gap plan Refresh runbook
Developer interest 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 source Add another stable developer-community source if available.
Hiring demand HN hiring threads, Remote OK and Remotive current jobs, and annual plus quarterly WordPress Jobs board snapshots are in. Best next source Add a broad hiring-platform export.
New-site history BuiltWith current pipeline and HTTP Archive proxies are in. Best next source Add a true first-seen site cohort.
Search interest Wikimedia, Stack Overflow, and current autocomplete query-intent proxies are in. Best next source Add Google Trends or a similar search-provider export.
Support history Current support queues plus quarterly Wayback support-view estimates are in. Best next source Add full topic and reply history if a stable export is available.
Ticket history96%
Ecosystem snapshots76%
Market share history72%
New-site choice48%
Hiring and search interest44%

Disk is currently very tight, so the next data pull should either free local cache space first or import one source at a time and checkpoint SQLite after each refresh.