Skip to content
SR Web Studio

Scaling a Collaborative Print-Publishing Platform Over Years

Sustained multi-year product engineering on a collaborative platform where 1M+ users co-design and order printed magazines, books, and posters — marketing site, editor app, and dashboard.

Browser mockup of a collaborative magazine-editor app: a page canvas, layout tools, page thumbnails, and co-editor avatars.
Illustration for this case study. Names and details are placeholders.

The problem

Three years, three connected surfaces, one product that never stopped being used while we worked on it. This collaborative platform lets ordinary users design, co-edit, and order printed magazines, books, posters, and photo collages together, and, by its own public claim, serves more than a million people. The work touched the public marketing site, the core editor and creation app, and the user dashboard handling project management, collaboration, and pricing — all three had to stay live while collaboration features, fulfillment flows, and new product formats were built and refined over time.

The approach / solution

  • Delivered and maintained a Nuxt, Tailwind, and TypeScript front end backed by a Strapi CMS, with i18n built in to serve a multi-language audience.
  • Worked across all three surfaces as one connected system: the marketing site, the editor where users co-design their publications, and the dashboard managing projects, collaboration, and pricing.
  • Kept the engagement running as ongoing product engineering: collaboration features, fulfillment flows, and multi-format product support (magazines, books, posters, collages) evolved while the live tool stayed in active use by its existing base.

Outcome / result

As of the most recent check the platform is live and active. High-demand order-delay messaging is still up, a sign of real transaction volume. Cloud-backed image storage, a multi-format product catalog, and customer testimonials are all still on-site. Of every project in this portfolio, this is the strongest scaled-and-maintained-over-years story, independent of the event-tech angle.

Why it matters for enterprise buyers

Anyone can ship a v1. Keeping a real product alive and improving for roughly three years — across a marketing site, a stateful creation app, and a user dashboard, all at once — takes a different kind of discipline. It’s the clearest proof of durability in this portfolio: the ability to own a product’s evolution, and keep owning it, long after launch.

Related service

Full stack web app or MVP

Have a live product that already has users on it, and needs to keep evolving without breaking for them? Reach out.