Changelog

Every change to this site that affects what a page claims, newest first. Entries are dated. The method behind the numbers is on the methodology page; mistakes that were corrected are recorded on corrections.

2026-11-02 — Trust pages, dated claims, six-link footer

Changed: added /changelog, /corrections, /examples and /tattoo-size-chart. Every guide now opens with a dated Last verified line, the sources that page was checked against and a link to report an error. Every page footer now carries About, Methodology, Changelog, Privacy, Terms and Contact. /about and /privacy now state the same image-retention window.

Why: a date and a named source let a reader judge a claim without trusting the site; the two trust pages previously disagreed by omission on how long a design is kept.

2026-10-30 — Photo check shipped (/photo-check)

Changed: an in-browser check for resolution, contrast, background clutter and subject-in-frame size, run on a 256 px copy of the image. No upload; the arithmetic lives in js/photo-check.js.

Why: most conversions that disappoint are photo problems rather than style problems, and people were paying before anyone told them the file was too small or too flat.

2026-10-30 — Artist handoff checks (/tattooer-handoff)

Changed: the seven checks a design should pass before it goes to an artist, plus a sources table of six artist and supplier guides, each read and dated 2026-10-30.

Why: a file that fails at the artist’s table costs a consultation and a deposit; the page names the failure in advance.

2026-10-30 — Photo privacy walkthrough (/photo-privacy)

Changed: a code-level trace of what leaves the browser, which browser keys are written, and the published three-day design cache. The page links each claim to the request or file it comes from.

Why: “we delete it” is not checkable. The walkthrough is the version a reader can audit.

2026-10-30 — Local tree re-synced to the live site

Changed: every page was re-synced from the live site (eleven had been behind) along with both JS files; 38 of 43 HTML files then matched live byte-for-byte, and three sitemap entries were added. At that point the sitemap listed 44 URLs.

Why: edits were being made against copies that were behind the deployed pages, which is how a fix silently reverts.

2026-10-29 — Homepage schema rebuilt as one graph

Changed: the homepage JSON-LD became a single @graph with Organization, WebSite and WebApplication nodes and stable @id values.

Why: three anonymous blocks describing one site is harder to reconcile than one graph with references between the nodes.

2026-10-29 — Favicon fix

Changed: a real multi-size favicon.ico was added, with a 32×32 icon link alongside the SVG favicon.

Why: an .ico is what older browsers, feed readers and some crawlers request; the SVG alone did not cover that.

2026-10-29 — Hero states the offer without an account

Changed: the homepage hero now says the included preview needs no account and no sign-up.

Why: the trial terms were only in the FAQ, so the first screen read as a paid product.

2026-10-29 — scripts/ci.sh added

Changed: a static-site CI script that checks sitemap coverage, one H1 and a canonical per page, JSON-LD that parses, a real ICO signature and every internal link.

Why: a static site has no build step to fail, so the checks have to be run on purpose.

What belongs here

Entries are for changes a reader could act on: a claim, a number, a page, a method. Spelling and layout tweaks are not logged. When a change also corrects something the site got wrong, the record with evidence goes on /corrections as well.

Next: about the site · how we test · pipeline examples