Skip to content

Veva CMS · by Advania

Snap together the site you need

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.

Build your stackSwitch a module on and it snaps into place.
11 packages

Veva.Web.Essentialsalways on

  • Pages
  • Assets
  • Documents

Add-on modules

dotnet add package Veva.Web.Essentials then restart the site

How a page is built

One page, four layers.

Developers shape the bottom two. Editors work in the top two. Each layer changes without touching the others.

DEV
C#, Razor and CSS in your repository
EDITOR
The page editor, in the browser
  1. Content EDITOR

    Text, images and data that editors write, bound into components with expressions like {_PageTitle}.

  2. Components EDITOR

    Heading, Grid and Form come built in. Your own are Razor components marked [VevaComponent].

  3. Template DEV

    Which areas a page has and which layout it uses: a Page Area for each page, Shared Areas for all of them.

  4. Theme DEV

    Layouts, CSS, header and footer, registered with AddNamed<ITheme, …>.

Why Veva

Small pieces, one system.

Visual editing

Editors compose pages from components, preview them and publish on their own.

Traditional or headless

Render pages, serve content as JSON over the API, or both from one site.

Plain .NET Blazor

Standard Blazor components, themes and hooks in Razor and C#. Nothing proprietary to learn.

Connects to your systems

Read JSON and XML feeds and bind them into pages. Integrate back-end services.

AI-assisted, agent-ready

An AI assistant for editors, and an MCP endpoint that coding agents connect to.

Secure and portable

Access control, dev and production kept apart. Windows, Linux or Docker.

Components and data binding

Some components show. Some supply.

Presentation components render what editors set. Data-providing components fetch documents, assets or rows and hand each one to the components inside them.

Components and data

Presentation components

UI

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.

Data-providing components

Data

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.

  1. 01

    Fetch

    A Document List queries the news, with its filters and paging.

    Document List
  2. 02

    Bind

    Each story's fields are bound by name, as {title} or {_Published:d. MMMM yyyy}.

    DataBindingContext
  3. 03

    Show

    A Heading, an Image and a Link in the item template show each story.

Forms

Forms without form code.

Editors build forms in the designer from fields, steps and checks. The kind of form decides where the answers go.

Forms

Saves documents

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 works

Filters, searches, posts

Generic Form

The 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 works
TextE-mailNumberDate and timeDrop-downCheckboxesFile uploadReferenceConditional sectionForm stepsPDF generatorCaptcha

AI assistant · MCP server

Ask the site. Agents can too.

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

Find your piece.

All articles

Get started

Start with one block.

Veva.Web.Essentials gives you pages, assets and documents. Add the next module when the site needs it.

Read Getting started dotnet add package Veva.Web.Essentials
  • Essentials
  • Next (empty slot)

Type to search the docs, components and API.

↑↓ to move ↵ to open Esc to close Search by Veva