The Resources module provides commonly used resources like JavaScript libraries and CSS files. It also enables the Resource Manager so any module can describe what resources are necessary on any page or component. When the full page is rendered all the required resources are computed and custom <script> and <link> tags are rendered accordingly. You can also register custom <meta> tags.

Resources will be served via the StaticFileMiddleware from either a module or themes wwwroot folder. When defining a resource the naming convention is ~/ThemeName/scripts/path-to-file.js or ~/Module.Name/styles/path-to-file.css

The tilde (~) is a convention used to indicate a relative path, for example a tenant base path. All script or stylesheet resources should be prefixed with the ~ character.

Resource Settings are configured through the site admin.

Enabling AppendVersion or Resources cache busting will automatically append a version hash to all local scripts and style sheets. This is turned on by default.

Enabling UseCdn will configure the IResourceManager to provide any scripts or styles, such as jQuery, from the configured CDN.

When enabled will serve scripts or styles, that have a CDN configured, or a debug-src, from the local server in non minified format.
This will also disabled the CdnBaseUrl prepending.

When supplied this will prepend local resources served via the IResourceManager or Tag Helpers with the absolute url provided. This will be disabled in ResourceDebugMode

Named resources are well-known scripts and stylesheets that are described in a module or theme.
They have a name, a type (script, stylesheet) and optionally a version.
The OrchardCore.Resources module provides some commonly used ones:

Named resources are registered by implementing the IResourceManifestProvider interface.

This example is provided from TheBlogTheme to demonstrate.

public class ResourceManifest : IResourceManifestProvider
{
    public void BuildManifests(IResourceManifestBuilder builder)
    {
        var manifest = builder.Add();

        manifest
            .DefineScript("TheBlogTheme-vendor-jQuery")
            .SetUrl("~/TheBlogTheme/vendor/jquery/jquery.min.js", "~/TheBlogTheme/vendor/jquery/jquery.js")
            .SetCdn("https://code.jquery.com/jquery-3.4.1.min.js", "https://code.jquery.com/jquery-3.4.1.js")
            .SetCdnIntegrity("sha384-vk5WoKIaW/vJyUAd9n/wmopsmNhiy+L2Z+SBxGYnUkunIxVxAv/UtMOhba/xskxh", "sha384-mlceH9HlqLp7GMKHrj5Ara1+LvdTZVMx4S1U43/NxCvAkzIo8WJ0FE7duLel3wVo")
            .SetVersion("3.4.1");
        }
    }

In this example we define a script with the unique name TheBlogTheme-vendor-jQuery. We use a name that is unique to TheBlogTheme to prevent collisions when multiple themes are active.

We set a url for the minified version, and the unminified version, which will be used in ResourceDebugMode. For the same reason we define two CDN Url's, which will be preferred over the local urls if the UseCdn setting in the site admin is set. We set the Cdn Integrity Hashes and the version to 3.4.1

This script will then be available for the tag helper or API to register by name.

!!! note "Registration" Make sure to register this IResourceManifestProvider in the Startup or your theme or module. serviceCollection.AddScoped<IResourceManifestProvider, ResourceManifest>();

There are two ways to invoke a resource: either by using the IResourceManager API or a Tag Helper.
The API is necessary if you need to inject a resource from code, however it is recommended to use a Tag Helper when inside a view.

From your module, add a reference to the OrchardCore.Resources.Abstractions project.
From the class you want to use the API in, inject the OrchardCore.ResourceManagement.IResourceManager interface.

var settings = _resourceManager.RegisterResource("script", "bootstrap")

The result of this call is an object of type RequireSettings that is used to pass more parameters to the required resource.

settings.AtHead();

settings.AtFoot();

settings.UseVersion("3.3");

This will use the latest available version between 3.3 and 3.4. If the version is not available an exception is thrown.

settings.UseAppendVersion(true);

This will append a version string that is calculated at runtime as an SHA256 hash of the file, the calculation cached, and appended to the url as part of the query string, e.g. my-script.js?v=eER9OO6zWGKaIq1RlNjImsrWN9y2oTgQKg2TrJnDUWk

At the beginning of the HTML document:

resourceManager.RegisterHeadScript(new HtmlString("<script>alert('Hello')</script>"));

At the end of the HTML document:

resourceManager.RegisterFootScript(new HtmlString("<script>alert('Hello')</script>"));

resourceManager.RegisterMeta(new MetaEntry { Content = "Orchard", Name = "generator" });

You can also add more content to an existing tag like this:

resourceManager.AppendMeta(new MetaEntry { Name = "keywords", Content = "orchard" }, ",");

From your module, in the _ViewImports.cshtml or your view, add @addTagHelper *, OrchardCore.ResourceManagement.

This example registers the script named bootstrap and all its dependencies (jquery).

{% script name:"bootstrap" %}

<script asp-name="bootstrap"></script>

And for a stylesheet:

<style asp-name="bootstrap"></style>

You can force a resource to be used from its CDN. By default the behavior is defined by configuration.

{% script name:"bootstrap", use_cdn:"true" %}

