Content Fields (OrchardCore.ContentFields)Link


This modules provides common content fields.

Available FieldsLink

Name Properties Shape Type Shape Class
BooleanField Value (bool) BooleanField DisplayBooleanFieldViewModel
DateField Value (DateTime?) DateField DisplayDateFieldViewModel
DateTimeField Value (DateTime?) DateTimeField DisplayDateTimeFieldViewModel
HtmlField Html (string) HtmlField DisplayHtmlFieldViewModel
LinkField Url (string), Text (string) LinkField DisplayLinkFieldViewModel
NumericField Value (decimal?) NumericField DisplayNumericFieldViewModel
TextField Text (string) TextField DisplayTextFieldViewModel
TimeField Value (TimeSpan?) TimeField DisplayTimeFieldViewModel


From a Content template, you can reference a field's value like this (if the content type is Article and has a Text Field named MyField):

var fieldValue = Model.ContentItem.Content.Article.MyField.Text;
{{ Model.ContentItem.Content.Article.MyField.Value }}

From a field shape (see Shape Type in the table listing all the fields) you can also access properties specific to each view model.

Common field propertiesLink

The convention for a field view model is to also expose these properties:

Property Description
Field The ContentField.
Part The ContentPart that contains the field.
ContentPartFieldDefinition The Content Part Field Definition that contains the part. Which also give access to the Content Type

Some view models have special properties that are computed from the actual field data and which are more useful for templating.


Property Description
Html The processed Html once all liquid tags are processed.

HtmlField ExampleLink

{{ Model.Html }}

or, to display the raw content before the tags are converted:

{{ Model.Field.Html }}


Property Description
LocalDateTime The date time in the time zone of the site.

DateTimeField ExampleLink

{{ Model.LocalDateTime }}

or, to display the UTC value before is it converted:

{{ Model.Field.Value }}

Creating Custom FieldsLink

What to extendLink

Before creating a new field the solution might be to provide a custom editor and formatter instead.

A field should represent some specific physical data and logical data. The same field can be customized to be edited and rendered differently using both Editors and Formatters. Editors are shapes that can be used to edit a field differently, for instance the WYSIWYG HTML editor is a custom editor for the HTML field. Formatters are alternate shapes that can be used to render a field on the front end, for instance a Link field could be rendered as a Youtube video player.

Model ClassLink

Create a class inheriting from ContentField that will represent the state of your field. Its content will be serialized as part of the content item. Json.NET classes can be used to customize the serialization.


public class TextField : ContentField
    public string Text { get; set; }

This class needs to be registered in the DI like this:

services.AddSingleton<ContentField, TextField>();

Display DriverLink

The display driver is the component that drives how the field is displayed on the front end, edited on the admin, updated and validated.

Create a class inheriting from ContentFieldDisplayDriver<TextField> and implement the three methods Display, Edit and DisplayAsync by looking at examples from this module.

This class needs to be registered in the DI like this:

services.AddScoped<IContentFieldDisplayDriver, TextFieldDisplayDriver>();

Creating Custom EditorsLink

For each field, the convention is to create an alternate that can target different editors. To provide a new choice in the list of available editors for a field, create a new shape template that matches this template: {FIELDTYPE}_Option__{EDITORNAME} This shape type will match a template file named {FIELDTYPE}-{EDITORNAME}.Option.cshtml

This template will need to render an <option> tag. Here is an example for a Wysiwyg options on the Html Field:

    string currentEditor = Model.Editor;
<option value="Wysiwyg" selected="@(currentEditor == "Wysiwyg")">@T["Wysiwyg editor"]</option>

Then you can create the editor shape by adding a file named {FIELDTYPE}_Editor__{EDITORNAME} which is represented by a template file named {FIELDTYPE}-{EDITORNAME}.Editor.cshtml.

For instance the filename for the Wysiwyg editor on the Html Field is named HtmlField-Wysiwyg.Editor.cshtml.


Copyright (c) 2017 Kyle Kemp, Rohit Kalkur, and contributors
License: MIT

Bootstrap SwitchLink
Copyright (c) 2013-2015 The authors of Bootstrap Switch
License: MIT