Skip to content

Home / Guides / Website usability

Website usability

An app-like WordPress site, without building an app

App-like WordPress with filter rails, sheets, shared components, reading options, dark mode inside a brand palette and a logo that is still text.

By Shane Rounce · 4 min read

An app-like WordPress site makes sense for readers of a sports betting news site: they often also use a betting app, and they bring its expectations with them. They expect filters that respond instantly, panels that slide in rather than new pages, settings that stick, and a dark mode. A theme built as a stack of web pages feels slow next to that.

I did not build an app. I built a few patterns into the WordPress site and used them everywhere. The patterns are simple. Being strict about reusing them was the hard part.

A filter rail with counts

The sports calendar, the betting glossary and the tipping record all use the same filter rail: a column of filters down the side, each option with a count of what it would show, and a round knob on its edge that folds the rail away. On phones it becomes a bottom sheet.

The counts matter more than they might seem to. A filter that leads to zero results is a small betrayal. Showing the count before the reader taps saves them the round trip.

Sheets, one at a time

Clicking an event, a term or a setting opens a sheet that slides over the page rather than loading a new one. Three rules kept the sheets sane:

  • One right-hand sheet at a time. Opening the bet slip closes the settings panel, and the other way round.
  • Every sheet has an address. An event sheet can be shared, and opening the link opens the sheet.
  • Only the page root locks on phones, so the sheet scrolls and the page behind it does not.

One settings panel

Preferences had been scattered: a theme toggle here, an odds format switch on every price banner, alert options somewhere else. They now live in one panel with four tabs: appearance, odds display, alerts, and reading and layout. Price banners just say how odds are shown, with a "Change" link to the panel.

Preferences are applied before the first paint, saved in the browser and, for signed-in readers, copied to their account. If a reader changes the scheme in another tab, or comes back to a page held in the browser's back-forward cache, the panel follows the newer choice rather than writing its own stale copy over it. That last bug took longer to find than to fix.

Accessibility options that actually change things

Two options went into the reading tab:

  • Reduce motion. It follows the device's setting and can also be switched on by hand. When it is on, animations and transitions finish at once, smooth scrolling stops, and the carousel's autoplay, the price ticker and the map's fly-to animations all stand still. A class on the root element and a small event mean every component can listen for it.
  • A dyslexia-friendly font. OpenDyslexic, self-hosted and only downloaded when the option is on, with a little more letter, word and line spacing for reading text and headings. Buttons, bars and prices keep their own sizes and figures, so the layout does not break.

Turning the font on was also the best layout test I ran. The bet slip's closed tab clipped its second line, and its price line cut the return off. Both were real bugs that would have hit anyone with a larger default font size too.

The bet slip and the settings panel share their parts

The bet slip and the settings panel are both right-hand sheets. Early on they had separately written close buttons, headers and edges, and they drifted apart a pixel at a time. The fix was not to make them look the same. It was to make them use the same parts: the slip now uses the settings panel's close button, with the same class, icon, size, hover and focus ring. They cannot drift because there is only one of each.

Dark mode inside the brand palette

The brand has a short, strict palette. The temptation in dark mode is to invent a few in-between colours to make things look right. I did not allow any. Every dark surface, link and accent comes from the existing palette, and where something did not work, the design changed rather than the palette.

That rule surfaced a nice problem with team kits. Kit swatches are drawn in the team's own colours. In dark mode a black kit disappears on a black surface. Kits now get a thin outline whenever their colour matches the surface they sit on, in either scheme.

An animated logo that is still text

The header logo used to be an image. It is now an animated wordmark made of real letters: the letters animate in once per session, then stay put. It is the homepage's main heading, so search engines read the site's name as text, and screen readers hear the plain name rather than the styled capitals letter by letter.

A few details made it acceptable to replace a brand image:

  • It was matched to the original image logo by pixel overlay, including spacing and the size of each element.
  • It plays once per session, again on a reload, and not on back or forward navigation.
  • With reduced motion, it simply appears.
  • With the dyslexia-friendly font on, the wordmark keeps its own letters.

App-like WordPress through shared patterns

None of this needed a JavaScript framework or a separate front end. It needed a small set of components, used everywhere, and a refusal to let one-off copies creep in. When two parts of the interface should behave the same, make them the same code, not the same appearance.

Need a hand with your next project?

I help with WordPress development, with practical advice and hands-on work. Tell me what you are trying to improve.

Email Shane