Source for theguardian.com
Clone or download
Pull request Compare This branch is 11994 commits behind guardian:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.github
.prbuilds
__mocks__
admin
applications
archive
article
commercial
common
data
dev-build
dev
diagnostics
discussion
docs
facia-press
facia
git-hooks
identity
integrated-tests
nginx
onward
preview
project
prout
rss
sanity-tests/test
sport
static
tools
.babelrc
.editorconfig
.eslintignore
.eslintrc.js
.flowconfig
.gitignore
.nvmrc
.prout.json
.sass-lint.yml
LICENSE
README.md
cla-corporate.txt
cla-individual.txt
makefile
package.json
riff-raff.yaml
sbt
scalastyle-config.xml
setup.sh
variables
webpack.config.atoms.js
webpack.config.dev.js
webpack.config.js
webpack.config.prod.js
yarn.lock

README.md

Gitter

Frontend

The Guardian website frontend.

Frontend is a set of Play Framework 2 Scala applications.

Frontend is built in two parts, using make for the client side asset build and SBT for the Play Framework backend.

Documentation

All documentation notes and useful items can be found in the docs folder.

Core Development Principles (lines in the sand)

These principles apply to all requests on www.theguardian.com and api.nextgen.guardianapps.co.uk (our Ajax URL)

On the server

  • Every request can be cached and has an appropriate Cache-Control header set.
  • Each request may only perform one I/O operation on the backend. (you cannot make two calls to the content API or any other 3rd party)
  • The average response time of any endpoint is less than 500ms.
  • Requests that take longer than two seconds will be terminated.

New developers

Welcome! The best place to start is here

To get set up, please follow the installation guide.

Fixes for common problems can be found here.

Please, read the development tips document to learn about more about development process.

Deploying

Follow the steps described in the How to deploy document.