How every grid in the catalogue gets built, sourced, and verified.

Each of the 82 overlays in Grid Maker Pro is implemented as a Canvas 2D drawing routine in the hero tool's JavaScript. The geometry is derived directly from canonical sources: Euclid for the Phi rectangle, Hambidge's The Elements of Dynamic Symmetry (1926) for the root rectangles, Loomis's Drawing the Head and Hands (1956) for the head construction, Material Design spec (2014) for the 8pt and icon-keyline systems, ISO 216 (1975) for the Root 2 paper grid, and so on.

Where a published source defines the geometry exactly, the overlay matches it exactly. Where the geometry is interpretive, we follow the published diagrams as the reference. Where the overlay would produce a visually wrong result if we simplified the math, we use the full math.

Verified on reference material

A Loomis construction is drawn over a photograph of a head and checked by eye and ruler. A golden rectangle is verified against a 1:phi proportion calculated to four decimal places. Hexagonal grid spacing is verified against tabletop miniature bases.

Each long-form pillar guide carries at least 4-6 in-text citations to canonical sources. Citations are included when they help the reader verify a method, trace a historical claim, or understand why the overlay is drawn that way.

Where historical claims are contested, including the Hockney-Falco thesis, dynamic symmetry as Greek practice, or the golden-ratio Parthenon attribution, we flag the debate openly rather than pick a side.

Bulk content sites fail in predictable ways when pages start to look like each other. Grid Maker Pro prevents that with page-level checks before publication.

Tier-B leaves are 900+ words excluding nav and footer. Tier-C leaves are 600+ words. Every leaf has at least 3 outbound internal links with descriptive anchor text and a self-canonical URL.

Every page ships JSON-LD structured data appropriate to its page type. Overlay leaves use Article, BreadcrumbList, FAQPage, and WebApplication references, with HowTo added when the page documents a step-by-step technique. Category hubs use CollectionPage and ItemList. Pillar guides use Article, Author Person, FAQPage, BreadcrumbList, speakable, and citation data. Author pages use Person with sameAs, alumniOf, jobTitle, and knowsAbout.

Schema validation is run via Google's Rich Results Test and Schema.org's official validator across the full sitemap before any batch ships. Any page with errors or more than two warnings is fixed before publish.

Every page is built on the same shared content system with no per-page JavaScript unless a feature genuinely needs it. The performance target on every page is mobile and desktop PageSpeed Insights 90 or higher, with Core Web Vitals green. The hero tool's Canvas workflow is optimized separately with preloaded canvas dimensions to prevent layout shift.

If we get something wrong - a historical claim that turns out to be unsupported, a citation that misattributes, or a math error in an overlay implementation - we want to know. Email sarah@gridmakerpro.com with a specific reference and your source, and we will correct the page within a week. Substantive corrections are noted in the changelog; minor typos or copy edits are silent.

Every page carries a last updated date. When a page is materially refreshed, the date is updated and the change shows in the changelog. Refresh cadence: Tier-S landings every 4 months, Tier-A hubs every 6 months, Tier-B leaves every 9 months, Tier-C leaves on an annual sweep - earlier if a correction comes in.