A print grid holds everything in fixed relationship. Every element has a position, a size, and a spatial relationship to every other element on the page. The designer controls exactly what the reader sees. A web flow lets elements reorder, reflow, collapse. The designer suggests an arrangement, and the browser interprets it based on the viewport.

Same content. Different container. Different world.

I made the transition from print to web in the middle of my career, and the difference in control was the first thing I felt. In the catalog work at Sterling, I could place a title 14 picas from the left margin and know it would be 14 picas from the left margin for every person who opened that page. The relationship between the title and the image below it was fixed. The negative space between columns was fixed. The entire composition was a single, resolved object.

On the web, that title sits wherever the browser puts it. A narrow viewport stacks the columns. A wide one stretches them. The image might load after the text. The user might increase their font size. Every fixed relationship I designed in print becomes a suggestion in the browser.

The fidelity question hits hard here. The intent behind a print layout is embedded in the object. The intent behind a web layout has to survive translation across hundreds of different viewports, font rendering engines, and user settings. The accommodation question becomes: what does this medium actually need to preserve the intent?

With Encore, I spent twelve years solving this for a complex enterprise application. Recruiting workflows that originally lived in a Windows Forms desktop application, where every pixel was controlled, had to move to the browser. The data density was extreme. Forms with forty fields, tables with twenty columns, dashboards with six panels. Each screen was a resolved print layout in the original version. Moving it to the browser meant deciding what to preserve and what to let go.

The answer was never “make it look the same.” The answer was “identify what the layout is actually doing and find the web-native way to do the same job.” A forty-field form in a fixed window uses spatial grouping to communicate hierarchy. On the web, that same spatial grouping might need progressive disclosure, collapsible sections, or responsive reflow. The grouping serves the same cognitive function. The implementation changes because the container changed.

I still think in print grids. My SCSS architecture uses design tokens that approximate print logic: fixed spacing increments, consistent margins, modular type scales. The Chainprinter heading face on this site is a print instinct applied to the web. The paper grain texture is a print artifact translated to a digital surface.

But I know where the translation fails. Print authority comes from resolution and precision. Web authority comes from responsiveness and accommodation. A print design that doesn’t accommodate the viewer is elegant. A web design that doesn’t accommodate the viewer is broken. The medium changed the rules.

The instincts from print (spatial hierarchy, information density, compositional rigor) transfer. The assumptions about control don’t. My career is the bridge between those two worlds, and the gap between them taught me more about fidelity than any single project did.