(Do NOT edit manually. Generated automatically)
- Quick start guide
- Visual glossary of the Guardian.com
- How to deploy
- Troubleshooting
- Development tips
- Testing tips
- FAQs
- Incident Response & Triage
- The different applications composing the Guardian website
- Fronts architecture
- Libraries we use
- Archiving
- Architecture principles for CSS
- Javascript
- How to setup and run A/B tests
- What to do when a deployment breaks
- Guardian embeds
- Inline SVGs
- Interactives
- Repressing fronts
- Sprite production
- Template Deduping
- Testing externally on your localhost
- Testing AMIs or provisioning in AWS
- Accessing HTTP access logs for your localhost
- Update configuration in Systems Manager Parameter Store
- Implement Google Analytics
- Overriding default configuration
- Updating the test database
- Working with Google AMP
- Working with emails
- Apply the special report tone
- Tracking components in the Data Lake
- Updating Social Media Overlay Images
- Testing Reader Revenue Components
- Recipe for Breton crêpes
- CSS guideline (out-of-date)
- Javascript guidelines (Out of date)
- Web Font Rendering Test (2013)
- Website benchmark (July 2012)
- Find the correct subdirectory your new documentation file belongs to.
- Every documentation file should be markdown (with .md extension).
- First line of every documentation file should contain its title (used to generated the table of content).
- Store all the images in an
/imagessubfolder in the same directory the document referencing them will be. - Table of content (TOC) is generated automatically with every commit, all changes will be staged accordingly.