Editorial workflows, GIT them here!
summary
Strapi v3 on Platform.sh deploys alongside a Gatsby front end using an internal network and a development Gatsby server to enable live preview via the __refresh endpoint. A runtime-writable mount lets editors create collections locally, then an ad hoc to_master collection flag plus an afterUpdate lifecycle hook uploads assets and recreates entries on the production Strapi instance. Source operations can commit mount changes into Git, but the flow adds edge cases around permissions, conflicts and non-reproducible dev-only behavior.
AI-written summary · about
chapters (7)
- 0:00Introduction to editorial workflows
- 3:56Why decouple and GitOps
- 10:25Platform.sh and GitOps model
- 13:35Live preview with Gatsby
- 18:13Editorial review process
- 26:04Adding new content types
- 29:52Summary and Q&A
related talks
25mNext-Gen Content Workflows in Strapi
28mBest Practices with Strapi, Next.js, and v0
33mRebuilding the Future: How We Transformed Our CMS with Strapi
08mShift gears, not code: How a French E-Bike Brand Hacked Digital Flow
18mSeamless UX with Advanced Technology in the Digital Era
11mHow I capture testimonials before they disappear
56mHow to keep Drupal relevant in the Git-based and API-driven CMS era
16mWhy I chose Next.js for my Strapi application