<script asp-name="bootstrap" use-cdn="true"></script>

This example will use the latest available version with a Major version of 3, like 3.4.0. If the version is not specified the latest one is always used.

{% script name:"bootstrap", version:"4" %}

<script asp-name="bootstrap" version="3"></script>

You can append a version hash that will be calculated, and calculation cached, and appended in the format ?v=eER9OO6zWGKaIq1RlNjImsrWN9y2oTgQKg2TrJnDUWk

{% script name:"bootstrap", append_version:"true" %}

<script asp-name="bootstrap" asp-append-version="true"></script>

By default all scripts are rendered in the footer. You can override it like this:

{% script name:"bootstrap", at:"Foot" %}

<script asp-name="bootstrap" at="Foot"></script>

Styles, however, are always injected in the header section of the HTML document.

You can declare a new resource directly from a view, and it will be injected only once even if the view is called multiple time.

{% script name:"foo", src:"~/TheTheme/js/foo.min.js", debug_src:"~/TheTheme/js/foo.js", depends_on:"jQuery", version:"1.0" %}
{% script name:"bar", src:"~/TheTheme/js/bar.min.js", debug_src:"~/TheTheme/js/bar.js", depends_on:"foo:1.0", version:"1.0" %}

<script asp-name="foo" asp-src="~/TheTheme/js/foo.min.js?v=1.0" debug-src="~/TheTheme/js/foo.js?v=1.0" depends-on="jQuery" version="1.0"></script>
<script asp-name="bar" asp-src="~/TheTheme/js/bar.min.js?v=1.0" debug-src="~/TheTheme/js/bar.js?v=1.0" depends-on="foo:1.0" version="1.0"></script>

We define a script named foo with a dependency on jQuery with the version 1.0.

We then define a script named bar which also takes a dependency on version 1.0 of the foo script.

If the version was not set the one with the highest number would be used.

When rendering the scripts the resource manager will order the output based on the dependencies, regardless of the order they are written to:

1. jQuery
2. foo
3. bar

You can also do the same for a stylesheet:

{% style name:"bar", src:"~/TheTheme/css/bar.min.css", debug_src:"~/TheTheme/css/bar.css", depends_on:"foo" %}
{% style name:"foo", src:"~/TheTheme/css/foo.min.css", debug_src:"~/TheTheme/css/foo.css", depends_on:"bootstrap" %}

<style asp-name="bar" asp-src="~/TheTheme/css/bar.min.css" debug-src="~/TheTheme/css/bar.css" depends-on="foo"></style>
<style asp-name="foo" asp-src="~/TheTheme/css/foo.min.css" debug-src="~/TheTheme/css/foo.css" depends-on="bootstrap"></style>

In this example define a style named bar with a dependency on the style named foo

We then define the style named foo

When rendering the scripts the resource manager will order the output based on the dependencies, regardless of the order they are written to:

1. bootstrap
2. foo
3. bar

!!! note You do not have to define a name for your script or style unless you want to reference it as a dependency.

The following example demonstrates how to inject a custom script in the footer section.

{% scriptblock at: "Foot" %}
    document.write('<!-- some script -->');
{% endscriptblock %}

<script at="Foot">
    document.write('<!-- some script -->');
</script>

You can also inject a named custom script.

{% scriptblock name: "Carousel", at: "Foot", depends_on:"jQuery" %}
    document.write('<!-- some script -->');
{% endscriptblock %}

<script name="Carousel" at="Foot" depends-on="jQuery">
    document.write('<!-- some script -->');
</script>

Named script will only be injected once and can optionally specify dependencies.

The following example demonstrates how to inject a custom style in the head section. The style block will be injected after all stylesheet resources.

{% styleblock at: "Head" %}
    .my-class {
        /* some style */
    }
{% endstyleblock %}

<style at="Head">
    .my-class {
        /* some style */
    }
</style>

You can also inject a named style block. The style block will only be injected once based on its name and can optionally specify dependencies.

{% styleblock name: "my-style", depends_on:"the-theme" %}
    .my-class {
        /* some style */
    }
{% endscriptblock %}

<style name="my-style" depends-on="the-theme">
    .my-class {
        /* some style */
    }
</style>

{% meta name:"description", content:"This is a website" %}

<meta asp-name="description" content="This is a website" />

These properties are available:

Your Layout.cshtml or Layout.liquid must make a call to the resource manager to render resources that have been registered.

These are generally rendered at the lower portion of the <head> section.

<head>
    ...
    {% resources type: "Meta" %}
    {% resources type: "HeadLink" %}
    {% resources type: "HeadScript" %}
    {% resources type: "Stylesheet" %}
</head>    

<head>
    ...
    <resources type="Meta" />
    <resources type="HeadLink" />
    <resources type="HeadScript" />
    <resources type="Stylesheet" />
</head>

These should be rendered at the bottom of the <body> section.

<body>
    ...
    {% resources type: "FootScript" %}
</body>    

<body>
    ...
    <resources type="FootScript" />
</body>

If you register a resource by name and it is not found this will be logged as an error in your App_Data/Logs folder.