Rebuilding the Future: How We Transformed Our CMS with Strapi
summary
Adidas replaces a dozen legacy CMSs with Strapi as the content core, modeling 94 collection types, wiring an event-driven pipeline with Kafka, OpenSearch and a separate high‑availability delivery tier, and deploying across three AWS regions. The platform handles 10 million publications, 31 million API requests per day and 1TB+ assets, cuts content creation time by 54% and raises creator satisfaction from 54 to 82 points while keeping a 20–25 person core team and year‑long development.
AI-written summary · about
chapters (8)
- 0:00Introduction to the talk
- 2:12Background and challenges
- 8:53Strapi integration approach
- 13:55System architecture overview
- 17:08Integration with enterprise systems
- 19:36Results and benefits achieved
- 23:26Cultural and technical impact
- 25:11Q&A session
related talks
11mStrapi at
09mFrom 0 to Strapi in Production in 60 days
03h 21mAdopt Stage
13mUsing Strapi as a publishing platform for the largest local sports betting platform
21mCreating a media website with over 900.000 articles
07mBoosting Productivity and Team Velocity with Strapi
21mCreating a Culture of Innovation
15mBuilding Modern CMS Driven Web Applications with Next.js