A 1,400-page SAP marketing site, edited by 40 humans without conflict.
Rizing is a global SAP consultancy. Their marketing site had grown to 1,400 pages across 12 locales, maintained by 40 editors in five countries. Concurrent saves were corrupting content. Preview was broken. Deploys took 45 minutes.
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.
The content model problem The root cause was a flat content model: every page was a blank canvas. We ran a two-week content audit and found 14 variations of a hero block, none of them compatible. The first deliverable was an ADR 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.
Edge rendering + ISR The site runs on Next.js 15 with Vercel Edge. The 45-minute deploy became a 90-second cache purge. TTFB dropped from 2.4s to 0.6s on the median page.
The result 40 editors work concurrently without conflict. Every content change previews in under two seconds.