logged
The Ancient Measures Test Lab separates trials from accepted work
A generated Test Lab index distinguishes ideas and working demonstrations from changes accepted for the main site.
Read the entryTechnical history
23 entries · Updated
How ancientmeasures.com is planned, built, verified and maintained. The Case Studies cover ancient measurement; this log covers the engineering. Entries follow the documented project history, newest first.
logged
A generated Test Lab index distinguishes ideas and working demonstrations from changes accepted for the main site.
Read the entrylogged
Links from pyramid articles open the calculator with the same monument selected. The navigation check covers the homepage and all eight pyramid presets.
Read the entrylogged
The editorial review now tests whether an article asks a worthwhile, supportable question before extending it, and keeps evidence, original analysis and graphic approval separate.
Read the entrylogged
Semantic progress classes and a full-tree CSS check now keep generated pages within the shared style system; unchanged renders verify the extraction of legacy styles.
Read the entrylogged
Specific passage requirements now govern research readiness, so generic catalogue matches cannot release a blocked study or put it next in the queue.
Read the entrylogged
A generated public report now ties every research commission, publication milestone and source holding to the same checked queue as the progress displays.
Read the entrylogged
Three instrument plates now show the article programme page by page: a pyramid of 233 stones, a dial for temples and measuring rods for units.
Read the entrylogged
The homepage now directs visitors from six converters to a preserved pyramid diagram, a rotating unit dossier, focused studies, and the latest build-log entries.
Read the entrylogged
A typography release is complete only when its character scope, fallback metrics, responsive rendering, cache key, and public requests all pass together.
Read the entrylogged
A build log earns its place by showing what changed, why it changed, and what was checked; it is not a second home for ancient-history essays.
Read the entrylogged
A successful HTTP response can still be a fallback document; route checks must confirm the page’s identity, not merely its status code.
Read the entrylogged
A relative asset path in a nested converter can resolve to an HTML fallback; the fix is to correct the depth and verify every sibling tool.
Read the entrylogged
When an immutable JavaScript asset remains cached after a correct deploy, the HTML reference needs a new version key and the public route needs a later check.
Read the entrylogged
The Study Library became a connected information architecture: named collections, stable routes, redirects, and a navigation system that exposes the research surface.
Read the entrylogged
When card badges needed clearance, the correction was a scoped shared rule across the library, not a series of hand-positioned exceptions.
Read the entrylogged
Renaming a case study or consolidating a page changes labels, not the obligation to preserve its address and the reader’s path to it.
Read the entrylogged
Topical essays moved to Articles, while the blog address became the technical build log.
Read the entrylogged
Version 5 changed no tools and no essays; it changed who visibly answers for them.
Read the entrylogged
The pyramid tool stopped asking users to type dimensions and began offering documented monuments.
Read the entrylogged
The site took its name and domain, then made unit dossiers account for their sources or gaps.
Read the entrylogged
One converter became five tools and 189 standards with the source register reconciled.
Read the entrylogged
Version 1 was built, frozen, and staged; version 2 hardened it before midnight.
Read the entrylogged
The scaffold came first: a brief, palette, port band, and fact-versus-interpretation spine.
Read the entryReturn to the field guide · Open the converter · Audit the sources