Technical Architecture of EZ EDGE CMS

I developed EZ EDGE CMS with a specific goal: to create a content management system that runs entirely on Cloudflare Workers without the bloat of traditional frameworks. By moving styling, image processing, and SEO logic to the edge, I’ve eliminated the need for origin servers and complex build pipelines. Here is the technical breakdown of the engine and the trade-offs I made to keep it fast. 1. Zero-CSS Middleware (with Theme Constraints) EZ EDGE CMS has no static CSS files. I integrated a Just-In-Time (JIT) UnoCSS middleware that runs at the edge. When a request is made: The middleware scans the HTML content. It generates the minimal utility classes required for that specific page. It injects the CSS directly into the . The Restriction: To maintain this performance, you cannot upload custom CSS files. You are limited to built-in themes where you can only customize colors and fonts. This ensures the JIT engine stays lightweight and prevents slowing down the edge isolate. 2. Edge-Nativ