Document Form
The answers become documents of a model you pick, in the folders you choose. With edit mode on, the same form edits them later.
How it worksVeva CMS · by Advania
Veva is a modular content management system for .NET Blazor. Every feature is a package: reference it, restart, and its components are in the editor.
Veva.Web.Essentialsalways on
Add-on modules
dotnet add package Veva.Web.Essentials
then restart the site
How a page is built
Developers shape the bottom two. Editors work in the top two. Each layer changes without touching the others.
Text, images and data that editors write, bound into components with expressions like {_PageTitle}.
Heading, Grid and Form come built in. Your own are Razor components marked [VevaComponent].
Which areas a page has and which layout it uses: a Page Area for each page, Shared Areas for all of them.
Layouts, CSS, header and footer, registered with AddNamed<ITheme, …>.
Why Veva
Editors compose pages from components, preview them and publish on their own.
Render pages, serve content as JSON over the API, or both from one site.
Standard Blazor components, themes and hooks in Razor and C#. Nothing proprietary to learn.
Read JSON and XML feeds and bind them into pages. Integrate back-end services.
An AI assistant for editors, and an MCP endpoint that coding agents connect to.
Access control, dev and production kept apart. Windows, Linux or Docker.
Components and data binding
Presentation components render what editors set. Data-providing components fetch documents, assets or rows and hand each one to the components inside them.
Heading, Paragraph, Link, Image, Icon, Tabs, Grid. They render the properties an editor sets, and any of their text can be bound to data. A Link with a theme button class is the button.
Document List, Document, Images, Data Table. They have no look of their own: they fetch items and hand each one to the components placed inside them.
01
A Document List queries the news, with its filters and paging.
Document List02
Each story's fields are bound by name, as {title} or {_Published:d. MMMM yyyy}.
DataBindingContext03
A Heading, an Image and a Link in the item template show each story.
Forms
Editors build forms in the designer from fields, steps and checks. The kind of form decides where the answers go.
The answers become documents of a model you pick, in the folders you choose. With edit mode on, the same form edits them later.
How it worksThe values become a page's query string, so a Document List or a search there filters by them. Or a submit handler of yours saves them.
How it worksAI assistant · MCP server
Editors ask the admin's AI assistant for pages, documents and images, with the permissions they already have. Coding agents such as Claude Code connect to the MCP server at /mcp and use the same tools.
Documentation
Setup, guides and the developer reference.
What each module does, and the package it comes in.
Hooks and interfaces for extending Veva.
Get started
Veva.Web.Essentials gives you pages, assets and documents. Add the next module when the site needs it.