CMS

Every WebEdge site needed the same editing tools — content types, media, roles — and one API to read published content, instead of a separate database per project.

Every WebEdge site needed the same editing tools — content types, a media library, roles — and one API to read published content, instead of a separate database per project. But it turned into more than storage: it became the place the public marketing content actually lives.

A Vue 3 + webedge-db CMS where editors define content types at runtime, upload to a media library and manage roles; webedge-db live queries drive a realtime admin, and a public REST endpoint serves published entries.

A headless CMS on our own reactive backend where editors define content types at runtime, upload to a media library and manage roles; live queries drive a realtime admin, and a public read API serves published entries. On top of that, it holds the real content this site runs on — the project catalog as article seeds, marketing and AI-topic articles, SEO hubs with internal links, and the forum-first public descriptions for the ePokalbis community.

Built with Vue 3, TypeScript, webedge-db.

A Vue 3 admin on our own reactive backend; runtime content types, a media library and roles; live queries for a realtime editor; a public read API with regression tests; seed data for the project catalog and articles.

This portfolio and the other WebEdge sites read their content from this single CMS through its public API.

One place to manage everything public: editors change content and the sites rebuild from it, so new pages, projects and articles are added through typed content instead of a separate publishing system.