WebEdge CMS and public content API

Content had to feed multiple sites, while manual updates slowed publishing.

The CMS and content API give WebEdge an internal place to manage content for more than one website. It replaces manual page edits with reviewed records, publishing states and a repeatable delivery path.

We built a CMS with a Convex data layer, typed structures and a public content consumption path.

The system combines a Vue administration interface with Convex data tables and a public content consumption path. Editors work with typed structures, while websites read approved content through a controlled API layer.

Technical foundation: Vue 3, TypeScript, Convex. This matters not as a logo list, but as the set of choices that keeps data, state, user actions and future maintenance manageable.

Vue 3 and TypeScript keep editor screens close to the data contract, while Convex provides the real-time record layer. The API is treated as a product boundary, not as a private database shortcut.

In real use, “WebEdge CMS and public content API” works as a clear sequence: it starts from the original problem, then the user takes the primary action, follows a clear data path and reaches the result. The experience stays logical instead of being a random set of screens.

The practical value shows where manual work used to be needed: part of the process is automated, responsibilities are clearly separated, and each module does one understandable job. That is what keeps the solution easy to maintain and extend.

Publishing is centralized and sites can consume one reviewed content source.

Publishing becomes a central workflow. Sites can share one reviewed content source, and the team can add new content types without rebuilding every public page by hand.