Extension points
Extend models, documents and their views.
Module · Veva.Modules.Documents
Define a model once, with the fields your content needs. Then list, filter, translate and publish its documents on any page, or serve them as JSON.
What it does
Field types from String and Html to Asset, Linked Documents and Value list. Or start from a model template.
A Document List shows them as a table, a grid, tabs or your own components, with paging.
Filter by folder, field, tag, search text or date, with values bound from a form or the address.
A Document friendly URL rule gives each document an address such as /news/my-story/.
Serve a model as JSON, XML, RSS or iCal, or read it through the headless Documents API.
Import CSV rows, translate the localizable fields, and publish drafts when they are ready.
How it works
01
Give it fields, languages and a UID format, or start from a model template.
IModelTemplate02
Write them in the editor, import a CSV file, or take them from a Document Form.
03
Place a Document List on a page and pick its design and filters.
Document List04
A detail page shows a single document. Bind its fields with {title}.
05
A routing rule turns ?uid= into a friendly URL.
DocumentFriendlyUrlRuleFor developers
Add a field type, react when documents are added, updated or deleted, or serve a model in a format of your own. Components bind document fields by name.
Extend models, documents and their views.
@code {
[CascadingParameter(Name = "RenderContext")]
public RenderContext RenderContext { get; set; }
// In a Document List's template, an editor sets it to
// "{title} · {_Published:d. MMMM yyyy}"
[EditorBrowsable, Parameter, DisplayName("Title")]
[EditorArgument("databinding", true)]
public string Title { get; set; }
}
<h3>@RenderContext.DataBindingContext.FormatString(Title)</h3>
Keep reading
Give each document an address of its own.
Read the guideProperties editors set, bound to document fields.
Read the guideModules
The ones marked Built in come with Veva.Web.Essentials. Add the others as packages, restart, and set them up in the site's settings.
Veva.Modules.Tags Predefined tags for any content that takes them, kept in the Tags section, and a Tag List component.
dotnet add package Veva.Modules.TagsVeva.Modules.Documents Models and their documents, in the Documents section. Adds the Document List, Document, Linked documents and Document Form components.
dotnet add package Veva.Modules.DocumentsVeva.Modules.Documents.ModelTemplates Starter models to create a model from: Articles (News) and an Employee list.
dotnet add package Veva.Modules.Documents.ModelTemplatesVeva.Modules.Documents.ViewEndpoints.Standard Serves a model's documents as RSS, XML or JSON, through endpoints set up on the model.
dotnet add package Veva.Modules.Documents.ViewEndpoints.StandardVeva.Modules.Documents.ViewEndpoints.ICAL Serves a model's documents as an iCalendar feed, so events go straight into a calendar.
dotnet add package Veva.Modules.Documents.ViewEndpoints.ICALVeva.Modules.DataSources.Documents Copies data source items into documents and keeps their fields up to date.
dotnet add package Veva.Modules.DataSources.DocumentsMore of Veva
Each one is made of modules. Reference a package, restart, and its components are in the editor.
Compose pages from components, then preview and publish
OpenComponents that show, components that fetch, and the binding between them
OpenDocument forms that save, generic forms that filter or post
OpenForm answers made into a PDF, downloaded or sent to be signed
OpenOne media library, with images sized on request
OpenCrawl, index and search the whole site
OpenThe admin's AI assistant, and the MCP server coding agents connect to
OpenBuildVeva(), modules, components, themes and hooks
OpenPlain .NET Blazor: three render modes, standard components
OpenData sources, sign-in, mail, analytics and media
OpenEvery module: what comes with Essentials, and the add-ons
Open