Case Study - A first website for a publisher with a growing catalogue

The starting point

Tonipress needed to go from no website to a proper public presence. That meant the site had to do more than look respectable. It needed to introduce the publisher clearly, showcase the catalogue, and give readers an easy way to move between books, authors, and categories.

What the site needed to support

The catalogue includes translated literature and other titles that benefit from browsing rather than one-off visits. Without a website, discovery depended too heavily on off-site channels. The site needed to become a place where readers could land, understand the publisher, and keep exploring.

What we built

The structure was built around the main public routes: books, authors, categories, and core publisher information. From there, the page model made it easier to move from one title to another, understand who the author is, and publish new books or updates using one repeatable format.

The key decision

Books, authors, and categories could have been treated as separate collections of pages. Connecting them created a more useful browsing system: a reader can arrive through one title and continue through the author or category without returning to the beginning each time.

Why that matters

A publisher without a site has very little control over how the catalogue is found or understood. A publisher site only becomes useful when it combines credibility, browseability, and a setup the team can keep using as the catalogue grows.

As a first website, this project does not have a like-for-like website baseline. The case therefore focuses on the publishing model and the routes that now exist, rather than claiming a conversion uplift that was not measured here.

What changed in day-to-day use