Devs building on Next.js, Astro, SvelteKit, Nuxt:
What's the worst part of your current CMS?
β Pricing that scales with usage
β Bad DX / clunky editor
β API rate limits
β Migrations / lock-in
β Something else
Researching pain points. Not selling.
Reply or DM π
Unfoldcms is shaking things up in the Laravel CMS world - but what makes it so revolutionary? We dove in to find out, and what we discovered might just change the way you build forever
https://t.co/mYjRXZpsHM
WordPress devs: what's the dumbest plugin you've had to install just to ship?
Mine: a plugin to add a 301 redirect. A whole plugin. For one redirect.
Building a CMS where this stuff is built-in β what else should be native by default?
Built a self-hosted CMS on Laravel + shadcn/ui as an alternative to WordPress + plugin sprawl.
If you've left WordPress (or wanted to): what's the ONE feature that would have made you switch sooner?
Looking for honest answers, not pitches. Replies > likes π
Stages of using WordPress as a developer:
1. "This is fine"
2. "Just one more plugin"
3. "Why is my site 8 seconds slow"
4. "I'll build my own CMS"
5. discovers UnfoldCMS
6. Peace
Unpopular opinion: 90% of websites don't need a headless CMS.
A traditional CMS with a clean API is enough for most projects.
Headless is a tool, not a religion.
Agree or disagree? π
WordPress plugin vulnerabilities disclosed weekly in 2026: 250+
That's 36 per day.
43% are exploitable without authentication.
Maybe it's time to consider alternatives