news
Content Management Systems (CMS): Sveltia, EmDash, and WordPress
Thibault Martin: TIL that Sveltia is a good CMS for Astro
This website is built with the static site generator Astro. All my content is written in markdown and uploaded to a git repository. Once the content is merged into the
mainbranch, Clownflare deploys it publicly. The process to publish involves: [...]
-
Joost de Valk ☛ EmDash: a CMS built for 2026
EmDash is the most interesting thing to happen to content management in years. Not because it’s built on Astro (though it is), but because it’s the first CMS designed from the ground up for how we work in 2026: AI agents building sites, structured content that machines can parse and manipulate easily, and deployment at the edge.
-
Alex & Manu ☛ my take on cloudflares emdash
in EmDash, plugins run in isolated sandboxes called Dynamic Workers. they can’t just hook into everything like WordPress plugins do. instead, plugins declare what they need in a manifest: capabilities like “read:content” or “email:send.” the plugin can only do what it says it’s going to do.
-
Remkus de Vries ☛ WordPress Page Builders and Performance (The Brutal Truth)
Page builders promise speed, but usually not the kind that matters most. They promise faster development, faster editing, and faster iteration. They make it easier to launch pages without waiting on a developer. They give marketers, designers, and site owners more control over layout and presentation.
That convenience is real, and pretending otherwise would be dishonest. But there is a difference between development speed and site speed. A page builder can absolutely help your team move faster while making the finished site slower. And that tradeoff gets overlooked far too often.
This is not a hit piece. It is a practical breakdown of what page builders actually do to performance, where the costs show up, and what to do if you are already committed to one.