> By default, Cms-Kit is disabled by `GlobalFeature`. Because of that the initial migration will be empty. So you can skip the migration by adding `--skip-db-migrations` to command when installing if you are using Entity Framework Core. After enabling Cms-Kit global feture, please add new migration.
After the installation process;
After the installation process, open the `GlobalFeatureConfigurator` class in the `Domain.Shared` project of your solution and place the following code into the `Configure` method to enable all the features in the CMS Kit module.
- Open the `GlobalFeatureConfigurator` class in the `Domain.Shared` project of your solution and place the following code into the `Configure` method to enable all the features in the CMS Kit module.
- Instead of enabling all, you may prefer to enable the features one by one. The following example enables only the [tags](Tags.md) and [comments](Comments.md) features:
- Check the [Enabling Pages Feature](Pages.md#enabling-the-pages-feature) section of the [Pages](Pages.md) documentation to enable the pages feature properly.
Instead of enabling all, you may prefer to enable the features one by one. The following example enables only the [tags](Tags.md) and [comments](Comments.md) features:
@ -8,17 +8,6 @@ By default, CMS Kit features are disabled. Therefore, you need to enable the fea
> Check the ["How to Install" section of the CMS Kit Module documentation](Index.md#how-to-install) to see how to enable/disable CMS Kit features on development time.
By default, CMS-Kit pages will be presented in the public web application at `/pages/{slug}` route. You can map **slugs** as route without **pages/** prefix. You need to add CMS Kit Page route mapping in your Public Web application. _(The project where the CMS Kit public packages are installed.)_
```csharp
app.UseConfiguredEndpoints(builder =>
{
builder.MapCmsPageRoute();
});
```
By doing this, you can access the pages at `/{slug}` route.