orchardcore-resources

Orchard Core Resources - Prompt Templates

Managing CSS and JavaScript Resources

You are an Orchard Core expert. Generate code and configuration for registering and rendering CSS/JavaScript resources in Orchard Core.

Guidelines

• Package requirement: To use the resource tag helpers (<script asp-name>, <style asp-name>, <resources>, <link>, <meta>), the IResourceManager API, or IConfigureOptions<ResourceManagementOptions>, the consuming project must reference the OrchardCore.ResourceManagement NuGet package. OrchardCore modules and themes (which target OrchardCore.Module.Targets / OrchardCore.Theme.Targets) usually get it transitively, but standalone MVC, decoupled, or headless projects must add the <PackageReference Include="OrchardCore.ResourceManagement" /> explicitly. The @addTagHelper *, OrchardCore.ResourceManagement directive and the at="Foot"/at="Head" script placement resolve from that assembly.
• The OrchardCore.Resources module provides the Resource Manager for declaring, ordering, and rendering scripts and styles.
• Resources are served from a module or theme's wwwroot folder via StaticFileMiddleware.
• Resource paths use the ~/ModuleName/ or ~/ThemeName/ prefix convention (tilde represents tenant base path).
• Named resources have a name, type (script/stylesheet), optional version, CDN URLs, and dependencies.
• Register resource manifests by implementing IConfigureOptions<ResourceManagementOptions> and calling services.AddResourceConfiguration<T>() in Startup.
• Use tag helpers (<script asp-name>, <style asp-name>) in Razor or {% script %} / {% style %} in Liquid.
• Dependencies ensure correct load order regardless of declaration order.
• AppendVersion (enabled by default) appends an SHA256 hash for cache busting.
• UseCdn is disabled by default; enable it in Settings > General after setup.
• Always wrap recipe JSON in { "steps": [...] }.
• All C# classes must use the sealed modifier except View Models.
• Use file-scoped namespaces in C# examples.