Big announcement from #StrapiConf Keynote 2025:

Strapi gets a Live Preview feature 🀩 Only available for Growth and Enterprise plans though, not for Community Edition.
https://strapi.io/features/live-preview

Keynote: https://www.youtube.com/watch?v=L2G_yG-_wPQ
#strapi #strapicms #cms #webdev

Live Preview | Strapi Features

Get a live preview of your content changes directly within Strapi before publishing, enabling seamless collaboration and confident content validation.

@mandrasch As a web (and strapi CMS) developer I am amazed how almost every "new" feature in the node.js ecosystem is basically a re-implementation of what has existed in PHP, Ruby & co. for decades. Particularly when it comes to headless... "decouple your interfaces, use APIs, do monorepos, write microservices, buy SaaS for scalability"... and after navigating so much complexity for years, devs are super happy for every bone that VC-startups throw at us that make things simply "work"...

@gorgonzola to be fair: real good live preview with side-by-side editing hasn't been integrated in most PHP CMSes as well, I only know a good implementation from CraftCMS? And headless is relatively new for PHP CMSes as well and still a challenge?

Regarding other stuff like SSR, I totally agree πŸ€“πŸ˜

@mandrasch @gorgonzola
@statamic does both very well since years.
@mariohamann @mandrasch @statamic Haha #statamic would have been my response as well! Been using it for some time now, didn't miss any other CMS ever since.

@gorgonzola @mariohamann @statamic okay, good point πŸ‘

But Statamic has its own challenges (professional git collaboration and sync with team > 5 devs for example). Therefore I'm not really sure if PHP CMSes do things really well yet - or if more innovation from NodeJS side is still needed as well. Storyblok did some with cloud + local dev bridge, Payload (created by one ex-WordPress+Dev) has still to show it's strengths, etc.

And it's a huge difference if one freelancer or max 2 devs work work on a project - or multiple devs in enterprise projects 🀷

And VC backed software is a good and critical point... But I experience it in the DDEV Open Source Community - it's hard to get funding for only 2 maintainers...

@mandrasch @gorgonzola @statamic Hm. "Der Spiegel" uses Statamic for all of their content. And I'm currently building something with a total of 4 developers. Not sure if I can relate. :)

What I understand is that the handling of data, migrations etc. can be a challenge β€” which could be reduced when switching to a database approach. And... data migration is a challenge in EVERY CMS in my opinion.

Would be curious what was your concrete experience?

@mariohamann @gorgonzola I know the Spiegel Story, but they use it in their special own ways (https://statamic.com/blog/statamic-at-spiegel-scale-2 - see screenshot. I'd be more convinced if an agency does Statamic at full scale.

My experience while evaluating Statamic was this a couple of years ago:

A) It's hard to separate content from config, but there is a new online course about it (didn't check it)

https://dev.to/mandrasch/separate-content-from-config-in-statamic-466e

b) There is no admin level restriction on Live server https://github.com/statamic/cms/discussions/6289

c) For CMSes like TYPO3, Drupal, CraftCMS - you can pull down the live database (and uploaded files) with a ssh and rsync command. For Statamic, there is Git Automation or switching to DB mode. 1/

Statamic at SPIEGEL Scale (Part 2)

Statamic

@mariohamann @gorgonzola

d) For CraftCMS, there is "php craftcms up" for deployment which applies all project config changes (entry type changes, fields) to the live database on deployment. https://craftcms.com/knowledge-base/deployment-best-practices#codify-deployment-steps

I haven't seen that for Statamic. Kirby has the same challenge. What if Developer A does some massive content structure changes and we want to deploy it safely and robust?

As you said - that is a challenge for all CMSes.

Each system and approaches has their strengths and weaknesses, but as far as I know Craft CMS took the biggest step towards "automatically keeping the config and data structure in git" and provide a way to deploy it.

Strapi has it in git, but there is not auto-migration if you change entry fields / do bigger structural challenges as far as I know. 2/

Deployment Best Practices | Craft CMS

The specific steps required to deploy Craft CMS depend on your hosting setup, but there are a few things everyone can do to make the process smoother and…

Craft CMS

@mariohamann @gorgonzola Therefore I didn't follow up with Statamic after trying it out - instead I looked more into Craft CMS which had separation of content and config built-in from the start (via project config https://craftcms.com/docs/5.x/system/project-config.html)

This auto-magic approach has some drawbacks as well, but it's one way of doing solid and robust deployments.

It will be interesting what https://payloadcms.com/ ends up it for example.

But it totally depends on your requirements. I looked at it from the "professional development with git" perspective with separation of content and configuration - which I had seen from TYPO3 teams. (And which wasn't possible with standard out-of-the-box WordPress for example ^^)

Maybe there are agencies or companies which fixed the troubles I had with Statamic? 3/3

Project Config | Craft CMS Documentation | 5.x