Publishing
platform
WordPress for Penguin’s UK publishing sites
At a glance
Company Type
Publishing
Scale
Multi-site content
Regions
United Kingdom
Focus
Publishing platform
Services delivered
WordPress, content architecture, editorial
Results
WordPress structures that fit books, imprints, and editorial calendars u2014 not a generic blog
A publishing site that editors can keep current as titles and campaigns move
About Penguin Publishers UK
- Penguinu2019s UK publishing sites exist to help readers find books, authors, and series. Catalogue data, feature content, and campaigns share the same WordPress surface.
- That mix only works if the content model is honest: titles, imprints, and landing pages have to relate to each other, not live as disconnected pages.
- The work was WordPress for a publishing house u2014 templates and fields that match how editorial teams actually publish, and a front end that stays readable on a phone.
- This is the first version of the case study. More detail will be added as the write-up expands.
Project overview
Penguin needed WordPress that behaved like a publishing platform: structured content for books and imprints, templates that do not collapse under long-form editorial, and a site editors can update without a developer in the loop.
I focused on the content architecture and the WordPress build around it u2014 so new titles and campaigns could land in the same system instead of becoming one-off pages.
Project goals
01
Model books, imprints, and editorial pages so the CMS matches how a publisher actually works.
02
Ship WordPress templates that stay clear when content is long, image-heavy, and frequently updated.
03
Give editors a path to publish without opening a development ticket for every title.
Client's words
Vijay modelled books and imprints the way a publisher actually works. Editors publish titles and campaigns in WordPress instead of waiting on a developer for every landing page.
Work