Update documentation for .NET 10.0 compatibility and improve formatting

- Changed references from .NET 9.0 to .NET 10.0 across multiple documentation files.
- Updated code block formatting for consistency (bash and json).
- Enhanced clarity in installation instructions and prerequisites.
- Improved overall structure and organization of content for better readability.
- Updated version numbers in package.json and layout files.
- Added a new agent documentation for writing software documentation.

Author: giovanninocco

.github/agents/Documentation Writer.agent.md

@@ -0,0 +1,12 @@
+---
+description: 'You are an experiences copy writer specialized in writing software documentation'
+tools: []
+---
+You are an experiences copy writer specialized in writing software documentation. Your task is to create clear, concise, and user-friendly documentation for software products, APIs, and libraries. You should be able to explain complex technical concepts in a way that is easy to understand for both technical and non-technical audiences.
+
+When writing documentation, consider the following best practices:
+1. **Audience Understanding**: Tailor the content to the target audience's technical level and needs.
+2. **Clarity and Conciseness**: Use simple language, avoid jargon, and keep sentences and paragraphs short.
+3. **Structure and Organization**: Use headings, subheadings, bullet points, and numbered lists to organize content logically.
+4. **Examples and Code Snippets**: Include practical examples and code snippets to illustrate concepts and usage.
+5. **Visual Aids**: Use diagrams, screenshots, and other visual aids to enhance understanding.

README.md

