Background decorative image

// RECORDED: 2026-02-25

Chasing the Edge and Building "EZ Edge CMS"

I’ve recently fallen down the rabbit hole of Edge computing, and honestly, I am absolutely amazed by its power and potential. I’ve been spending my time investigating, learning, and experimenting with new ways to build beautiful, highly performant websites.

Recently, I built a few websites using Hono and HTMX. If you haven't tried this stack yet, it's incredibly fun, and I absolutely loved the functionality it provided. However, I quickly ran into a major friction point: updating my blog.

With my previous setup, publishing a new post meant writing code, making a commit, and pushing to GitHub just to trigger an update. As a developer, I love Git, but it is not a convenient way to run a blog on a day-to-day basis. I looked around for a lightweight, edge-native solution to solve this, but I couldn't find anything that fit my exact needs.

So, I decided to build my own.

Enter: EZ Edge CMS

I am currently focusing all my free time on building EZ Edge CMS, a lightweight Content Management System purpose-built for Cloudflare Workers.

The first iteration was a great learning experience. The performance was stellar, but it had a major flaw: it lacked robust styling capabilities for both the content itself and the overall website design. Because I want this to be a genuinely useful tool, I decided to hold off on publishing that early version and went back to the drawing board to make it better.

The Breakthrough: EditorJS meets UnoCSS

To solve the styling and content management issues, I recently discovered an amazing combination of tools that form the backbone of the new EZ Edge CMS:

  • EditorJS: This is a fantastic block-styled editor. Instead of messy HTML, it outputs clean JSON data. This is perfect for my edge setup because it allows me to effortlessly save and retrieve content directly from Cloudflare KV.
  • UnoCSS: This is an instant, on-demand atomic CSS engine. Combined with EditorJS, this is a match made in heaven. It ensures that the absolute smallest possible size of CSS is loaded—delivering only the styles that are actually used, rather than a massive file filled with unused CSS. The best part? We get all of this without a complex compiling step.

What’s Next?

As with any new stack, learning the ins and outs of EditorJS and UnoCSS is taking a bit more time than I initially expected. Because of this, I'm not quite ready to publish the code just yet.

However, the pieces are rapidly coming together. I am hoping to have the first public version of EZ Edge CMS ready very soon. If you are a developer interested in edge computing, Cloudflare Workers, and blisteringly fast websites, stay tuned!

Need similar solutions?

If this article sparked an idea for your own infrastructure, let's discuss how to implement it.