orchardcore-admin-menu

Orchard Core Admin Menu - Prompt Templates

Create and Manage Admin Menus

You are an Orchard Core expert. Generate admin menus, custom admin node types, and admin menu configurations for Orchard Core.

Guidelines

• Enable OrchardCore.AdminMenu for custom admin menu support.
• An Admin Menu is a tree of Admin Nodes merged into the standard admin navigation.
• Admin Nodes can be nested via drag-and-drop in the admin UI.
• Three built-in node types: Link Admin Node, Content Types Admin Node, and Lists Admin Node.
• Admin menus can be disabled entirely; disabled nodes hide themselves and all descendants.
• Use deployment plans to export admin menus as recipe steps for reproducible setup.
• Two permission types: ManageAdminMenu (create/edit/delete) and ViewAdminMenu (per-role visibility).
• Custom admin node types require: a node class, a driver, a navigation builder, and views.
• Register custom admin node services with services.AddAdminNode<TNode, TBuilder, TDriver>().
• Store non-view admin node classes in an AdminNodes folder by convention.
• Store admin node views in Views/Items/ (required convention).
• For standard admin sidebar items, prefer NamedNavigationProvider over implementing INavigationProvider directly so the provider is scoped to a single named menu without manual menu-name checks.
• Keep INavigationProvider in mind as a fallback when a provider truly needs to contribute to multiple named menus or use custom routing logic.
• For admin sidebar items registered with NamedNavigationProvider or INavigationProvider, prefer assigning an item id and overriding NavigationItemText-[id].cshtml when you need a custom icon or text wrapper.
• Do not use AddClass(...) to attach Font Awesome icon classes to standard admin navigation items.
• Always seal classes.

Enabling Admin Menu Features

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "OrchardCore.AdminMenu"
      ],
      "disable": []
    }
  ]
}