The image standard, enforced in code

A ten-step standing order for every image the product publishes — aspect ratio, required alt text, SEO filename derived from that alt text, 1000px maximum, WebP, hosted upload — written as a function nobody can partly follow.

What it is

Every image destined for the website, the blog or a jobsite record passes through one pipeline. Placement decides the aspect ratio and purpose. Alt text is required and checked for specificity rather than generic filler. The filename is generated from the alt text as an SEO slug. Output is capped at 1000px on the long edge, encoded as WebP, and uploaded to the hosted media library, returning the hosted URL.

Also called: image standards · web images · alt text · compress images · photo naming

See it
The image standard, enforced in code
Area
Operations
Group
Media & Images
Scope
Stands on its own
Solves
3 named problems
01Choose the placement (blog hero, blog thumb, site hero, site section, site card, stage photo, checkpoint proof, note photo) — that fixes purpose and aspect
02Supply alt text; specificity is asserted, not assumed
03The filename is derived from the alt text as a slug
The ten numbered steps as a flow, with a real example: alt text → slug filename → 1000px WebP → hosted URL — imagePipeline.ts. Sample data — no customer information appears here.
How it works
  1. 1Choose the placement (blog hero, blog thumb, site hero, site section, site card, stage photo, checkpoint proof, note photo) — that fixes purpose and aspect
  2. 2Supply alt text; specificity is asserted, not assumed
  3. 3The filename is derived from the alt text as a slug
  4. 4Optimise: 1000px maximum edge, WebP encode
  5. 5Publish into a foldered media library and return the hosted URL
Why we built it

Images published by a business drift the moment the standard lives in a document: someone skips the alt text, someone else uploads a photo straight off a phone, and the page meant to sell a barn takes six seconds to load on a truck's connection. The ten-step standard runs as a single step in the software instead, so nobody can follow eight parts of it and quietly skip the other two — the shape is enforced, alt text is required and becomes the filename, and everything comes out web-sized in a modern format before it is hosted. A long-standing belief here, that the media host refused the smaller format, turned out to be false the first time anyone tested it against the live service; correcting that took roughly a third off the weight of every image the product publishes.

The problem
  • Image standards written as a document get partly followed
  • Unnamed, uncompressed images hurt page speed and search
  • Images composed for the wrong ratio get cropped badly by the layout
Sound familiar?
What you get
Every published image is compressed, correctly sized and correctly named
Alt text exists for every image because the pipeline refuses to run without it
Roughly 25-35% smaller files than the previous JPEG rule

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →