This module provides Content Management services.

You can access content items from liquid views and templates by using the Content property.
By default, you can retrieve content by alias or content item ID.
Other modules (such as Alias and Autoroute) allow you to retrieve content by other identifiers.

{% assign my_content = Content["alias:main-menu"] %}

Aliases can be in various forms, like when using Autoroute, with the slug prefix.

{% assign my_content = Content["slug:my-blog/my-blog-post"] %}

Aliases are provided by implementing IContentAliasProvider.

You can use the Latest property to retrieve the latest version of a content item (whether that's the published version or the latest draft version) by alias:

{% assign my_content = Content.Latest["alias:main-menu"] %}

{% assign my_content = Content.ContentItemId["417qsjrgv97e74wvp149h4da53"] %}

When a list of content item ids is available, the content_item_id filter should be preferred:

{% assign posts = postIds | content_item_id %}

{% assign my_content = Content.ContentItemVersionId["49gq8g6zndfc736x0az3zsp4w3"] %}

{% contentitem alias:"alias:test" display_type="Detail" %}

The console_log liquid filter can be used to dump data from well known properties, or objects serializable to json, to the browser console.

{{ Model.Content | console_log }}

{{ Model.ContentItem | console_log }}

Well known properties include

• Strings
• JTokens
• Content Items (from the Model.ContentItem property)
• Shapes (from the Model.Content property)
• Objects that can serialize to json.

!!! note To log shapes call {{ Model.Content | console_log }} after calling {{ Model.Content | shape_render }} This will allow the shape to execute, and populate the alternates for any child shapes.

The following methods are available from the Razor helper.

The Razor Helper is accessible on the Orchard property if the view is using Orchard Core's Razor base class, or by injecting OrchardCore.IOrchardHelper in all other cases.

The ConsoleLog extension method can be used to dump data from well known properties, or objects serializable to json, to the browser console.

@Orchard.ConsoleLog(Model.Content as object) noting that we cast to an object, as extension methods do not support dynamic dispatching.

@Orchard.ConsoleLog(Model.ContentItem as object) noting that we cast to an object, as extension methods do not support dynamic dispatching.

Well known properties include

• Strings
• JTokens
• Content Items (from the Model.ContentItem property)
• Shapes (from the Model.Content property)
• Objects that can serialize to json.

!!! note To log shapes call @Orchard.ConsoleLog(Model.Content as object) after calling @await DisplayAsync(Model.Content) This will allow the shape to execute, and populate the alternates for any child shapes.

The contents module provides a feature to provide GraphQL queries for content items. For more information about how to send GraphQL queries, please refer to this section.

You can use content queries to fetch either a single content item, or a list of content items for a certain content type.

Here, we use the blogPost query to fetch a list of BlogPost content items. In the response, we include only the contentItemId and displayText of each BlogPost content item:

query {
  blogPost {
    contentItemId
    displayText
  }
}

We can also query a specific BlogPost content item using the blogPost query. Note that we're using the where argument to select the content item:

query {
  blosPost(where: {
    contentItemId: "417qsjrgv97e74wvp149h4da53"
  }) {
    contentItemId
    displayText
    publishedUtc
  }
}

These fields are available at the content item level:

In addition, all the content parts can also be retrieved like this:

{
  blogPost {
    displayText
    autoroutePart {
      path
    }
  }
}

Different types of query arguments can be composed to filter the results:

• Ordering: Sorting content items by any field value using orderBy
• Filtering: Selecting content items in a query by scalar or relational filters using where
• Pagination: Slicing content items in a query using first and skip

When querying all content items of a type you can supply the orderBy argument for every scalar field of the type: orderBy: { <field>: ASC } or orderBy: { <field>: DESC }.

Order the list of all BlogPost content items ascending by displayText:

query {
  blogPost(orderBy: { displayText: ASC }) {
    contentItemId
    displayText
    publishedUtc
  }
}

Order the list of all BlogPost content items descending by publishedUtc and then ascending by displayText:

query {
  blogPost(orderBy: { publishedUtc: DESC, displayText: ASC  }) {
    contentItemId
    displayText
    publishedUtc
  }
}

The field you are ordering by does not have to be selected in the actual query.

It's also not currently possible to order responses by their parts or custom fields.

When querying all content items of a type you can supply different parameters to the where argument to constrain the data in the response according to your requirements. The available options depend on the scalar and part fields defined on the type in question.

If you supply exactly one parameter to the where argument, the query response will only contain content items that adhere to this constraint.
Multiple filters can be combined using AND and/or OR, see below for more details.

By default only the published content items are returned. You can select either DRAFT, LATEST or ALL versions of a content item.

query {
  blogPost(status: DRAFT) {
    contentItemId
    displayText
    publishedUtc
  }
}

The easiest way to filter a query response is by supplying a concrete value for a certain field to filter by.

Query all BlogPost content items with a specific display text:

query {
  blogPost(where: {
    displayText: "About"
  }) {
    contentItemId
  }
}

Depending on the type of the field you want to filter by, you have access to different advanced criteria you can use to filter your query response.

Query all BlogPost content items whose displayText is in a given list of strings:

query {
  blogPost(where: {
    displayText_in: ["My biggest Adventure", "My latest Hobbies"]
  }) {
    contentItemId
    displayText
    publishedUtc
  }
}

Query all BlogPost content items whose creation date is less than a specific date:

query {
  blogPost(where: {
    creationgUtc_lt: "2011-11-13T07:45:00"
  }) {
    contentItemId
    displayText
    publishedUtc
  }
}

For content parts, you can define conditions on the part by nesting the according argument in where.

Query all BlogPost content items where the autoroutePart has a specific value in its path:

query {
  blogPost(where: {
    autoroutePart {
      path_contains: "/about"
    }
  }) {
    contentItemId
    displayText
    publishedUtc
  }
}

You can use the filter combinators OR, AND and NOT to create an arbitrary logical combination of filter conditions:

For an AND-filter to evaluate to true, all of the nested conditions have to be true. For an OR-filter to evaluate to true, at least one of the nested conditions has to be true. For a NOT-filter to evaluate to true, all of the nested conditions have to be false. Using OR, AND and NOT

Let's start with an easy example:

Query all BlogPost content items that are created in 2018 and whose displayText is in a given list of strings:

query {
  blogPost(where: {
    AND: {
      displayText_in: ["My biggest Adventure", "My latest Hobbies"]
    }, {
      publishedUtc_gt: "2018"
    }
  }) {
    contentItemId
    displayText
    publishedUtc
  }
}

You can combine and even nest the filter combinators AND, OR and NOT to create arbitrary logical combinations of filter conditions.

Query all BlogPost content items that are created in 2018 and whose displayText is in a given list of strings, or have the specific contentItemId we supply:

query {
  blogPost(where: {
    OR: {
      AND: {
        displayText_in: ["My biggest Adventure", "My latest Hobbies"],
        publishedUtc_gt: "2018"
      },

      contentItemId: "417qsjrgv97e74wvp149h4da53"
    }
  }) {
    contentItemId
    displayText
    publishedUtc
  }
}

Notice how we nest the AND combinator inside the OR combinator.

When querying all content items of a specific content type, you can supply arguments that allow you to paginate the query response.

To limit the number of results, use first.

To skip a number of results, use skip.

Query the first 3 content items:

query {
  posts(first: 3) {
    contentItemId
    displayText
    publishedUtc
  }
}

Query the content items from position 6 to position 10:

query {
  posts(
    first: 5
    skip: 5
  ) {
    contentItemId
    displayText
    publishedUtc
  }
}