Trampolin is a creative studio from Europe that likes to do things properly.
They build brands, interactive experiences, and complex platforms. What ties everything together is their approach. Every project starts with a consistent technical foundation, designed to give the team full control, and enough flexibility to push the design wherever they want to go.
They call that foundation Boiler: A Nuxt/Dato boilerplate that's prepared to scale for any project that comes their way.
We sat down with Andrija and Dragan to talk about how they’ve scaled this setup across a range of use-cases like cultural institutions, radio platforms, animated storefronts, and fast-moving editorial teams, all without reinventing the wheel.
Sticking with what works
Boiler powers all Trampolin projects. It includes the essentials: a ready-to-use UI component library, internationalization, DatoCMS schema integration, and a deploy-ready setup. For the team, it is not just about saving time. It is about avoiding chaos from years of experience.
We’ve been using the same stack for everything, which gives us kind of our super Swiss army knife that we can use on each and every web project.
Nuxt gives them a full-stack framework that scales across use cases, from static sites and hybrid apps to web platforms with API layers, e-commerce, or realtime components. DatoCMS handles the structured content, and its clean editor experience means clients understand what they are working with almost immediately, minimising their average onboarding time to about 2 hours.
Boiler is consistent across all projects - internationalization, Lighthouse focus, consistent naming conventions for fields... That consistency lets the team move quickly while still keeping flexibility and control. Once deployed, it is extended as needed, and more technologies and frameworks are added into the mix depending on the project needs. The content structure stays predictable. The build process stays stable. The project scope can grow without forcing a rebuild. It just works.
Boiler is so well-structured as their foundation, that they're able to easily extend it to other technologies and frameworks as needed, using modules they've got in place to plug-and-play other tools into their stack depending on the project.
Schema-first
Schema comes first. Trampolin aligns their design and development workflows with the structure of the CMS. Components in the frontend mirror sections in DatoCMS. Naming conventions are fixed. Blocks are modular and controlled. Every developer on the team kinda already knows how a new project will be structured before they even open the repo.
We can have one person jump into a project that’s been running for two months and immediately start working, without any onboarding.
Their content models include built-in validations, field constraints, and reusable structures for SEO and performance best practices. Editors are guided through structured flows, and can only create layouts that match the original design logic, ensuring there's nothing breakable by accident.
The schema doesn’t just support the frontend. It also helps enforce standards for accessibility, responsiveness, and structured metadata.
If the schema breaks down, everything above it becomes harder to manage.
That is why they treat it as the core of every build, not a side task to clean up later.
Creativity 🤝 Performance
One of the more surprising parts of their projects is that many of their builds are visual and interaction-heavy, but still deliver clean Core Web Vitals and near-perfect Lighthouse scores. This is not a happy accident.
On projects heavy on visuals and animations, like their Hitradio Center one, boiler is optimized for performance from the start. It includes default lazy loading strategies, uses GPU-accelerated CSS transforms, avoids layout shifts, and limits JavaScript payloads with tight control over third-party libs. Performance tracking is integrated into the dev process, not added later just for "handling pretty effects".
We check performance scores constantly. It’s something that was pushed into our dev team early, and now it’s part of how we work from the start.
For example, for projects like SpaceKart, they leaned on GSAP and Three.js for animation, but made trade-offs early to avoid heavy scripts where unnecessary.
For Beletrina Digital, they integrated custom video and audio players alongside static editorial layouts and B2B sub-portals, all from a single codebase.
The result looks diverse on the surface, but under the hood it remains stable and fast.
They have also built modules into Boiler for Unity integration, real-time audio streams, and 3D model embedding via DatoCMS. None of this happens without tight planning around performance budgets. Every interaction is tested before launch.
Honestly, its all pretty damn dope!
Let's get back to us 💅
Of course we've gotta make it all about us somehow though 😅
The end goal for Trampolin is a CMS their clients don't have to fight with. Onboarding is simple. Most handovers happen over a single recorded session where two hours is usually enough.
The only pain point was the wait time for rebuilds after content changes. So they solved that too. The Boiler starter now includes real-time previews, allowing editors to see their changes live on staging without needing a full deploy.
It’s like editing any other website. It refreshes instantly, and they don’t have to wait for the site to build.
The CMS itself has never been a blocker. Trampolin’s team consistently returns to DatoCMS because it balances flexibility with clarity. It is fast to work in, doesn’t overwhelm editors, and scales well with project complexity.
Nobody has ever said anything bad about the CMS. And that’s a confirmation that we made the right choice.
Features like GraphQL types, built-in image optimization, and multiple environments make development smoother. The Appearance tab lets them brand the experience for each client. The Plugin SDK gives them control when any specific new features are needed.
