Fictional repair study · real WordPress runtime

Make room for every screen.

A reversible responsive CSS patch for a fictional bicycle workshop page. One scoped child theme addresses card overflow, a long reference URL, crowded actions and a wide pricing table.

Explore the viewport comparison

The page shown here is a case-study frontend. The WordPress demo is local and is not hosted with this page.

Actual WordPress fixture after the Tor Viewport responsive child-theme patch, shown at desktop width
After · desktopActual local WordPress capture

Document width

Same fixture, same 375 px viewport. Document width before and after the patch.

Before1111 px
After375 px

375 px viewport · measured locally

A closer look · 375 px

One fixture, two states.

Switch between the real mobile captures. The before state shows the intentionally rigid fixture; the after state shows the scoped repair.

After · 375 px
Actual WordPress fixture after the responsive repair at a 375 pixel viewport
After · 375 px · service cards fit in one column

The repair

Scoped, measured, reversible.

01

Contain the change

The child theme loads after Tor Workshop’s existing stylesheet. Every rule is scoped to .viewport-study; the parent theme files stay untouched.

02

Repair the pressure points

Cards move to a minimum-width-safe grid, long text can break, actions wrap, and the pricing table scrolls within its own frame on narrow screens.

03

Keep rollback simple

Switching back to the parent theme removes the child stylesheet and restores the fixture’s intentional baseline layout.

Verified in local WordPress 375 px · 768 px · 1280 px · parent-theme rollback

No document overflow at 375, 768 or 1280 px after the patch. Switching back to the parent restored the 1111 px baseline at 375 px. The table also responded to keyboard scrolling in the test browser.

Take the source

A small patch you can inspect.

The download contains the child theme, the fictional core-block page fixture, its intentionally broken baseline stylesheet, and setup notes. It does not include a WordPress installation, database, login, or hosted backend.