CMS Kit Menu system allows to manage public menus dynamically.
By default, CMS Kit features are disabled. Therefore, you need to enable the features you want, before starting to use it. You can use the Global Feature system to enable/disable CMS Kit features on development time. Alternatively, you can use the ABP's Feature System to disable a CMS Kit feature on runtime.
Check the "How to Install" section of the CMS Kit Module documentation to see how to enable/disable CMS Kit features on development time.
CMS Kit module admin side adds the following items to the main menu, under the CMS menu item:
- Menus: Menu management page.
CmsKitAdminMenus class has the constants for the menu item names.
Menus page is used to manage dynamic public menus in the system.
The created menu items will be visible on the public-web side, as shown below:
This module follows the Entity Best Practices & Conventions guide.
MenuItem(aggregate root): A Menu Item presents a single node at menu tree.
This module follows the Repository Best Practices & Conventions guide.
Following custom repositories are defined for this feature:
IMenuItemRepository
This module follows the Domain Services Best Practices & Conventions guide.
MenuItemManager is used to perform some operations for the MenuItemManager aggregate root.
MenuItemAdminAppService(implementsIMenuItemAdminAppService): Implements the management operations of menu system.MenuItemPublicAppService(implementsIMenuItemPublicAppService): Implements the public use cases of menu system.
All tables/collections use the Cms prefix by default. Set static properties on the CmsKitDbProperties class if you need to change the table prefix or set a schema name (if supported by your database provider).
This module uses CmsKit for the connection string name. If you don't define a connection string with this name, it fallbacks to the Default connection string.
See the connection strings documentation for details.
- CmsMenuItems
- CmsMenuItems