diff --git a/docs/en/solution-templates/layered-web-application/images/web-applications.png b/docs/en/solution-templates/layered-web-application/images/web-applications.png
new file mode 100644
index 0000000000..e39b800c12
Binary files /dev/null and b/docs/en/solution-templates/layered-web-application/images/web-applications.png differ
diff --git a/docs/en/solution-templates/layered-web-application/web-applications.md b/docs/en/solution-templates/layered-web-application/web-applications.md
new file mode 100644
index 0000000000..8ade995dc2
--- /dev/null
+++ b/docs/en/solution-templates/layered-web-application/web-applications.md
@@ -0,0 +1,16 @@
+# Layered Solution: Web Applications
+
+The web applications are the main user interfaces of the solution. They are the entry points for users to interact with the system. The Layered Solution Template supports the following web applications:
+
+- **MVC / Razor Pages**: This is an ASP.NET Core MVC application. It is a traditional web application that serves HTML pages to users and is suitable for building web applications with server-side rendering.  
+- **Angular**: This is an Angular application, a single-page application (SPA) that runs on the client side. It communicates with the server using HTTP requests and is ideal for building modern web applications with rich user interfaces.  
+- **Blazor UI**: A flexible framework for building web applications with .NET. It supports various hosting models:
+  - **Blazor WebAssembly**: This is a client-side SPA that runs entirely in the user's browser. It communicates with the server using HTTP requests and is suitable for modern web applications with rich interactivity and offline capabilities.  
+  - **Blazor Server**: This is a server-side SPA that runs on the server and communicates with the client in real time using SignalR. It is ideal for applications requiring constant connectivity and rapid server updates.  
+  - **Blazor WebApp**: This is a combination of Blazor technologies optimized for building hybrid web applications that can leverage both client-side and server-side capabilities.  
+  - **Maui Blazor (Hybrid)**: This enables building cross-platform applications that combine Blazor for the UI with .NET MAUI for native device integration. It is suitable for building apps that work across desktop and mobile platforms.  
+- **No UI**: This option creates a backend-only solution without a web interface, suitable for scenarios like API-only applications or headless services.  
+
+You can select the web application type that fits your requirements during the solution creation process in the *UI Framework* step. The Layered Solution Template generates the selected web applications with the necessary configurations and integrations.
+
+![Web Applications](images/web-applications.png)