A 1,400-page SAP marketing site, edited by 40 humans without conflict.

Rizing came to us with a site that had outgrown itself. Built on a legacy CMS with no content model discipline, 1,400 pages of SAP consulting content were maintained by 40 editors across five countries. Concurrent saves were producing merge conflicts in the CMS. The preview environment was six weeks out of date. Deploys to the CDN took 45 minutes and required a developer on call.

The content model problem The root cause was a flat content model: every page was a blank canvas, and editors had added components over the years without governance. We ran a two-week content audit and found 14 variations of a "hero" block, none of them compatible. The first deliverable was an Architecture Decision Record that reduced the block vocabulary from 47 components to 11.

DatoCMS for 12 locales We chose DatoCMS for its field-level localization model. Each record exists once; locale variants are fields, not duplicate records. For a 1,400-page site with machine-translated content needing human review, this was the difference between a manageable workflow and chaos. We defined the schema in code, reviewed it with the Rizing content team, and promoted it to production before writing a single line of Next.js.

Edge rendering + ISR The site runs on Next.js 15 with Vercel Edge. Static pages are generated at build time and revalidated on DatoCMS webhooks. The 45-minute deploy became a 90-second cache purge. TTFB dropped from 2.4s to 0.6s on the median page. The 12-locale homepage now loads in under 800ms from any continent.

The result 40 editors work concurrently without conflict. Every content change previews in under two seconds. The site has shipped zero regressions in three quarterly releases. Rizing's marketing team now ships campaigns without filing a developer ticket.