Heron runs inside Revit, Rhino, ArchiCAD and SketchUp, so the site had to read as an instrument rather than a brochure from the first frame.

The preloader replaces the progress bar with a drawing in progress. A red datum line moves up an architectural elevation carrying the percentage value, and the building is drawn in line by line as loading completes. Supporting information sits in the margins in the same register: live cursor coordinates, a project spec card covering type, founding year, focus and location, and a numbered system boot sequence.

Functionally it covers asset loading for the interactive hero, so the drag-to-reveal behaviour responds immediately once the page lands. Editorially it sets the frame before a single line of marketing copy appears.

The 404 was treated as a proper page rather than a fallback state.

The number is constructed as an architectural drawing. The 4 and the 0 are formed from walls at true thickness, with furniture laid out inside the resulting rooms and dimension strings running along both edges. It sits inside the same drafting system as the rest of the site rather than borrowing a display typeface.

The error message then repeats. Instead of a single dialog, identical windows cascade back across the canvas, each one carrying the same 404 notice. It reads as a system throwing an unresolved warning over and over, which is the exact behaviour Heron is built to prevent inside a model.

Error pages are never in the brief. They're a good measure of whether a team understood the product or just styled it.

Treating a 404 as an actual page instead of a dead end is such a good instinct, where did the architectural drawing idea come from, personal interest bleeding into the work?