From Pica Ruler to CSS
Print to digital.
Nobody reads a catalog. They navigate it. At Sterling Publishing, I laid out hundreds of pages of titles, prices, category breaks, seasonal lists. The grid was the navigation system. Get the hierarchy wrong and the reader gives up before they find what they came for.
I didn’t know it was called information architecture. I called it catalog layout. The question was the same: given this density and this limited attention, where does the eye go first? The pica ruler measured the physical space. The decisions about what went where, how large, how much whitespace, those were structural decisions about how a person would process the page.
Years later, when UX became a defined discipline, I recognized the problem immediately. I’d already been solving it with a pica ruler instead of a wireframe tool.
The transfer from print to digital happened in stages. At USA Tees in Brooklyn, I was in the art department doing color separation and production. Halftone screens at specific angles, registration dialed by hand, ink density controlled plate by plate. Separation means you never work on the image. You work on a channel. One color at a time, decomposing a whole into discrete layers that reconstruct it when they register.
That’s the operation I still run on everything. Every SCSS cascade is a plate. Every function chain is a sequence of passes. Every stage in a multi-agent workflow is a channel. The whole only exists when the layers register. I learned that on a press floor, and I carried it into every digital environment I’ve worked in since.
CSS is pica measurement in a different medium. The Sovereign Design Engine makes this literal: every CSS value resolves to a fixed measurement in inches or points. Print production doesn’t tolerate ambiguity. Type scale is phi-derived (base 7pt, ratio 1.618). Spacing follows the same ratio from a quarter-inch base. Templates inherit both, so visual relationships stay consistent across different page sizes.
That level of precision comes from print training. A web developer who learned CSS first thinks in relative units and viewport fractions. I think in points and inches and then translate. The underlying question is always physical: if this were a printed page, would the hierarchy hold? Would the eye move where it needs to? Would the information survive the density?
PressWorks closes the loop. I spent twenty years in Adobe doing the plate-by-plate work digitally. Then my brain stopped matching the interface. I still think in plates and passes and registration offsets. I just stopped thinking in Adobe’s UI. So I built a press that runs from the terminal. CMYK separation, halftone screening at specific frequencies, misregistration per channel, grain, all of it parameterized in a bash script wrapping ImageMagick.
Every texture on this site came through PressWorks. The grain, the halftone, the desaturated color. The same plate-by-plate logic a physical shop uses, running in code instead of on a Heidelberg. Print to digital to code to print again, through a pipeline that I control end to end.
The pica ruler is gone. The thinking it trained never left.