From 12677ce9fe76de1c061c0285f54e3724f7b95afe Mon Sep 17 00:00:00 2001
From: Enis Necipoglu <iletisim@enisnecipoglu.com>
Date: Tue, 26 Sep 2023 15:45:39 +0300
Subject: [PATCH] Revert "Update CMS-Kit docs"

This reverts commit 8cec189c5133e8c61cbdbd4a4b69695c20c9b49f.
---
 docs/en/Modules/Cms-Kit/Index.md | 35 +++++++++++++++-----------------
 docs/en/Modules/Cms-Kit/Pages.md | 11 ----------
 2 files changed, 16 insertions(+), 30 deletions(-)

diff --git a/docs/en/Modules/Cms-Kit/Index.md b/docs/en/Modules/Cms-Kit/Index.md
index 70311e9595..ddf43205a5 100644
--- a/docs/en/Modules/Cms-Kit/Index.md
+++ b/docs/en/Modules/Cms-Kit/Index.md
@@ -38,27 +38,24 @@ abp add-module Volo.CmsKit --skip-db-migrations
 
 > 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.
+```csharp
+GlobalFeatureManager.Instance.Modules.CmsKit(cmsKit =>
+{
+    cmsKit.EnableAll();
+});
+```
 
-    ```csharp
-    GlobalFeatureManager.Instance.Modules.CmsKit(cmsKit =>
-    {
-        cmsKit.EnableAll();
-    });
-    ```
-
-    - 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:
-        ```csharp
-        GlobalFeatureManager.Instance.Modules.CmsKit(cmsKit =>
-        {
-            cmsKit.Tags.Enable();
-            cmsKit.Comments.Enable();
-        });
-        ```
-
-- 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:
+
+````csharp
+GlobalFeatureManager.Instance.Modules.CmsKit(cmsKit =>
+{
+    cmsKit.Tags.Enable();
+    cmsKit.Comments.Enable();
+});
+````
 
 > If you are using Entity Framework Core, do not forget to add a new migration and update your database.
 
diff --git a/docs/en/Modules/Cms-Kit/Pages.md b/docs/en/Modules/Cms-Kit/Pages.md
index 4860c3938d..cc1f5074f4 100644
--- a/docs/en/Modules/Cms-Kit/Pages.md
+++ b/docs/en/Modules/Cms-Kit/Pages.md
@@ -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.
-
 ## The User Interface
 
 ### Menu items