The organisation needed one portfolio publishing platform for prospective clients, editors, and studio leadership. The existing journey divided project stories, media collections, service pages, team profiles, editorial publishing, enquiry qualification, landing pages, and content performance between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete portfolio publishing platform shaped around prospective clients, editors, and studio leadership
The organisation needed one portfolio publishing platform for prospective clients, editors, and studio leadership. The existing journey divided project stories, media collections, service pages, team profiles, editorial publishing, enquiry qualification, landing pages, and content performance between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between portfolio stories, editorial publishing, and enquiry journey, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole portfolio publishing platform.
- Separate firm creative services rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined portfolio stories, editorial publishing, and enquiry journey without blurring roles
Give editors structured project content and flexible visual composition without making every new story a development task.
In the portfolio publishing platform, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Next.js, Headless CMS, Image CDN formed one supportable portfolio publishing platform
The architecture follows business ownership rather than the navigation menu. Next.js, Headless CMS, Image CDN share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind editorial publishing.
In the portfolio publishing platform, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Next.js supports the primary product surface.
- Headless CMS owns a bounded part of the product journey.
- Image CDN keeps operational data and handoffs reviewable.
The release had to prove the whole portfolio publishing platform, not one polished screen
The studio can publish stronger work stories, qualify enquiries, and keep the site current without sacrificing the visual system. The release plan therefore followed representative work across every audience and the complete path through portfolio stories, editorial publishing, and enquiry journey.
Acceptance for the portfolio publishing platform included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
The studio can publish stronger work stories, qualify enquiries, and keep the site current without sacrificing the visual system.
- 01
The portfolio publishing platform now gives prospective clients, editors, and studio leadership one shared operating record.
- 02
Portfolio stories, editorial publishing, and enquiry journey follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.