@@ -5,49 +5,66 @@
 [![Netlify Status](https://api.netlify.com/api/v1/badges/6dbb93bc-ad39-4fda-849a-e542abdcfa7c/deploy-status)](https://app.netlify.com/sites/genocs-blog/deploys)
 
 <p align="center">
-    <img src="genocs-framework.png" alt="icon">
+    <img src="./assets/images/gnx-framework.png" alt="Genocs Framework" width="400"/>
 </p>
 
 ## How to contribute?
 
 1. Fork this Repository.
-2. Navigate to your newly forked Repository -> Settings -> Secrets.
+2. Navigate to your newly forked `Repository -> Settings -> Secrets`.
 3. Here, Add a new Repository Secret with a name `GT_TOKEN`. As for the value, paste in your GitHub Token (https://github.com/settings/tokens)
 4. Now, clone this repository locally.
-5. Ensure that you have Node.js and Visual Code installed.
-6. At the root of the repository run `npm install`. This installs all the required packages.
-7. All the documentations are to be written in markdown format.
+5. Ensure that you have Node.js and VS Code installed.
+6. At the root of the repository run `npm install` (This installs all the required packages).
+7. All the documentations is written in markdown format.
 8. Refer https://github.com/Genocs/genocs-library-docs/blob/main/content/en/templates/general/getting-started/index.md to get an idea on how to write documentation and include images, code snippets and stuff.
 9. To run the application locally, run the command `npm run start` and navigate to localhost:1313
 10. Once ready, send a Pull Request.
 
 
+# How to build and run locally
+
+1. Clone the repository
+2. Run the following commands to build and run the application locally
+   ```bash
+   # install dependencies
+   npm install
+   # build the application release version
+   npm run clean && npm run build
+   # run the application locally
+   npm run start
+   ```
+3. Navigate to localhost:1313 to view the documentation
+
 # How to build and run on Docker
 
 1. Clone the repository
 2. Run the following command to build the docker image
-    ```bash
-    # build the application release version
-    npm run clean && npm run build
+   ```bash
+   # build the application release version
+   npm run clean && npm run build
 
-    # build the docker image
-    docker build -t genocs/genocs-library-docs .
+   # build the docker image
+   docker build -t genocs/genocs-library-docs .
 
-    # tag the image
-    docker tag genocs/genocs-library-docs genocs/genocs-library-docs:1.2.1
-    docker tag genocs/genocs-library-docs genocs/genocs-library-docs:latest
+   # tag the image
+   docker tag genocs/genocs-library-docs genocs/genocs-library-docs:1.3.0
+   docker tag genocs/genocs-library-docs genocs/genocs-library-docs:latest
+
+   # build and tag in a single command
+   docker build -t genocs/genocs-library-docs:latest -t genocs/genocs-library-docs:1.3.0 .
 
-    # login to docker hub
-    docker login
+   # login to docker hub
+   docker login
 
-    # push the image to docker hub
-    docker push genocs/genocs-library-docs:1.2.1
-    docker push genocs/genocs-library-docs:latest
-    ```
+   # push the image to docker hub
+   docker push genocs/genocs-library-docs:1.3.0
+   docker push genocs/genocs-library-docs:latest
+   ```
 3. Run the following command to run the docker image on localhost:1613
-    ```bash
-    docker run -d -p 1613:80 genocs/genocs-library-docs
-    ```
+   ```bash
+   docker run -d -p 1613:80 genocs/genocs-library-docs
+   ```
 4. Navigate to localhost:1613 to view the documentation
 
 

config/_default/params.toml

@@ -69,7 +69,7 @@ copyRight = "Copyright (c) 2025 Genocs"
 # Alert
 alert = true
 alertDismissable = false
-alertText = ".NET 9.0 Genocs Library Released <a target=\"_blank\" class=\"alert-link\" href=\"https://www.youtube.com/watch?v=TgxDvU---Ak/\">Click here to get started!</a>"
+alertText = ".NET10.0 Genocs Library Released <a target=\"_blank\" class=\"alert-link\" href=\"https://www.youtube.com/watch?v=TgxDvU---Ak/\">Click here to get started!</a>"
 
 # Edit Page
 repoHost = "GitHub"

content/en/blog/auth/index.md

@@ -1,7 +1,7 @@
 ---
 title: "Authentication & Authorization"
-description: ".NET 9.0 - Boilerplate API Tutorial with Email Sign Up, Verification, Authentication & Forgot Password"
-lead: "Introducing about how to use authentication and authorization with NET9."
+description: ".NET10.0 - Boilerplate API Tutorial with Email Sign Up, Verification, Authentication & Forgot Password"
+lead: "Introducing about how to use authentication and authorization with NET10.0."
 date: 2024-12-09T00:00:00+02:00
 lastmod: 2024-12-09T00:00:00+02:00
 draft: false
@@ -22,7 +22,7 @@ Authentication is implemented with JWT access tokens and refresh tokens. On succ
 HTTP Only cookies are used for refresh tokens to increase security because they are not accessible to client-side javascript which prevents XSS (cross site scripting) attacks. Refresh tokens only have access to generate new JWT tokens (via the */accounts/refresh-token route*), they cannot perform any other secure action which prevents them from being used in CSRF (cross site request forgery) attacks.
 
 ### API endpoints
-The example .NET9 API has the following endpoints/routes to demonstrate email sign up and verification, authentication and role based autorization, refreshing and revoking tokens, forgot password and reset password, and secure account management routes:
+The example .NET10.0 API has the following endpoints/routes to demonstrate email sign up and verification, authentication and role based autorization, refreshing and revoking tokens, forgot password and reset password, and secure account management routes:
 
 - POST `/accounts/authenticate` - public route that accepts POST requests containing an email and password in the body. On success a JWT access token is returned with basic account details, and an HTTP Only cookie containing a refresh token.
 - POST `/accounts/refresh-token` - public route that accepts POST requests containing a cookie with a refresh token. On success a new JWT access token is returned with basic account details, and an HTTP Only cookie containing a new refresh token (see refresh token rotation just below for an explanation).
@@ -52,8 +52,8 @@ To try to keep things simple the boilerplate API uses a SQLite database, SQLite
 The boilerplate API project is available on GitHub at https://github.com/cornflourblue/dotnet-6-signup-verification-api.
 
 
-Tools required to run the .NET 6.0 Tutorial Example Locally
-To develop and run .NET 6.0 applications locally, download and install the following:
+Tools required to run the .NET10.0 Tutorial Example Locally
+To develop and run .NET10.0 applications locally, download and install the following:
 
 .NET SDK - includes the .NET runtime and command line tools
 Visual Studio Code - code editor that runs on Windows, Mac and Linux

content/en/cli/index.md

@@ -18,15 +18,7 @@ Genocs tool is based on [Microsoft-dotnet tools](https://learn.microsoft.com/en-
 
 ## Supported runtime
 
-Genocs CLI can be used on both .NET6|8|9.
-
----
-
-## Visual Studio Integration
-
-The Genocs CLI is integrated with Visual Studio. You can use the Genocs CLI to create, build, and run applications directly from Visual Studio. The Genocs CLI provides a unified experience across different platforms, allowing you to create cross-platform applications with ease. You can use the Genocs CLI to automate tasks such as project management, dependency resolution, and deployment. The Genocs CLI is an essential tool for modern developers, offering productivity, flexibility, and scalability in application development.
-
-{{< img src="vs_integration.png" >}}
+Genocs CLI can be used on both .NET10.x, .NET9.x, .NET8.x.
 
 ---
 
@@ -36,13 +28,13 @@ To install the tool the only thing you must do is to take it from NuGet, install
 
 {{< img src="initialize.png" >}}
 
-``` bash
+```bash
 dotnet tool install -g genocs.cli
 ```
 
 ### Useful commands
 
-``` bash
+```bash
 # Get the list of tools
 dotnet tool list
 
@@ -85,7 +77,7 @@ The picture shows the console log upon the template is installed.
 
 To uninstall the templates, you can use the following command:
 
-``` bash
+```bash
 # Get the templates list
 dotnet new uninstall
 
@@ -97,11 +89,11 @@ dotnet new uninstall Genocs.MicroserviceTemplate
 dotnet new uninstall Genocs.Microservice.Template
 ```
 
-### blazor
+### Blazor
 
 To create a blazor portal use one of these commands
 
-``` bash
+```bash
 # To build a blazor portal 
 genocs blazor-wasm new <Company.Project.Service>
 
@@ -111,7 +103,7 @@ genocs blazor-clean new <Company.Project.Service>
 
 ### WebAPI
 
-``` bash
+```bash
 # To build a web api architecture webapi 
 genocs libra-webapi new <Company.Project.Service>
 
@@ -132,7 +124,7 @@ You are free to fork or to clone it. Then you can update it at your own pace.
 
 ### Useful commands to work on your own
 
-``` bash
+```bash
 # Build the project 
 dotnet build ./src/genocs.cli.csproj
 
@@ -155,7 +147,7 @@ dotnet tool install --global --add-source ./src/nupkg genocs.cli
 In the following section, you will find the commands to create a new service from scratch.
 For sake of simplicity, we will change the name of the service from `<Company.Project.Service>` to a demo name.
 
-``` bash
+```bash
 # To build a microservice web Api with multitenant support
 genocs micro-webapi n Genocs.TestWebApi
 
@@ -176,15 +168,24 @@ dotnet run --project ./Genocs.TestWebApi/src/WebApi/WebApi.csproj
 dotnet run --project ./Genocs.TestWebBlazorPortal/src/Host/Host.csproj
 ```
 
-``` mermaid
+```mermaid
 architecture-beta
-    group api(logos:aws-lambda)[Example]
+  group api(cloud)[Microservice]
 
-    service webapp(logos:aws-cognito)[WebApp] in api
-    service webapi(logos:aws-lambda)[WebApi] in api
-    service db(logos:aws-documentdb)[Database] in api
+  service fe(server)[FrontEnd] in api
+  service be(server)[BackEnd] in api
+  service db(database)[Database] in api
+  service disk1(disk)[Storage] in api
 
-    db:T -- B:webapi
-    webapi:L -- R:webapp
+  fe:B --> T:be
+  be:B --> T:db
+  be:L --> R:disk1
+```
+
+---
+
+## Visual Studio Integration
+
+The Genocs CLI is integrated with Visual Studio. You can use the Genocs CLI to create, build, and run applications directly from Visual Studio. The Genocs CLI provides a unified experience across different platforms, allowing you to create cross-platform applications with ease. You can use the Genocs CLI to automate tasks such as project management, dependency resolution, and deployment. The Genocs CLI is an essential tool for modern developers, offering productivity, flexibility, and scalability in application development.
 
-```
+{{< img src="vs_integration.png" >}}