Skip to content

Start typing to search

Colophon: How This Site Is Built

What PingEverything runs on, the checks every build must pass before anything goes live, how analytics and ads are kept in their place, and what we skip.

Last updated

The one rule

Every page should work for a reader on a slow phone, in either theme, without a script they did not need. The rest of this page is how that rule is kept.

What the site stands on

  • Static pages. The site is generated with Astro. Every page is plain HTML, built ahead of time; there is no client-side framework. The few interactive parts (theme switch, table of contents, search, cookie panel, code copy buttons, FAQ answers) are small scripts.
  • Styling. Tailwind CSS, with every colour defined as a named token, so both themes are checked the same way.
  • Hosting. Vercel.
  • Search. Pagefind. The index is built together with the site and searched in your browser against files on this domain; no search service sees what you type.
  • Type. Headings use Space Grotesk, served from this domain. Body text uses your system’s own font. There is no third-party font service.

The exact versions in use are listed on the site facts page, generated from the site itself.

Two themes, dark first

Dark is the default. Light is a choice you make with the switch, and your browser remembers it. Your operating system’s colour preference is deliberately not read. Text colours are set separately for each theme so that contrast holds in both.

Checks that run before anything goes live

Every build runs a chain of checks, and any one of them stops publication:

  • Links. Broken internal links, in-page anchors that point nowhere, links that cross into another language without declaring it, and missing preview images.
  • Structure. Every article belongs to exactly one topic guide, links to that guide from its opening, is linked from the guide in turn, and ends with exactly one “continue” block.
  • Text. Hidden control characters, and the spacing French punctuation requires.
  • Security headers. A Content Security Policy built from the exact scripts the pages contain.
  • Legal. The legal notice must be complete.

Browser tests then check accessibility with axe in both themes, the interactive parts, and advertising density.

Speed

Without ads, every page type scores 100 in Lighthouse on mobile and desktop in local measurement. The numbers, and how they were measured, are on the site facts page.

Analytics and advertising

Analytics (Google Analytics 4) runs only on this domain and only after your first interaction with the page, with consent defaulting to denied: nothing is stored for measurement or advertising until you agree in the cookie panel. When ads run, each one is labelled and keeps a reserved space so the page does not jump while it loads. The details are in the privacy policy and the cookie policy.

What we deliberately do not do

  • No comments, newsletter pop-ups, lead forms or sales funnels. The site is funded by advertising only.
  • No client-side framework, and no third-party font or icon service.
  • No automatic switching between themes.

Security

If you have found a vulnerability, the security page explains how to report it. The machine-readable contact file is at /.well-known/security.txt.

Found a mistake?

Please say so on the contact page.