On Sunday, May 10, the team shipped Comic #1 to production. The URL is potatuhs.com/comic/1. The title is The Garbage Collection. The format is twelve frames of snap-scroll narrative, lightbox-enabled, keyboard-navigated, swipeable on mobile. The story is office life inside Potatuhs Inc., featuring characters customers have only ever seen as static portraits on the org chart. This is the first time the storefront has sold a story before — or alongside — selling a product.

The technical scaffolding is built to scale. The route is /comic/:number, which means Comic #2 lives at /comic/2 the moment its assets exist. The reader component is generic. It takes a frame manifest and renders the snap-scroll experience. The lightbox handles full-bleed viewing without leaving the page. Keyboard navigation is left-arrow / right-arrow. Mobile swipe is detection-based and works on any phone. The plumbing was the work; the content is the product.

What makes this interesting at a brand level is that the comic does not interrupt the storefront. A customer browsing hoodies can click into the comic and read it without being pulled into a separate funnel. The cart persists. The checkout works. The product pages load. The comic is content adjacent to commerce, not content instead of commerce. The Shopify Hydrogen surface, which is ostensibly an e-commerce framework, is now hosting episodic narrative. That is a configuration most brands do not attempt.

The /comic/:number route reads a frame manifest. The manifest is a JSON file that describes the frames, their assets, their order, and their metadata. The reader component does not care about which comic it is rendering. It accepts the manifest, the comic appears. This means Comic #2 is, from an engineering perspective, a content-only ship. The next twelve comics land without touching the reader code.

The lightbox merits a paragraph of its own. It is keyboard-accessible, ARIA-tagged, and dismisses on escape. It does not navigate the user away from the storefront. It does not blow open a modal that breaks the back button. It is the kind of feature that, when working correctly, is invisible — and that is the only way to ship a comic reader inside an e-commerce surface without losing customers to friction. The Hydrogen integration respects the host. That is the design discipline.

Behind the reader, the storefront also gained an API layer this week: /api/v1/products, /api/v1/collections, /api/v1/search. These routes expose the storefront's catalog state to other surfaces inside the company. Potatocore can read it. The Press can read it. The design system can read it. The storefront stopped being only an endpoint for customers and became a source for the rest of the company. The comic lives on the same surface, and any internal consumer can read both.

The brand implication of Comic #1 is more significant than the engineering. potatuhs.com was a storefront. As of this week, it is also a publishing surface. The distinction matters because publishers have return readers in a way that storefronts do not. A customer buys a hoodie once a year. A customer reads a comic when the next one drops. The comic format gives the brand a reason to bring customers back without an offer.

This is the answer to a problem the company has been quietly working on for months: how to keep the storefront in customers' lives between purchases. Email lists work. Loyalty programs work. But neither feels like Potatuhs. The comic feels like Potatuhs. It is silly, it is structured, it features the same characters customers are buying merch of, and it lives on the same domain. There is no friction. There is no separate destination. The brand stays in one place and grows new dimensions inside it.

What this means operationally is that the storefront now needs an editorial calendar. Comic #2 needs a date. Comic #3 needs a date. The Diamonds quarterly spotlight needs to coincide with a comic release. The publications arm, freshly led by Tater starting late this month, will own that calendar. The storefront is the surface. The publications arm is the cadence. The customer sees one site, behind one logo, telling one ongoing story while it sells them merchandise. That is the configuration the brand has been quietly building toward.

While the storefront was getting its comic system, potatuhs-studio — the production arm that handles video and animation — was quietly experimenting. Two commits on Wednesday May 13 and Friday May 15. The commit messages were 'decent video' and 'ignore,' both of which are diagnostic. The team was iterating on something visual without yet declaring what it was. The work was real, the output was private, the artifact was a candidate.

Production work like this is the kind of activity that does not show up in customer-visible reports until it does. Most weeks, the studio is invisible by design. The team is rendering, retiming, color-grading, cutting. When the studio surfaces, it surfaces with a finished piece. The two commits this week are a signal that one of those finished pieces is in progress. The Tater Times will report it when it ships.

The pattern of having both extremely visible launches (the comic) and extremely quiet experimentation (the studio) in the same week is the operating shape this company is finding. Customer-facing surfaces get loud. Production surfaces stay quiet until they have something to say. The weekly brief reports both, because the absence of visible activity is content too, and the studio's 'decent video' commit will eventually mean something the customer sees.