Problem
The boost_library_usage_dashboard app aggregates data on how Boost C++ libraries are used across open-source GitHub projects, but this analytics data is currently locked inside PostgreSQL with no public-facing visualization layer. The review eval (Section 4) explicitly flags the absence of pre-built visualization as a gap relative to all five competitors (GrimoireLab, DevLake, Augur, DevStats, Cauldron). A GitHub Pages site displaying library usage data would be the project's first public-facing output and the demo artifact for Week 21.
Acceptance Criteria
- A GitHub Pages repository (or
gh-pages branch) exists and is configured with Pages enabled
- The boost-data-collector pipeline exports usage dashboard data (JSON or static HTML) to the Pages repository on a scheduled or triggered basis
- The deployed GitHub Pages site renders Boost library usage data: at minimum, a table or chart showing library-level adoption metrics across scanned GitHub repositories
- The export/push workflow is automated (GitHub Actions) so the dashboard stays current without manual intervention
- The Pages site loads correctly in Chrome and Firefox with no broken assets or empty data states
Problem
The
boost_library_usage_dashboardapp aggregates data on how Boost C++ libraries are used across open-source GitHub projects, but this analytics data is currently locked inside PostgreSQL with no public-facing visualization layer. The review eval (Section 4) explicitly flags the absence of pre-built visualization as a gap relative to all five competitors (GrimoireLab, DevLake, Augur, DevStats, Cauldron). A GitHub Pages site displaying library usage data would be the project's first public-facing output and the demo artifact for Week 21.Acceptance Criteria
gh-pagesbranch) exists and is configured with Pages enabled