Added new KB

docs/en/kb/can-not-login-with-admin-user.md

@@ -1,4 +1,4 @@
-# Problem: Can not login with the admin user
+# KB#0003: Can not login with the admin user
 
 * Try username `admin` and Password `1q2w3E*`.
 * Try to migrate database. If you have a `DbMigrator` application in your solution, use it. It will seed initial data and create the admin user for you.

docs/en/kb/index.md

@@ -2,6 +2,6 @@
 
 The following documents provide useful information about several topics you might need to know.
 
-* [How to Fix "Filename too long" Error on Windows](windows-path-too-long-fix.md)
-* [Problem: Can not login with the admin user](can-not-login-with-admin-user.md)
-* [When to Use a Distributed Cache Server](when-to-use-a-distributed-cache-server.md)
+* KB#0001: ["Filename too long" error on Windows](windows-path-too-long-fix.md)
+* KB#0003: [Can not login with the admin user](can-not-login-with-admin-user.md)
+* KB#0002: [When to use a distributed cache server](when-to-use-a-distributed-cache-server.md)

docs/en/kb/when-to-use-a-distributed-cache-server.md

@@ -1,4 +1,4 @@
-# When to Use a Distributed Cache Server
+# KB#0002: When to Use a Distributed Cache Server
 
 ABP provides a [distributed cache service](../framework/fundamentals/caching.md) that is based on [ASP.NET Core's distributed cache](https://docs.microsoft.com/en-us/aspnet/core/performance/caching/distributed). This document explains when you need to have a separate cache server for your applications.
 

docs/en/kb/windows-path-too-long-fix.md

@@ -1,4 +1,4 @@
-# How to Fix "Filename too long" Error on Windows
+# KB#0001: How to Fix "Filename too long" Error on Windows
 
 If you encounter the "filename too long" or "unzip" error on Windows, it's probably related to the Windows maximum file path limitation. Windows has a maximum file path limitation of 255 characters.