This module follows the [module development best practices guide](https://docs.abp.io/en/abp/latest/Best-Practices/Index) and consists of several NuGet and NPM packages. See the guide if you want to understand the packages and relations between them.
CMS kit packages are designed for various usage scenarios. When you visit the [CMS kit package list page](https://www.nuget.org/packages?q=Volo.CmsKit), you will see that packages have admin, public and unified versions:
CMS kit packages are designed for various usage scenarios. If you check the [CMS kit packages](https://www.nuget.org/packages?q=Volo.CmsKit), you will see that some packages have `Admin` and `Public` suffixes. The reason is that the module has two application layers, considering they might be used in different type of applications. These application layers uses a single domain layer.
- `Volo.CmsKit.Admin.*` packages contain the functionalities required by admin (back office) applications.
- `Volo.CmsKit.Public.*` packages contain the functionalities used in public websites where users read blog posts or leave comments.
@ -59,7 +59,7 @@ CMS kit packages are designed for various usage scenarios. When you visit the [C
### Menu items
CMS kit module adds the following items to the "Main" menu, under the "CMS" menu item:
CMS Kit module admin side adds the following items to the main menu, under the *CMS* menu item:
* **Pages**: Page management page.
* **Blogs**: Blog management page.
@ -75,11 +75,11 @@ CMS kit module adds the following items to the "Main" menu, under the "CMS" menu
Pages page is used to manage dynamic pages in the system.
You can create and edit an existing blog post on this page. If you enable specific features such as tags, you can set tags for the blog post on this page.
CMS Kit provides an extensible reaction component system to allow users to send reactions to your content. Here how the reactions component looks on a sample page.