guardian/frontend

The Guardian DotCom.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 11th, 2026
Created on May 18th, 2012
Open Issues & Pull Requests: 226 (+0)
GitHub issues: Enabled
Number of forks: 573
Total Stargazers: 5,898 (+0)
Total Subscribers: 196 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 93.5 days
90th percentile: 359.0 days
Tracked items: 238

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Article-A|B-Testing" is answered fastest, typically in about 24 hours, while "Team Candidate: WebX" waits about 7 weeks. 26% of tracked open issues have had no activity in three months. Only 9% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 117
New in 7 days: 7
Closed in 7 days: 5
Avg open age: 243 days
Stale 30+ days: 53
Stale 90+ days: 50

Recent activity

Opened in 7 days: 7
Closed in 7 days: 5
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Headline-A|B-Testing (85)
  • Article-A|B-Testing (43)
  • Team Candidate: WebX (16)
  • Rota (9)
  • Team Candidate: Fronts and Curation (8)
  • Pick me up (7)
  • maintenance (5)
  • feature (4)

Detailed Description

Frontend is a set of Play Framework 2 Scala applications that serves as the backend for the Guardian website frontend.

The project solves the problem of efficiently rendering news content at scale by building JSON responses that feed into a modern rendering service called Dotcom Rendering. Its approach enforces strict performance and architectural constraints: every request must be cacheable with appropriate headers, each request performs only one backend I/O operation, average response times stay below 500ms, and requests exceeding two seconds are terminated. The codebase uses make for client-side asset builds and SBT for the Play Framework backend, with comprehensive documentation covering architecture, setup, deployment, and development practices.

Frontend suits organizations building high-traffic news or content platforms where performance and cacheability are non-negotiable. The strict architectural principles—single I/O per request, aggressive timeout enforcement, mandatory cache headers—make it most appropriate for teams willing to design around these constraints rather than work around them. The project is production-grade, powering theguardian.com itself, and includes detailed setup guides and troubleshooting documentation for new developers.

The project maintains a substantial base of external adopters who report issues regularly, indicating real-world production use beyond the core team. Maintainers typically respond to new issues and pull requests within a few days. Work in the issue tracker centers on A/B testing infrastructure for headlines and articles, along with efforts from the WebX team, suggesting active experimentation and feature development focused on audience engagement and testing capabilities.