Here are a few projects where we implemented @datocms for growing enterprise teams.
In some cases, it replaced outdated systems that were difficult to maintain. In others, it gave editorial teams a simpler way to manage multilingual content, preview updates in real time, and launch new pages faster.
The goal was the same across all of them: build a faster, scalable website experience without making content operations more complicated.
Read more: https://t.co/6JrC5rMjw5
A throwback worth a repost.
A few years back, Brian Dean (Backlinko) came to us with a problem most content sites eventually hit. His WordPress site, built around big illustrations and a heavy theme, was slow. Years of optimization had not fixed it. The man who taught half the SEO industry that page speed matters was being slowed down by his own stack.
We moved Backlinko to a composable setup. Next.js on the front, headless WordPress on the back, deployed on Netlify. The editorial workflow stayed the same. Everything in front of the user got faster.
The numbers from that migration:
3x faster load time
64% overall performance improvement
Core Web Vitals improved across the board
Zero downtime in the cutover
Brian's take at the time: "We struggled with Backlinko's loading speed for years. The move made a tremendous difference in our load times and Core Web Vitals scores."
Sharing it again because the lesson has not aged. If WordPress is slowing your content site down, you do not have to throw away your CMS. You just have to stop letting it render the front end.
Case study: https://t.co/JcVJZFEdgL
We’ve seen @storyblok solve the same kind of problems across very different projects.
Let’s take 6 projects across 4 industries. Different companies. Different products. Different teams.
But the same kinds of issues keep appearing behind the scenes.
In the video, I break down what those problems looked like in each case, and how Storyblok helped simplify the way teams work with content in practice.
More details on the projects: https://t.co/E8fbIChFSH
Seven brands. One system.
HanseYachts AG is one of the world's largest sailing yacht builders, with seven distinct brands under one roof. We did not redesign seven websites for them. We built one design system, with a theming layer, that lets each brand keep its own identity while sharing a single technical and design backbone.
Built on Next.js, Storyblok, and Vercel.
Applying a new brand becomes a configuration job, not a project. Marketing teams ship faster. Cohesion across the portfolio without flattening any single identity.
If your company runs multiple brands and your team is rebuilding the same wheel for each one, there is a better shape.
https://t.co/ezJ0HYcuVK
We added a few more @sanity_io features to our CMS comparison center:
1️⃣ Real-time collaboration
2️⃣ Schema-as-code
3️⃣ App SDK for building custom workflows directly inside the CMS
👉 If you're evaluating headless CMSes, worth a look: https://t.co/pk646dS5aS
A redesign without a rebuild. UI work for RudderStack, the customer data platform.
Quick context: ~90% of the site got a new design system. 6X faster builds after we shipped.
The brief was the part most teams will recognize. Scale and modernize an existing Next.js and Sanity setup, without disrupting growth. Legacy Material UI made changes risky. The site had drifted into inconsistency. A full rebuild wasn't an option.
We rolled out a design system in phases. Replaced components one section at a time. Kept the site live and improving the whole way through.
On the conversion side: measured, tracked, ran A/B tests, analyzed heatmaps on the homepage and the key conversion points. Every recommendation backed by data, not assumption.
Sharing because most enterprise redesigns fail not on the design, but on the migration plan.
#designsystems #nextjs #cro
https://t.co/Vts7E31BeJ is built for multi-brand from day one. The video below shows why.
Two ways to make the system yours:
Pick a starter style. A couple of minutes to a working brand-aligned look.
Upload your own design variables. Color, type, spacing, radii. The system adapts and you get an Astro-ready foundation immediately.
Most design systems aren't actually portable. They ship with one theme and bend awkwardly when you try to use them across products. We built ours to feel native to whatever brand it lands in.
https://t.co/Vts7E31BeJ
#designsystems #astro #opensource
We built Bejamas/ui Create for @astrodotbuild 🔥
- Preview your Astro UI instantly
- Customize styles, colors, fonts, and icons
- Shuffle presets for quick inspiration
- Generate a full project in one command
See it in action 👇
https://t.co/O43ZyPTpuD
We just launched something new 👇
Bejamas Freelance Hub 🚀
→ access to quality projects (no bidding)
→ modern stack (React, Next.js, AI)
→ structured delivery (no chaos)
Built for freelancers who want to focus on real work.
👉👉Join the move - https://t.co/cxENwy40Jw
Turning complex financial services into a clear web experience is harder than it sounds.
We just published our latest case study: the full website redesign and rebuild for VFX Financial, a foreign exchange specialist operating across 20+ countries.
The challenge? FX risk management, international payments, private FX services. Dense, technical offerings that needed to feel simple and trustworthy on the web.
Here's what we did:
→ Restructured complex financial content into clear, digestible sections
→ Built a scalable design system that supports their ongoing growth
→ Implemented a headless CMS (Storyblok) so their team can manage content independently
→ Shipped on Next.js + Vercel for performance that shows in Core Web Vitals
The result is a fast, modern site that actually explains what VFX Financial does without making your head spin.
This is the kind of work we love at Bejamas. Taking something complex, stripping away the noise, and building a web experience that works for both the business and the end user.
Check out the full case study: https://t.co/IrroLwEMhI
Migrating an enterprise design system is never just a design problem. It's a process problem.
We worked with Rippling on exactly this. Their design and dev team plus ours, migrating components, rebuilding what needed rebuilding, and making sure the system works for everyone who touches it.
The result: a marketing platform that scales with one of the fastest-growing companies in HR tech.
The animation below shows a piece of what we built together.
#designsystems #scalabledesign #migration #bejamas
Transforming Van Raam with speed and multilingual power.
Van Raam is a Netherlands-based manufacturer and world market leader in special needs bicycles.
Their previous website needed a modern technical foundation that could perform consistently across regions and support scalable content operations.
Our scope in this project was implementation only:
- Modern frontend development in Next.js
- Headless CMS implementation and migration to DatoCMS
- Global hosting setup on Vercel
- Smooth page transitions and interactions for a frictionless browsing experience
Impact:
- 3.5x faster loading performance
- Load times reduced from 6-7 seconds to under 2 seconds globally, including the US
- Reliable multilingual publishing workflow for content teams
- Future-ready platform built for growth and easier updates
As Van Raam shared:
Together, we have built a fast, future-ready website that reflects the latest in web innovation and is scalable to meet our growth ambitions.
Case study:
https://t.co/3NLdFkbZ8b
StarkWare builds blockchain solutions that make decentralized systems faster, more secure, and more scalable.
For this project, we explored a visual language that combines technical clarity with imagination.
Our design direction:
- Fluid gradients, soft light transitions, and layered transparencies
- Motion-inspired compositions that feel open and forward-looking
- Illustration scenes that express security, scalability, and connectivity without rigid diagrams
- A style that complements StarkWare’s geometric and isometric visuals while adding more depth
Outcomes:
- Stronger visual identity across marketing touchpoints
- Clearer storytelling around complex blockchain concepts
- A reusable illustration approach for consistent future assets
Feedback from StarkWare:
We looked for a team to step into an existing project and help upgrade it. From the beginning Bejamas stepped up and worked professionally, quickly and collaboratively, making the entire process smooth and seamless.
Thanks to the StarkWare team for the trust, and to Justyna Lasota for leading the illustration direction.
Case study:
https://t.co/dG3l3bIqXR
Rebolt is a marketing platform for local service businesses. From cleaners and contractors to landscapers and personal trainers, it helps teams generate leads and manage their digital presence with less friction.
Our scope in this project was Web Design.
Working closely with the Rebolt team, we shaped a clean, modern visual direction focused on clarity and conversion.
What we focused on:
• Clean, contemporary aesthetic that feels credible and approachable
• Clear visual hierarchy across landing and pricing pages
• Consistent component styling for a cohesive brand experience
• Readable layouts that highlight services and plan differences
• Mobile-first visual decisions for busy local business owners
Outcome:
A polished, intuitive design that communicates Rebolt’s value quickly and helps local pros feel confident taking the next step online.
Case study:
https://t.co/m4KKzahwPe
Great products need documentation that moves at the same speed as the product itself.
For O1 Labs, we redesigned O1JS documentation to make the developer journey faster, clearer, and easier to trust.
O1JS content previously lived inside the broader Mina documentation, which created confusion around context, ownership, and where to start.
What changed:
- Dedicated O1JS documentation space with a clear identity
- Reworked information architecture and clearer naming
- Navigation built for both onboarding and deep technical browsing
- Search results redesigned to add context and reduce repetitive dead ends
- Visual system improved for readability across long technical pages
- Reusable templates for diagrams and graphics to speed up future updates
Why this matters:
- Faster onboarding for new developers
- Less friction during everyday implementation work
- Easier maintenance for internal teams
- Stronger long-term adoption of the library
Documentation is part of product experience, not an afterthought.
Your product is solid. Your docs should be too.
https://t.co/4jFHzUMakB
Another great collaboration with @descopeinc!
This time, for their MCP Hackathon.
Built on @contentful, the setup is easy to reuse and update, so future hackathons won’t start from scratch.
More in the full case study: https://t.co/1zSjdwUkpa
https://t.co/dhSanX8BVY now includes 40+ ready-to-use components.
Need more power in Astro? https://t.co/Vts7E31BeJ uses the same core component system, so your team can move from no-code to code without rebuilding everything.
Start in Webflow, scale in Astro.
Faster launches, cleaner handoff, and consistent UI across both workflows.