AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

Buying for a business?Offer from Amazon

Get business pricing on monitors, keyboards and dev gear

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

Brennen Puth published a post arguing that websites, especially text-focused ones, should be designed to print legibly. He shared CSS changes for print-specific typography, links and page elements, then said feedback prompted him to simplify the stylesheet; the post reached the front pages of Hacker News and Lobsters, according to Puth.

Software developer Brennen Puth published an essay on October 24 arguing that websites should be designed to work on paper as well as on screens, after finding that printing his own site produced oversized text, an unattractive header and links that were hard to distinguish in grayscale. In an October 26 update, he said feedback from readers on Hacker News and Lobsters had led him to simplify his print stylesheet.

Puth said he reads printed papers because marking up a physical document helps him engage with the material. He tested his site using a browser’s print command and found that the result was technically readable but poorly suited to a printed page. The experience prompted him to use CSS rules that apply specifically when a page is printed.

His example stylesheet hides elements marked “noPrint”, shows elements marked “onlyPrint”, sets body text to 12-point type and uses larger sizes for headings. It also changes links to black so they remain legible in monochrome printing and adjusts the appearance of code blocks. Puth said he uses the print-only option to add a short author attribution and removes his website header from the paper version.

He also described a problem he had not solved: code blocks can be awkward to print because they may stay together as a single block rather than break naturally across pages. Puth invited readers to suggest a fix. He said on October 26 that he was simplifying the stylesheet after receiving feedback, but did not detail every change in the update supplied with the post.

At a glance
reportWhen: Published October 24, 2026; updated Oct…
The developmentBrennen Puth published a practical argument for making websites more readable on paper, and later updated it after online feedback.

Paper Access for Text-Heavy Sites

The post makes a modest but practical case for print accessibility: people may prefer paper for reading, annotation or working away from a screen, and a browser’s default print output may not preserve a site’s layout or readability. Print-specific styling can remove navigation and other screen-oriented elements while keeping the main text usable.

Puth acknowledged that relatively few visitors may print a given webpage and that preparing a print layout took him a substantial part of a morning, even though his site was not complex. His argument is not that every site needs an elaborate redesign. Rather, for websites made largely of text, he says supporting paper is a small consideration that can give readers another way to use the content.

Products Worth Considering

Bose Lifestyle Ultra Wireless Soundbar with Dolby Atmos, Black

Bose Lifestyle Ultra Wireless Soundbar with Dolby Atmos, Black

Logitech MX Master 4 for Mac Wireless Ergonomic Mouse, White Silver

Logitech MX Master 4 for Mac Wireless Ergonomic Mouse, White Silver

Amazon Kindle Paperwhite (2024, 12th Generation), 16 GB, 7-Inch Display, Black

Amazon Kindle Paperwhite (2024, 12th Generation), 16 GB, 7-Inch Display, Black

As an affiliate, we earn on qualifying purchases.

From Browser Print to CSS

Web browsers provide a print command, commonly accessed with Ctrl-P, but the resulting page depends on both the webpage’s styling and the printer setup. Puth’s first test showed that having all the content appear on paper does not necessarily mean it is comfortable to read: his text was too large, the header did not suit the page, and link colors lost contrast in black and white.

CSS supports print-specific styling through print media rules. Puth used those rules to change font sizes and colors and to control which elements appear in print. The post offers a working example rather than a formal standard or a claim that one set of settings will suit every website. Its code-block issue also highlights a trade-off: print layouts must handle content that does not fit neatly within page boundaries.

Puth’s October 26 update said the essay had appeared on the front pages of Hacker News and Lobsters after he submitted it. He wrote that readers on those sites and a friend had pointed out things he had missed, and that he was simplifying the stylesheet in response.

“I would personally love to experience more webpages that think about how printing works.”

— Brennen Puth

Print Layout Problems Remain

The post does not establish how many people print webpages, how often visitors use Puth’s print styles or whether the changes improved the experience for readers beyond his own tests. His comment that he might be the only one who regularly prints webpages is a personal observation, not usage data.

It is also unclear from the supplied update exactly which stylesheet choices Puth changed after receiving feedback. He identified code blocks breaking across page boundaries as an unresolved difficulty and asked readers for suggestions. The article does not report a final solution or present a broader evaluation of print behavior across browsers and printers.

Revisions and Reader Feedback

Puth said he was simplifying his print stylesheet after comments on Hacker News and Lobsters, but gave no timetable for completing those changes. Readers can test the print view using the browser’s print command, though results may differ by browser, printer settings and page content.

The next development described in the source is Puth’s ongoing revision and any further reader suggestions, particularly for code blocks. The post does not announce a formal project, product release or industry-wide change.

Key Questions

What did Brennen Puth argue?

He argued that websites should account for readers who want to print them, especially when the site mainly contains text. His essay describes changes he made to improve his own site’s print layout.

What CSS changes did he demonstrate?

Puth showed print-specific rules to hide screen-oriented elements, show print-only content, set text and heading sizes, change links to black and adjust code-block styling.

What remained difficult to print?

Puth said code blocks were still awkward because they tend to print as one chunk and may not break cleanly across page boundaries. He asked readers for suggestions.

Did Puth revise the stylesheet?

In an October 26 update, he said feedback from readers on Hacker News and Lobsters had led him to simplify the stylesheet. The supplied material does not list all the specific revisions.

Does the essay show that many people print webpages?

No. Puth discusses his own reading habits and says he doubts many people regularly print webpages. The post provides no audience or usage data.

Source: brennenputh.me

You May Also Like

How Pickleball Video Analysis Can Support Player Ratings

A proposed pickleball app would replay rallies, tag shots and track skill metrics. Its value depends on testing use and paid subscriptions at three clubs.

X agrees to crack down on illegal hate and terror content in the UK

Ofcom confirms X has accepted new commitments to better address illegal hate and terror content in the UK, including content removal and reporting targets.

The Eye Over The City: How Wide-Area Motion Imagery Works — And Where It Goes Blind

An in-depth analysis of WAMI technology, its capabilities, limitations, and future directions in city surveillance and military operations.

The Real Price Of Free AI: More Than Just Money

Exploring how abundant AI shifts value away from models to physical infrastructure and human judgment, impacting sovereignty and economic dynamics.