Skip to content

Phase 4: Build Public Metrics Dashboard #936

Description

@ckenst

Overview

Build a public-facing page to visualize project health and transparency to the community. This dashboard will surface key metrics collected during Phase 2 and provide insights into site quality, growth, and maintenance status.

Goals

  • Create a /stats or /quality page to display project health metrics
  • Visualize key indicators: Lighthouse scores, broken link counts, build times, conference growth
  • Make metrics accessible and easy to understand for both contributors and visitors
  • Establish testingconferences.org as a transparent, well-maintained project

Implementation Notes

  • Determine dashboard location (/stats, /quality, or alternative)
  • Design page layout with clear sections for each metric type
  • Reference _data/quality_log.yml (or equivalent) populated by Phase 2 work
  • Consider Jekyll plugin or JavaScript approach for rendering metrics
  • Include:
    • Current site version
    • Build status
    • Latest Lighthouse scores
    • Recent broken link status
    • Conference count trends
  • Make the dashboard update automatically with each release
  • Ensure accessibility (WCAG compliance)
  • Keep loading performance good (no heavy JavaScript)

Related

  • Part of Phase 4: Public Quality Dashboard
  • Depends on: Phase 2 completion (Quality Ledger & Metrics)
  • Complements: Trend Visualization issue

Acceptance Criteria

  • Dashboard page is created at agreed-upon URL
  • At least 5 key metrics are displayed
  • Metrics update automatically on release
  • Page is accessible and performant
  • Documentation explains how to maintain/update the dashboard
  • Dashboard integrates with _data/quality_log.yml

Resources

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions