Michael Gifford-Santos

Colophon

Two things that are usually left out: where the mark came from, and how the pages are made.

Specification, then artefact

A coat of arms is a spec that outlives its implementation.

A blazon is text — unambiguous, style-free, and older than any drawing of it. Hand the same sentence to ten artists and you get ten shields that are all correct. I have spent fifteen years doing the same thing with software, which is why this is the mark I have used since 2004.

  1. The blazon

    Azure, a chevron argent, in chief a lion passant argent, a canton gules, within a bordure or.

    Formal description. Written once, in the 14th century’s own terms.

  2. As a spec

    field: #30347achevron: #d1d3d4lion: #d1d3d4canton: #bc282ebordure: #fff200

    The same sentence, read as structure. Every clause is a field.

  3. The draught

    Geometry only. Where each charge sits, before any colour is chosen.

  4. The arms

    One implementation of that spec. Mine, drawn in 2004.

What is drawn here is the escutcheon — the shield alone. The complete achievement carries three more clauses: Crest: a mullet of seven points or · Supporters: on the dexter a horse rampant argent, on the sinister a bear rampant proper · Motto: Imaginare, upon an escroll.

Note what is not there: no helm, no compartment, and not a word about where the scroll sits or whether the supporters stand on it. That is the artist’s business, not the blazon’s — and it is exactly the line I try to hold in a spec. Say what must be true; leave the rest to whoever implements it.

How this site is built

There is a humans.txt and an llms.txt, and something in the browser console.