(options =>
+{
+ // How long to keep exported files before cleanup
+ options.FileRetentionHours = 48;
+
+ // Base URL for download links in notification emails
+ options.DownloadBaseUrl = "https://yourdomain.com";
+
+ // Configure the cleanup worker schedule
+ options.ExcelFileCleanupOptions.Period = (int)TimeSpan.FromHours(24).TotalMilliseconds;
+
+ // Use cron expression for more advanced scheduling (requires Hangfire or Quartz)
+ options.ExcelFileCleanupOptions.CronExpression = "0 2 * * *"; // Run at 2 AM daily
+});
+```
+
+The module includes pre-configured email templates for notifications about completed or failed exports, ensuring users are always informed about the status of their export requests.
+
+> **Note**: This feature requires a configured BLOB storage provider to store the generated Excel files. See the [BLOB Storing documentation](https://abp.io/docs/9.3/framework/infrastructure/blob-storing) for more information.
+
+For more details about the Audit Logging Module and its Excel export capabilities, please refer to the [official documentation](https://abp.io/docs/9.3/modules/audit-logging-pro).
+
+## Community News
+
+### Announcing ABP Studio 1.0 General Availability 🚀
+
+
+
+We are thrilled to announce that ABP Studio has reached version 1.0 and is now generally available! This marks a significant milestone for our integrated development environment designed specifically for ABP developers. The stable release brings several powerful features including:
+
+* Enhanced Solution Runner with health monitoring capabilities
+* Theme style selection during project creation (Basic, LeptonX Lite, and LeptonX Themes)
+* New "Container" application type for better Docker container management
+* Improved handling of multiple DbContexts for migration operations
+
+> For a detailed overview of these features and to learn more about what's coming next, check out our [announcement post](https://abp.io/community/articles/announcing-abp-studio-1-0-general-availability-82yw62bt).
+
+### ABP Community Talks 2025.05: Empower Elsa Workflows with AI in .NET + ABP Framework
+
+In this episode of ABP Community Talks, 2025.05, we are thrilled to host [**Sipke Schoorstra**](https://github.com/sfmskywalker), the creator of the [Elsa Workflows](https://docs.elsaworkflows.io/) library! This month's session is all about **"Empower Elsa Workflows with AI in .NET + ABP Framework"**.
+
+
+
+Sipke will join us to demonstrate how you can leverage AI within Elsa Workflows using .NET and the ABP Framework. The session will explore practical techniques and showcase how to integrate AI capabilities to enhance and automate your business processes within the Elsa workflow engine.
+
+> 👉 Don't miss this opportunity to learn directly from the creator of Elsa and see real-world examples of building intelligent, automated workflows! You can register from [here](https://kommunity.com/volosoft/events/abp-community-talks-202505empower-elsa-workflows-with-ai-in-netabp-framework-3965dd32).
+
+### ABP Bootcamp: Mastering Infrastructure & Features
+
+We are excited to announce the very first **ABP Bootcamp: Mastering Infrastructure & Features**! This is a live training program designed to give you hands-on, practical experience with ABP's core infrastructure and features.
+
+
+
+Join the ABP Bootcamp to learn directly from the core team in a focused, hands-on program designed for busy developers. Over four days, you'll gain a deep understanding of ABP's infrastructure, best practices, and practical skills you can immediately apply to your projects.
+
+> **Seats are limited!** Don't miss this opportunity to level up your ABP skills with direct guidance from the experts.
+>
+> 👉 [See full details and reserve your seat!](https://abp.io/bootcamp)
+
+### New ABP Community Articles
+
+There are exciting articles contributed by the ABP community as always. I will highlight some of them here:
+
+* [Prabhjot Singh](https://abp.io/community/members/prabhjot) has published 3 new articles:
+ * [Accessing Multiple Remote ABP based Backends Using HttpApi.Client](https://abp.io/community/articles/consume-multi-backends-using-clients-6f4vcggh)
+ * [Adopting the new .slnx format to organize applications and services](https://abp.io/community/articles/adopting-the-new-.slnx-format-to-organize-applications-6cm3vl8k)
+ * [Replacing Dynamic client proxies with Static client proxies](https://abp.io/community/articles/replacing-dynamic-client-proxies-with-static-client-proxies-g30lf0vx)
+* [Liming Ma](https://github.com/maliming) has published 2 new articles:
+ * [Resolving Tenant from Route in ABP Framework](https://abp.io/community/articles/resolving-tenant-from-route-in-abp-framework-ah7oru97)
+ * [Integrating .NET AI Chat Template with ABP Framework](https://abp.io/community/articles/integrating-.net-ai-chat-template-with-abp-framework-qavb5p2j)
+* [Engincan Veske](https://engincanveske.substack.com/) has published 2 new articles:
+ * [Understanding HttpApi.Client Project & Remote Services in an ABP Based Application](https://abp.io/community/articles/http-api-client-and-remote-services-in-abp-based-application-xkknsp6m)
+ * [Using Elsa 3 with the ABP Framework: A Comprehensive Guide](https://abp.io/community/articles/using-elsa-3-workflow-with-abp-framework-usqk8afg)
+* [Enis Necipoğlu](https://github.com/enisn) has published 2 new articles:
+ * [White Labeling in ABP Framework](https://abp.io/community/articles/white-labeling-in-abp-framework-5trwmrfm) by [Enis Necipoğlu](https://github.com/enisn)
+ * [You do it wrong! Customizing ABP Login Page Correctly](https://abp.io/community/articles/you-do-it-wrong-customizing-abp-login-page-correctly-bna7wzt5)
+* [New in ABP Studio: Docker Container Management](https://abp.io/community/articles/abp-studio-docker-container-management-ex7r27y8) by [Yunus Emre Kalkan](https://github.com/yekalkan)
+* [Solving MongoDB GUID Issues After an ABP Framework Upgrade](https://abp.io/community/articles/solving-mongodb-guid-issues-after-an-abp-framework-upgrade-tv8waw1n) by [Burak Demir](https://abp.io/community/members/burakdemir)
+
+
+Thanks to the ABP Community for all the content they have published. You can also [post your ABP-related (text or video) content](https://abp.io/community/posts/create) to the ABP Community.
+
+## Conclusion
+
+This version comes with some new features and a lot of enhancements to the existing features. You can see the [Road Map](https://abp.io/docs/9.3/release-info/road-map) documentation to learn about the release schedule and planned features for the next releases. Please try ABP v9.3 RC and provide feedback to help us release a more stable version.
+
+Thanks for being a part of this community!
\ No newline at end of file
diff --git a/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/abp-studio.png b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/abp-studio.png
new file mode 100644
index 0000000000..76b24a8573
Binary files /dev/null and b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/abp-studio.png differ
diff --git a/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/audit-logs-export-to-excel.png b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/audit-logs-export-to-excel.png
new file mode 100644
index 0000000000..4c10f516db
Binary files /dev/null and b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/audit-logs-export-to-excel.png differ
diff --git a/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/bootcamp.png b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/bootcamp.png
new file mode 100644
index 0000000000..e07293c13c
Binary files /dev/null and b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/bootcamp.png differ
diff --git a/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/community-talk-2025-5.png b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/community-talk-2025-5.png
new file mode 100644
index 0000000000..3989dde47a
Binary files /dev/null and b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/community-talk-2025-5.png differ
diff --git a/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/cover-image.png b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/cover-image.png
new file mode 100644
index 0000000000..291da0d04f
Binary files /dev/null and b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/cover-image.png differ
diff --git a/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/download-pdf-on-docs.png b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/download-pdf-on-docs.png
new file mode 100644
index 0000000000..ce5b1b3727
Binary files /dev/null and b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/download-pdf-on-docs.png differ
diff --git a/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/generate-pdf-docs.png b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/generate-pdf-docs.png
new file mode 100644
index 0000000000..2a1de4398d
Binary files /dev/null and b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/generate-pdf-docs.png differ
diff --git a/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/studio-switch-to-preview.png b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/studio-switch-to-preview.png
new file mode 100644
index 0000000000..32f6d01edb
Binary files /dev/null and b/docs/en/Blog-Posts/2025-06-18 v9_3_Preview/studio-switch-to-preview.png differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/1752664190317-min.jpeg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/1752664190317-min.jpeg
new file mode 100644
index 0000000000..7cd0f2aa47
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/1752664190317-min.jpeg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15924-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15924-min.jpg
new file mode 100644
index 0000000000..3730feed30
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15924-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15933-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15933-min.jpg
new file mode 100644
index 0000000000..5c4348c2a6
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15933-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15934-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15934-min.jpg
new file mode 100644
index 0000000000..bfaec7bc9d
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15934-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15941-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15941-min.jpg
new file mode 100644
index 0000000000..8539d5be5c
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15941-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15944-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15944-min.jpg
new file mode 100644
index 0000000000..2502d8904c
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15944-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15946-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15946-min.jpg
new file mode 100644
index 0000000000..da423629c7
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15946-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15947-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15947-min.jpg
new file mode 100644
index 0000000000..372f41e3a5
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15947-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15948-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15948-min.jpg
new file mode 100644
index 0000000000..9d98fe4585
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15948-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15949-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15949-min.jpg
new file mode 100644
index 0000000000..dac9184cf3
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15949-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15956-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15956-min.jpg
new file mode 100644
index 0000000000..73ef867711
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15956-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15959-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15959-min.jpg
new file mode 100644
index 0000000000..af4c2b300a
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15959-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15963-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15963-min.jpg
new file mode 100644
index 0000000000..e2c3a297f7
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15963-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15964-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15964-min.jpg
new file mode 100644
index 0000000000..4ed6c26b33
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15964-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15966-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15966-min.jpg
new file mode 100644
index 0000000000..80296b7ead
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15966-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15968-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15968-min.jpg
new file mode 100644
index 0000000000..6f915ee94c
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15968-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15969-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15969-min.jpg
new file mode 100644
index 0000000000..de112a11ea
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15969-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15970-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15970-min.jpg
new file mode 100644
index 0000000000..acdd4bb0b0
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15970-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15971-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15971-min.JPG
new file mode 100644
index 0000000000..5fd55d58e1
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15971-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15972-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15972-min.JPG
new file mode 100644
index 0000000000..c1956daebd
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15972-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15973-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15973-min.JPG
new file mode 100644
index 0000000000..3d1a5b0789
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15973-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15974-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15974-min.JPG
new file mode 100644
index 0000000000..147f7ef967
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15974-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15975-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15975-min.JPG
new file mode 100644
index 0000000000..173610a7ec
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15975-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15976-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15976-min.JPG
new file mode 100644
index 0000000000..c48a7944d6
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15976-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15977-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15977-min.JPG
new file mode 100644
index 0000000000..6f5cb19831
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15977-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15979-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15979-min.JPG
new file mode 100644
index 0000000000..9ca4140717
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15979-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15980-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15980-min.JPG
new file mode 100644
index 0000000000..0ebf59d8b8
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15980-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15981-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15981-min.JPG
new file mode 100644
index 0000000000..10e02621cf
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15981-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15982-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15982-min.JPG
new file mode 100644
index 0000000000..63bc90cc76
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15982-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15983-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15983-min.JPG
new file mode 100644
index 0000000000..14e1f16c9a
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15983-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15984-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15984-min.jpg
new file mode 100644
index 0000000000..0984be8e2e
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15984-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15985-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15985-min.JPG
new file mode 100644
index 0000000000..8d30f62cd3
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15985-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15986-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15986-min.JPG
new file mode 100644
index 0000000000..55f48e13a9
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15986-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15987-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15987-min.JPG
new file mode 100644
index 0000000000..9cbd57efaa
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15987-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15989-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15989-min.jpg
new file mode 100644
index 0000000000..f4c0bb2cfc
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15989-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15994-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15994-min.jpg
new file mode 100644
index 0000000000..35201fee15
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15994-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15995-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15995-min.jpg
new file mode 100644
index 0000000000..bc4220f83a
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15995-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15996-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15996-min.jpg
new file mode 100644
index 0000000000..e5dd4c0c9d
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15996-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15998-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15998-min.jpg
new file mode 100644
index 0000000000..d2ae92ff0e
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15998-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15999-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15999-min.jpg
new file mode 100644
index 0000000000..22c32abd22
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_15999-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16001-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16001-min.jpg
new file mode 100644
index 0000000000..1f8a500948
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16001-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16002-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16002-min.jpg
new file mode 100644
index 0000000000..8753a09cfe
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16002-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16003-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16003-min.jpg
new file mode 100644
index 0000000000..4f4eec7b54
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16003-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16006-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16006-min.JPG
new file mode 100644
index 0000000000..eef991dd38
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16006-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16007-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16007-min.jpg
new file mode 100644
index 0000000000..48cb26cd40
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16007-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16008-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16008-min.jpg
new file mode 100644
index 0000000000..3eadec4490
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16008-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16009-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16009-min.jpg
new file mode 100644
index 0000000000..0e8387065d
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16009-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16011-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16011-min.jpg
new file mode 100644
index 0000000000..392a680bdf
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16011-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16012-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16012-min.jpg
new file mode 100644
index 0000000000..15a3fbf143
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16012-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16013-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16013-min.jpg
new file mode 100644
index 0000000000..256c2bc22c
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16013-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16019-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16019-min.JPG
new file mode 100644
index 0000000000..e657a682ad
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16019-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16021-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16021-min.JPG
new file mode 100644
index 0000000000..5a81fddee1
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16021-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16022-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16022-min.JPG
new file mode 100644
index 0000000000..ed8660fdbd
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16022-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16023-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16023-min.JPG
new file mode 100644
index 0000000000..05b2040d18
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16023-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16024-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16024-min.JPG
new file mode 100644
index 0000000000..2cc6f9fbee
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16024-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16025-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16025-min.JPG
new file mode 100644
index 0000000000..0ede12db76
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16025-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16026-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16026-min.JPG
new file mode 100644
index 0000000000..268e4a4454
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16026-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16027-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16027-min.JPG
new file mode 100644
index 0000000000..68d288fc19
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16027-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16028-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16028-min.JPG
new file mode 100644
index 0000000000..72d060a6e1
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16028-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16029-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16029-min.JPG
new file mode 100644
index 0000000000..47bc5a910c
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16029-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16030-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16030-min.JPG
new file mode 100644
index 0000000000..5180e62195
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16030-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16031-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16031-min.JPG
new file mode 100644
index 0000000000..3085d54f3d
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16031-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16032-min.jpg b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16032-min.jpg
new file mode 100644
index 0000000000..26ddb2dc75
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16032-min.jpg differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16040-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16040-min.JPG
new file mode 100644
index 0000000000..4bf5c04712
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16040-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16041-min.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16041-min.JPG
new file mode 100644
index 0000000000..3b38f0c487
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/IMG_16041-min.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/cover.png b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/cover.png
new file mode 100644
index 0000000000..595446cefa
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/cover.png differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/image-20250722203102576.png b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/image-20250722203102576.png
new file mode 100644
index 0000000000..8b8f3a978b
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/image-20250722203102576.png differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-1.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-1.JPG
new file mode 100644
index 0000000000..6be6b041d3
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-1.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-2.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-2.JPG
new file mode 100644
index 0000000000..b05c488c4d
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-2.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-3.JPG b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-3.JPG
new file mode 100644
index 0000000000..51dd5e7e57
Binary files /dev/null and b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/my-talk-3.JPG differ
diff --git a/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/post.md b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/post.md
new file mode 100644
index 0000000000..1b996e4867
--- /dev/null
+++ b/docs/en/Blog-Posts/2025-07-22-My-Impressionf-at-WeAreDevelopers/post.md
@@ -0,0 +1,101 @@
+# WeAreDevelopers 2025: A Speaker’s Impressions
+
+
+
+After speaking at DotNext Moscow, I had high expectations for WeAreDevelopers 2025—and the event delivered on all fronts. Held in Berlin / Germany, it brought together a truly global crowd of developers, tech leaders, and innovators. As a speaker and software architect , I’m sharing my first-hand highlights, favorite moments, and candid scenes from this 2025’s conference.
+
+## 🗣 My Talk
+
+We have a good experience on multi-tenancy topic in SaaS development. My talk's topic was "Building Multi-Tenant ASP.NET Core Applications: Best Practices and Real-World Solutions". It was on the stage 4, 11 July Friday 10:20 am - 10:50 am and [this my presentation file](https://github.com/ebicoglu/presentations/blob/main/multi-tenancy-wearedevelopers-2025_30mins.pptx).
+
+
+
+
+
+
+
+
+## 🏛 Huge Venue
+
+
+*The image is credited to WeAreDevelopers organization*
+
+First of all, I had been in numerous software conferences, I must say that I've never seen such a big software event. The event spanned **500+ sessions across 20+ stages**, including the HR Leaders Summit for **2 full days**.
+
+
+
+
+------
+
+## 🎤 Opening Keynote from GitHub
+
+GitHub CEO Thomas Dohmke initiated the conference on the main stage with a talk on *“Agents for the Sake of Happiness”*. Having introduced Copilot three years ago here, he now launched bold predictions about autonomous AI—a fascinating evolution... He demonstrated GitHub Co-Pilot's AI and created a snake game. Altough it didn't work as he planned, we're developers we know live coding is hard. Actually that's because we shouldn't rely on AI. AI is not deterministic even though we set all those temperature, TopP, TopK parameters to minimum.
+
+> AI is a good but not trustable friend!
+
+
+
+------
+
+## 🧭 11 Parallel Stages: Rush
+
+There were 11 stages where 11 different topics were being explained. And the sessions were 30 minutes. Actually that's the downside of this event. Because there were so nice talks that needs to be minimum 40 minutes. But anyway I understand the organization team because there are many smart speakers whose needs to be included in this event. So as a attendee I was on a hurry to pick the next talk even when I was listening to a talk :)
+
+The venue consists of 3 buildings. So if you pick a talk on another building, you have 10 mins to go to toilet or drink something and catch the next session on that far building...
+
+There was HR track with **3 stages and 2 full days** of HR/Talent Acquisition programming, it attracted a notable overlap of developers and HR pros. Themes included AI‑powered recruiting, remote work culture, mental health, diversity & inclusion, and building AI agents
+
+
+
+
+
+------
+
+## 🤖 AI & AI & AI & Others...
+
+I'm one of those AI lovers. I love learning cutting-edge information. And as I see AI is being more trendy everyday. That's why most of the talks were about AI. Everything related to AI. I generaly attended AI related talks because I'm also working on some AI topics in Volosoft at the moment.
+
+
+------
+
+## 🤝 Expo Floor & Networking
+
+The expo was a developer’s playground—cloud services, open‑source tools, startups, and enterprise platforms. I found new partners and reconnected with peers in a buzzing atmosphere. Everywhere was full of talking's even outside. If you want to get fresh air and drink coffee, you can go out and listen to the outside talks.
+
+
+
+
+
+
+Networking wasn't just daytime chatter—hallway meetups and evening socials were unforgettable.
+
+
+
+
+------
+
+## 😂 Candid & Fun Moments
+
+Swag stations, sponsor games, “developer selfies”—these lighter moments kept the vibe upbeat and human.
+
+
+
+
+------
+
+## ✅ Final Thoughts & Looking Ahead
+
+WeAreDevelopers 2025 was an unforgettable three-day ride: **15,000 tech minds**, **500+ sessions**, and a true **bridge between developers and HR**
+I’m leaving with:
+
+- Fresh strategies in GenAI and SaaS growth
+- Stronger HR-tech understanding and crossover potential
+- New professional connections—and fun memories
+
+
+------
+
+
+
+
+
diff --git a/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/POST.md b/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/POST.md
new file mode 100644
index 0000000000..3acf9a7dd0
--- /dev/null
+++ b/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/POST.md
@@ -0,0 +1,79 @@
+# ABP.IO Platform 9.3 Final Has Been Released!
+
+We are glad to announce that [ABP](https://abp.io/) 9.3 stable version has been released today.
+
+## What's New With Version 9.3?
+
+All the new features were explained in detail in the [9.3 RC Announcement Post](https://abp.io/community/announcements/announcing-abp-9-3-release-candidate-4dqgiryf), so there is no need to review them again. You can check it out for more details.
+
+## Getting Started with 9.3
+
+### Creating New Solutions
+
+You can check the [Get Started page](https://abp.io/get-started) to see how to get started with ABP. You can either download [ABP Studio](https://abp.io/get-started#abp-studio-tab) (**recommended**, if you prefer a user-friendly GUI application - desktop application) or use the [ABP CLI](https://abp.io/docs/latest/cli) to create new solutions.
+
+> **Note**: ABP Studio **v1.2.1** has been released with support for **ABP 9.3**. If you already have ABP Studio installed, update it to v1.2.1 (or later, if available) to create new applications targeting 9.3. ABP Studio checks for updates automatically and will prompt you in-app modal to update to the latest version, or you can download the latest installer from the [Studio](https://abp.io/studio) page. See the [upgrading guide](https://abp.io/docs/latest/studio/installation#upgrading) for details. After updating, the New Solution wizard will create applications with ABP 9.3 by default. You can check the [ABP Studio and ABP Startup Template Version Mappings](https://abp.io/docs/latest/studio/version-mapping) documentation to see the corresponding ABP versions for other versions of Studio.
+
+### How to Upgrade an Existing Solution
+
+You can upgrade your existing solutions with either ABP Studio or ABP CLI. In the following sections, both approaches are explained:
+
+### Upgrading via ABP Studio
+
+If you are already using the ABP Studio, you can upgrade it to the latest version. ABP Studio periodically checks for updates in the background, and when a new version of ABP Studio is available, you will be notified through a modal. Then, you can update it by confirming the opened modal. See [the documentation](https://abp.io/docs/latest/studio/installation#upgrading) for more info.
+
+After upgrading the ABP Studio, then you can open your solution in the application, and simply click the **Upgrade ABP Packages** action button to instantly upgrade your solution:
+
+
+
+### Upgrading via ABP CLI
+
+Alternatively, you can upgrade your existing solution via ABP CLI. First, you need to install the ABP CLI or upgrade it to the latest version.
+
+If you haven't installed it yet, you can run the following command:
+
+```bash
+dotnet tool install -g Volo.Abp.Studio.Cli
+```
+
+Or to update the existing CLI, you can run the following command:
+
+```bash
+dotnet tool update -g Volo.Abp.Studio.Cli
+```
+
+After installing/updating the ABP CLI, you can use the [`update` command](https://abp.io/docs/latest/CLI#update) to update all the ABP related NuGet and NPM packages in your solution as follows:
+
+```bash
+abp update
+```
+
+You can run this command in the root folder of your solution to update all ABP related packages.
+
+## Migration Guides
+
+There are a few breaking changes in this version that may affect your application. Please read the migration guide carefully, if you are upgrading from v9.2: [ABP Version 9.3 Migration Guide](https://abp.io/docs/9.3/release-info/migration-guides/abp-9-3)
+
+## Community News
+
+### New ABP Community Articles
+
+As always, exciting articles have been contributed by the ABP community. I will highlight some of them here:
+
+* [Fahri Gedik](https://abp.io/community/members/fahrigedik) has published 2 new articles:
+ * [A Modern Approach to Angular Dependency Injection using inject function](https://abp.io/community/articles/a-modern-approach-to-angular-dependency-injection-using-8np4o1ap)
+ * [Angular Application Builder: Transitioning from Webpack to Esbuild](https://abp.io/community/articles/angular-application-builder-transitioning-from-webpack-to-3yzhzfl0)
+* [Benjamin Fadina](https://abp.io/community/members/benjaminsqlserver@gmail.com) has published several videos on various topics such as **Blazor Web Assembly Using ABP.IO**, **CQRS Implementation with MediatR in ABP** and more. You can see all his videos [here](https://abp.io/community/members/benjaminsqlserver@gmail.com).
+* [Mansur Besleney](https://abp.io/community/members/mansur.besleney) has published [How to Build Persistent Background Jobs with ABP Framework and Quartz](https://abp.io/community/articles/how-to-build-persistent-background-jobs-with-abp-framework-n9aloh93)
+* [Halil Ibrahim Kalkan](https://x.com/hibrahimkalkan) has published [Multitenancy with Separate Databases in .NET and ABP](https://abp.io/community/articles/multitenancy-with-separate-databases-in-dotnet-and-abp-51nvl4u9)
+* [Alex Maiereanu](https://abp.io/community/members/alex.maiereanu@3sstudio.com) has published [ABP-Hangfire-AzurePostgreSQL](https://abp.io/community/articles/abphangfireazurepostgresql-s1jnf3yg)
+* [Jack Fistelmann](https://abp.io/community/members/jfistelmann) has published [ABP and maildev](https://abp.io/community/articles/abp-and-maildev-gy13cr1p)
+* [Harsh Gupta](https://abp.io/community/members/harshgupta) has published [How to Add a Module in the ABP.io Application?](https://abp.io/community/articles/how-to-add-a-module-in-the-abp.io-application-sdeajkn6)
+* [Tarık Özdemir](https://abp.io/community/members/mtozdemir) has published [AI-First Architecture for .NET Projects: A Modern Blueprint Inspired by McKinsey](https://abp.io/community/articles/AI-First%20Architecture%20for%20.NET%20Projects%3A%20A%20Modern%20Blueprint-h2wgcoq3)
+* [Liming Ma](https://github.com/maliming) has published [Using Hangfire Dashboard in ABP API Website](https://abp.io/community/articles/using-hangfire-dashboard-in-abp-api-website--r32ox497)
+
+Thanks to the ABP Community for all the content they have published. You can also [post your ABP related (text or video) content](https://abp.io/community/posts/create) to the ABP Community.
+
+## About the Next Version
+
+The next feature version will be 10.0. You can follow the [release planning here](https://github.com/abpframework/abp/milestones). Please [submit an issue](https://github.com/abpframework/abp/issues/new) if you have any problems with this version.
diff --git a/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/cover-image.png b/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/cover-image.png
new file mode 100644
index 0000000000..291da0d04f
Binary files /dev/null and b/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/cover-image.png differ
diff --git a/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/upgrade-abp-packages.png b/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/upgrade-abp-packages.png
new file mode 100644
index 0000000000..ad5e9bd462
Binary files /dev/null and b/docs/en/Blog-Posts/2025-08-08 v9_3_Release_Stable/upgrade-abp-packages.png differ
diff --git a/docs/en/Community-Articles/2022-04-18-abp-community-talks-20223/post.md b/docs/en/Community-Articles/2022-04-18-abp-community-talks-20223/post.md
index fcd7043594..5d9c9e0d3e 100644
--- a/docs/en/Community-Articles/2022-04-18-abp-community-talks-20223/post.md
+++ b/docs/en/Community-Articles/2022-04-18-abp-community-talks-20223/post.md
@@ -6,7 +6,7 @@
* ABP Community Talks are scheduled to be held on a monthly basis.
* ABP Community Talks are and always will be completely free to attend. Everyone is welcome to join, ask questions and make suggestions before, during and after the event.
* ABP Community Talks are created and announced on [Kommunity](https://kommunity.com/volosoft/events).
- * ABP Community Talks are announced regularly on [ABP Framework Twitter Account](https://twitter.com/abpframework), [Volosoft LinkedIn account](https://www.linkedin.com/company/volosoft), [Volosoft Facebook Account](https://www.facebook.com/volosoftcompany), [ABP Community Discord Server](https://discord.gg/CrYrd5vcGh). We highly encourage everyone to follow us and make suggestions.
+ * ABP Community Talks are announced regularly on [ABP Framework Twitter Account](https://twitter.com/abpframework), [Volosoft LinkedIn account](https://www.linkedin.com/company/volosoft), [Volosoft Facebook Account](https://www.facebook.com/volosoftcompany), [ABP Community Discord Server](https://abp.io/join-discord). We highly encourage everyone to follow us and make suggestions.
* ABP Community Talks are available to watch after the event on YouTube. See [ABP Community Talks YouTube Playlist](https://www.youtube.com/playlist?list=PLsNclT2aHJcOsPustEkzG6DywiO8eh0lB).
# ABP Community Talks 2022.3
diff --git a/docs/en/Community-Articles/2022-04-19-official-abp-discord-server-is-here/post.md b/docs/en/Community-Articles/2022-04-19-official-abp-discord-server-is-here/post.md
index 5d099cc1c3..ca765a5860 100644
--- a/docs/en/Community-Articles/2022-04-19-official-abp-discord-server-is-here/post.md
+++ b/docs/en/Community-Articles/2022-04-19-official-abp-discord-server-is-here/post.md
@@ -1,9 +1,9 @@
- We are excited to announce Official ABP Discord Server is created! You can join the ABP Discord Community by clicking [here](https://discord.gg/wbcQAsUrs9).
+ We are excited to announce Official ABP Discord Server is created! You can join the ABP Discord Community by clicking [here](https://abp.io/join-discord).
In the first week of opening ABP Discord Server, member amount reached more than 500. We are grateful to and blessed by your interest. Thanks to all of you! This also made us sure that an ABP Discord Server was actually a need for the community members to interact with each other.
ABP Community is growing by the second, and we are grateful for all your contributions towards ABP Framework. We noticed that ABP Community’s communication were significant on ABP Framework’s GitHub, we wanted to take it to the next level and have an area where all of us can easily chat with each other.
-> [Join ABP Discord Server Now](https://discord.gg/wbcQAsUrs9)
+> [Join ABP Discord Server Now](https://abp.io/join-discord)
# What Can You Do on ABP Community Discord Server?
@@ -42,11 +42,11 @@
# How Can You Join To ABP Discord Server?
- You can join ABP Discord Server by simply clicking to [https://discord.gg/abp](https://discord.gg/wbcQAsUrs9).
+ You can join ABP Discord Server by simply clicking to [https://abp.io/join-discord](https://abp.io/join-discord).
We are excited to welcome you in ABP Discord Server!
-> [Click Here to Join ABP Discord Server Now](https://discord.gg/wbcQAsUrs9)
+> [Click Here to Join ABP Discord Server Now](https://abp.io/join-discord)
### What is Discord?
@@ -62,4 +62,4 @@
In Discord Servers, users communicate with each other in a way that is convenient for them. Discord allows people to make voice calls, video chats, or simply text messages. Communities are created by wether fans of a specific topic(games, open-source frameworks, NFT, etc.) or by the official authorities of that specific topic(game creator, framework core team, creator of a token, etc).
- In ABP Community Discord Server’s case, it is a server created by official authorities with core team being present in the server along with the community members. Even though it is created for the framework community members to communicate with each other easily, everyone who is interested in following the latest news about ABP Platform are welcome to [join ABP Discord Server](https://discord.gg/wbcQAsUrs9)!
\ No newline at end of file
+ In ABP Community Discord Server’s case, it is a server created by official authorities with core team being present in the server along with the community members. Even though it is created for the framework community members to communicate with each other easily, everyone who is interested in following the latest news about ABP Platform are welcome to [join ABP Discord Server](https://abp.io/join-discord)!
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2022-05-10-abpio-platform-53-rc-has-been-published/post.md b/docs/en/Community-Articles/2022-05-10-abpio-platform-53-rc-has-been-published/post.md
index eb157010b8..cc0e57db93 100644
--- a/docs/en/Community-Articles/2022-05-10-abpio-platform-53-rc-has-been-published/post.md
+++ b/docs/en/Community-Articles/2022-05-10-abpio-platform-53-rc-has-been-published/post.md
@@ -254,4 +254,4 @@ We've created an official ABP Discord server so the ABP Community can interact w
Thanks to the ABP Community, **700+** people joined our Discord Server so far and it grows every day.
-You can join our Discord Server from [here](https://discord.gg/abp), if you haven't yet.
\ No newline at end of file
+You can join our Discord Server from [here](https://abp.io/join-discord), if you haven't yet.
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2023-02-21-abp-year-review-2022-wrap-up/post.md b/docs/en/Community-Articles/2023-02-21-abp-year-review-2022-wrap-up/post.md
index 6abf2f3d12..a27aeb9f2c 100644
--- a/docs/en/Community-Articles/2023-02-21-abp-year-review-2022-wrap-up/post.md
+++ b/docs/en/Community-Articles/2023-02-21-abp-year-review-2022-wrap-up/post.md
@@ -1,100 +1,200 @@
- ABP Framework is an open source infrastructure that enables developers to create modern web applications by following the best practices and conventions of software development. In 2022, ABP Framework continued to thrive, achieving significant milestones and making waves in the software development community. With more than 9K GitHub stars and over 10 millions of downloads on NuGet, ABP Framework has become a go-to framework for developers seeking a reliable and efficient way to build web applications.
-
-As ABP Team, we owe our success to our vibrant community, and we are immensely grateful for the support and contributions of each and every member. With your help, we achieved a lot in 2022. We remained committed to our values of transparency, openness, and collaboration, engaging with our community members as much as possible to ensure that we are creating a framework that meets their needs.
-
-One of the major highlights of 2022 was the release of .NET Core 7, which provided a powerful platform for ABP Framework to build upon. Additionally, ABP Commercial and our training programs continued to help developers and businesses to leverage the power of the ABP Framework, enabling them to build modern web applications more efficiently and effectively than ever before.
-
-In this article, we'll take a closer look at the key highlights of 2022 for ABP Framework, from major updates to achivements and the community insights. We are excited to share our progress with you and provide insights into how ABP Framework is continuing to shape the future of software development. So, let's dive in!
-
-
-
-
- NuGet Downloads
- NuGet is a package manager designed specifically for the .NET ecosystem. It simplifies the process of creating and consuming packages, thanks to the NuGet client tools. By using these tools, developers can easily manage their project dependencies and improve their workflow.
- In 2022, ABP Core NuGet package reached more than 10 million of downloads!
- On the other hand, overall Volosoft NuGet Packages reached more than half a billion downloads!
- Thank you all for your interest and support towards Volosoft and ABP packages.
-
-
- E-Books
- Our published e-book amount is reached 3! This year, with our founder Halil İbrahim Kalkan's contributions we now have 3 published e-books.
-
-
-
- Tutorial Videos
- In 2022, we tried to be as much active as we could. To give you more insight and let you understand ABP Framework with short videos according to your interests, we published 48 tutorial videos. Though the videos were created by overall team members of ABP Framework, someone deserves a special mention here. Shout out to our ABP Core Team member Hamza Albreem for his hard work.
-
-
- GitHub Stars
- ABP Framework GitHub repository reached more than 9K stars. We appreciate your interest and support for ABP Framework GitHub repository. We are working hard to be worthy of your interest and reach out to more people to simplify and streamline their development processes.
-
- Community Talks
-ABP Community Talks is our monthly event that brings together members of the ABP Framework community to discuss and exchange ideas. Prior to each event, we collect suggestions from our contributors, monitor trending topics in the industry, and review updates and news related to the ABP Platform to curate the topics for discussion. Once the topics are finalized, we announce them through our social media and community channels to ensure everyone is aware and can join in on the conversation.
- We did 10 ABP Community Talks Episodes of and 1 ABP Suite webinar. You can take a look at them and check out our videos we have on Volosoft YouTube Channel.
-
- ABP Community Contributions
- The ABP Community is a hub that offers resources such as articles, video tutorials, and updates on ABP's development progress and events for ABP Framework, .NET, and software development. Developers can also connect with others, help each other, and share their expertise in ABP Community.
- You can check out each source from the list below.
- - ABP Community Events: You can reach them from here.
- - ABP Community Posts: You can reach them from here
- - ABP Community Videos: You can reach them from here.
- - ABP Community Stackoverflow: You can reach them from here.
-
- In 2022, the community's contribution reached a point where more than 100 resources. Thank you for all your effort! Please keep it going! It is becoming a more and more rich resource thanks to your variety of contributions and help.
-
-
- ABP Community Discord Server
- To take community interaction to the next level, we created the official ABP Discord server, providing a platform for the ABP Community to connect and communicate instantly through chatting.
- We were so excited announcing the official ABP Discord Server. In the first week of announcing it, the server quickly attracted over 500 members. We're grateful for your interest and support, which confirms the need for a dedicated platform for community interaction.
-> Join ABP Discord Server Now
-
-
- ABP Framework GitHub Contributions
- In 2022, ABP Core Team worked hard to achieve milestones and give the best value with ABP Framework so users can benefit from its features. Additional to our team's work, ABP Framework is perfected in 2022 with ABP Community members' contributions, 3157 commits pushed from 48 different contributors.
- We appreciate your hard work and effort you put into making ABP Framework better and improved.
-
-
- Events/Summits
- We try to contribute to the developers community as much as we can since day 1. This year was no different. We tried to give value through sponsorships for developer communities. Especially with us leaving the pandemic behind every day, we try to keep up with the in-person events as well as online events. We plan to do more in next year. So, stay tuned!
- This year, we sponsored to 4 events. They were, DevNot
-Designing Monolith First for Microservice Architecture event, DNF Summit 2022, Developer Summit 2022, and .NET Conference 2022.
-
-
-
ABP Releases
- ABP Framework released 4 versions from 5.1 to 7.1 in 2022. You can check the release logs from ABP Framework Release Logs.
- The most important milestone in these releases is that we upgraded ABP Framework to .NET 7.0 in ABP v7.0.
- Additionally, we switched to OpenIddict for the startup templates in ABP v6.0.
-
-
- ABP Commercial
- It has been a successful year for ABP Commercial as well as ABP Framework. We have already reached to more than 100 countries over the years of ABP Commercial's release. This year, we continued to be streamline businesses' development processes with ABP Commercial.
-
- - We have served to different sizes of businesses from more than 50 countries and more than 40 industries .
-- We performed 286 hours of training to simplify users' learning curve of ABP Framework.
-- 1771 support tickets resolved in the premium support forum in which ABP Commercial users can ask their questions directly to ABP Core Team members via ABP Commercial Support Center in addition to community support we provide for ABP Framework users/developers.
-- We received 39 new testimonials, all from satisfied customers which led us to the other headline, Gartner Badges.
-
-
-
- LeptonX Theme
-The Lepton Theme is a module that offers a theme for abp.io-based applications, featuring an Admin Dashboard designed by the ABP Platform. We released a version we called LeptonX Theme which is an upgraded version of Lepton Theme. You can view a live preview of the LeptonX Theme. While the LeptonX theme is currently exclusive to ABP Commercial users, ABP Framework users can still access the Lite version. You can see the documentation for ABP LeptonX Theme light from here.
-
-
- Gartner Badges
- Gartner badges are given as an award to the listed softwares within their software review/suggestion platforms. To be able to get these awards, certain criterias have to be met such as ease of use, likelihood of recommend, functionality, etc. and they are calculated completely according to the users' real reviews.
- In 2022, ABP Commercial reached to such success thanks to its users' support on Gartner, it has been recognized with 2 badges in Application Development category.
-
- Thank you all for all these recognition you deemed us worthy of.
+ ABP Framework is an open source infrastructure that enables developers to create modern web applications by following the best practices and conventions of software development. In 2022, ABP Framework continued to thrive, achieving significant milestones and making waves in the software development community. With more than 9K GitHub stars and over 10 millions of downloads on NuGet, ABP Framework has become a go-to framework for developers seeking a reliable and efficient way to build web applications.
+
+
+
+As ABP Team, we owe our success to our vibrant community, and we are immensely grateful for the support and contributions of each and every member. With your help, we achieved a lot in 2022. We remained committed to our values of transparency, openness, and collaboration, engaging with our community members as much as possible to ensure that we are creating a framework that meets their needs.
+
+
+
+One of the major highlights of 2022 was the release of .NET Core 7, which provided a powerful platform for ABP Framework to build upon. Additionally, ABP Commercial and our training programs continued to help developers and businesses to leverage the power of the ABP Framework, enabling them to build modern web applications more efficiently and effectively than ever before.
+
+
+
+In this article, we'll take a closer look at the key highlights of 2022 for ABP Framework, from major updates to achivements and the community insights. We are excited to share our progress with you and provide insights into how ABP Framework is continuing to shape the future of software development. So, let's dive in!
+
+
+
+
+
+
+
+
+
+ NuGet Downloads
+
+ NuGet is a package manager designed specifically for the .NET ecosystem. It simplifies the process of creating and consuming packages, thanks to the NuGet client tools. By using these tools, developers can easily manage their project dependencies and improve their workflow.
+
+ In 2022, ABP Core NuGet package reached more than 10 million of downloads!
+
+ On the other hand, overall Volosoft NuGet Packages reached more than half a billion downloads!
+
+ Thank you all for your interest and support towards Volosoft and ABP packages.
+
+
+
+
+
+ E-Books
+
+ Our published e-book amount is reached 3! This year, with our founder Halil İbrahim Kalkan's contributions we now have 3 published e-books.
+
+
+
+
+
+
+
+ Tutorial Videos
+
+ In 2022, we tried to be as much active as we could. To give you more insight and let you understand ABP Framework with short videos according to your interests, we published 48 tutorial videos. Though the videos were created by overall team members of ABP Framework, someone deserves a special mention here. Shout out to our ABP Core Team member Hamza Albreem for his hard work.
+
+
+
+
+
+ GitHub Stars
+
+ ABP Framework GitHub repository reached more than 9K stars. We appreciate your interest and support for ABP Framework GitHub repository. We are working hard to be worthy of your interest and reach out to more people to simplify and streamline their development processes.
+
+
+
+ Community Talks
+
+ABP Community Talks is our monthly event that brings together members of the ABP Framework community to discuss and exchange ideas. Prior to each event, we collect suggestions from our contributors, monitor trending topics in the industry, and review updates and news related to the ABP Platform to curate the topics for discussion. Once the topics are finalized, we announce them through our social media and community channels to ensure everyone is aware and can join in on the conversation.
+
+ We did 10 ABP Community Talks Episodes of and 1 ABP Suite webinar. You can take a look at them and check out our videos we have on Volosoft YouTube Channel.
+
+
+
+ ABP Community Contributions
+
+ The ABP Community is a hub that offers resources such as articles, video tutorials, and updates on ABP's development progress and events for ABP Framework, .NET, and software development. Developers can also connect with others, help each other, and share their expertise in ABP Community.
+
+ You can check out each source from the list below.
+
+ - ABP Community Events: You can reach them from here.
+
+ - ABP Community Posts: You can reach them from here
+
+ - ABP Community Videos: You can reach them from here.
+
+ - ABP Community Stackoverflow: You can reach them from here.
+
+
+
+ In 2022, the community's contribution reached a point where more than 100 resources. Thank you for all your effort! Please keep it going! It is becoming a more and more rich resource thanks to your variety of contributions and help.
+
+
+
+
+
+ ABP Community Discord Server
+
+ To take community interaction to the next level, we created the official ABP Discord server, providing a platform for the ABP Community to connect and communicate instantly through chatting.
+
+ We were so excited announcing the official ABP Discord Server. In the first week of announcing it, the server quickly attracted over 500 members. We're grateful for your interest and support, which confirms the need for a dedicated platform for community interaction.
+
+> Join ABP Discord Server Now
+
+
+
+
+
+ ABP Framework GitHub Contributions
+
+ In 2022, ABP Core Team worked hard to achieve milestones and give the best value with ABP Framework so users can benefit from its features. Additional to our team's work, ABP Framework is perfected in 2022 with ABP Community members' contributions, 3157 commits pushed from 48 different contributors.
+
+ We appreciate your hard work and effort you put into making ABP Framework better and improved.
+
+
+
+
+
+ Events/Summits
+
+ We try to contribute to the developers community as much as we can since day 1. This year was no different. We tried to give value through sponsorships for developer communities. Especially with us leaving the pandemic behind every day, we try to keep up with the in-person events as well as online events. We plan to do more in next year. So, stay tuned!
+
+ This year, we sponsored to 4 events. They were, DevNot
+
+Designing Monolith First for Microservice Architecture event, DNF Summit 2022, Developer Summit 2022, and .NET Conference 2022.
+
+
+
+
+
+
ABP Releases
+
+ ABP Framework released 4 versions from 5.1 to 7.1 in 2022. You can check the release logs from ABP Framework Release Logs.
+
+ The most important milestone in these releases is that we upgraded ABP Framework to .NET 7.0 in ABP v7.0.
+
+ Additionally, we switched to OpenIddict for the startup templates in ABP v6.0.
+
+
+
+
+
+ ABP Commercial
+
+ It has been a successful year for ABP Commercial as well as ABP Framework. We have already reached to more than 100 countries over the years of ABP Commercial's release. This year, we continued to be streamline businesses' development processes with ABP Commercial.
+
+
+
+ - We have served to different sizes of businesses from more than 50 countries and more than 40 industries .
+
+- We performed 286 hours of training to simplify users' learning curve of ABP Framework.
+
+- 1771 support tickets resolved in the premium support forum in which ABP Commercial users can ask their questions directly to ABP Core Team members via ABP Commercial Support Center in addition to community support we provide for ABP Framework users/developers.
+
+- We received 39 new testimonials, all from satisfied customers which led us to the other headline, Gartner Badges.
+
+
+
+
+
+
+
+ LeptonX Theme
+
+The Lepton Theme is a module that offers a theme for abp.io-based applications, featuring an Admin Dashboard designed by the ABP Platform. We released a version we called LeptonX Theme which is an upgraded version of Lepton Theme. You can view a live preview of the LeptonX Theme. While the LeptonX theme is currently exclusive to ABP Commercial users, ABP Framework users can still access the Lite version. You can see the documentation for ABP LeptonX Theme light from here.
+
+
+
+
+
+ Gartner Badges
+
+ Gartner badges are given as an award to the listed softwares within their software review/suggestion platforms. To be able to get these awards, certain criterias have to be met such as ease of use, likelihood of recommend, functionality, etc. and they are calculated completely according to the users' real reviews.
+
+ In 2022, ABP Commercial reached to such success thanks to its users' support on Gartner, it has been recognized with 2 badges in Application Development category.
+
+
+
+ Thank you all for all these recognition you deemed us worthy of.
+
diff --git a/docs/en/Community-Articles/2024-11-25-Global-Assets/POST.md b/docs/en/Community-Articles/2024-11-25-Global-Assets/POST.md
index 33dd9eb292..e5196dde34 100644
--- a/docs/en/Community-Articles/2024-11-25-Global-Assets/POST.md
+++ b/docs/en/Community-Articles/2024-11-25-Global-Assets/POST.md
@@ -51,7 +51,7 @@ public class MyBlazorWebAssemblyBundlingModule : AbpModule
options.ScriptBundles.Get(BlazorWebAssemblyStandardBundles.Scripts.Global).AddContributors(typeof(MyModuleBundleScriptContributor));
// Style Bundles
- options.ScriptBundles.Get(BlazorWebAssemblyStandardBundles.Scripts.Global).AddContributors(typeof(MyModuleBundleStyleBundleContributor));
+ options.StyleBundles.Get(BlazorWebAssemblyStandardBundles.Styles.Global).AddContributors(typeof(MyModuleBundleStyleBundleContributor));
});
}
}
diff --git a/docs/en/Community-Articles/2025-06-20-Using-Hangfire-Dashboard-in-ABP-API-website/POST.md b/docs/en/Community-Articles/2025-06-20-Using-Hangfire-Dashboard-in-ABP-API-website/POST.md
new file mode 100644
index 0000000000..4fcb9860bc
--- /dev/null
+++ b/docs/en/Community-Articles/2025-06-20-Using-Hangfire-Dashboard-in-ABP-API-website/POST.md
@@ -0,0 +1,250 @@
+# Using Hangfire Dashboard in ABP API Website 🚀
+
+## Introduction
+
+In this article, I'll show you how to integrate and use the Hangfire Dashboard in an ABP API website.
+
+Typically, API websites use `JWT Bearer` authentication, but the Hangfire Dashboard isn't compatible with `JWT Bearer` authentication. Therefore, we need to implement `Cookies` and `OpenIdConnect` authentication for the Hangfire Dashboard access.
+
+## Creating a New ABP Demo Project 🛠️
+
+We'll create a new ABP Demo `Tiered` project that includes `AuthServer`, `API`, and `Web` projects.
+
+```bash
+abp new AbpHangfireDemoApp -t app --tiered
+```
+
+Now let's add the Hangfire Dashboard to the `API` project and configure it to use `Cookies` and `OpenIdConnect` authentication for accessing the dashboard.
+
+## Adding a New Hangfire Application 🔧
+
+We need to add a new Hangfire application to the `appsettings.json` file in the `DbMigrator` project:
+
+> **Note:** Replace `44371` with your `API` project's port.
+
+```json
+"OpenIddict": {
+ "Applications": {
+ //...
+ "AbpHangfireDemoApp_Hangfire": {
+ "ClientId": "AbpHangfireDemoApp_Hangfire",
+ "RootUrl": "https://localhost:44371/"
+ }
+ //...
+ }
+}
+```
+
+2. Update the `OpenIddictDataSeedContributor`'s `CreateApplicationsAsync` method in the `Domain` project to seed the new Hangfire application.
+
+```csharp
+ //Hangfire Client
+var hangfireClientId = configurationSection["AbpHangfireDemoApp_Hangfire:ClientId"];
+if (!hangfireClientId.IsNullOrWhiteSpace())
+{
+ var hangfireClientRootUrl = configurationSection["AbpHangfireDemoApp_Hangfire:RootUrl"]!.EnsureEndsWith('/');
+
+ await CreateApplicationAsync(
+ applicationType: OpenIddictConstants.ApplicationTypes.Web,
+ name: hangfireClientId!,
+ type: OpenIddictConstants.ClientTypes.Confidential,
+ consentType: OpenIddictConstants.ConsentTypes.Implicit,
+ displayName: "Hangfire Application",
+ secret: configurationSection["AbpHangfireDemoApp_Hangfire:ClientSecret"] ?? "1q2w3e*",
+ grantTypes: new List //Hybrid flow
+ {
+ OpenIddictConstants.GrantTypes.AuthorizationCode, OpenIddictConstants.GrantTypes.Implicit
+ },
+ scopes: commonScopes,
+ redirectUris: new List { $"{hangfireClientRootUrl}signin-oidc" },
+ postLogoutRedirectUris: new List { $"{hangfireClientRootUrl}signout-callback-oidc" },
+ clientUri: hangfireClientRootUrl,
+ logoUri: "/images/clients/aspnetcore.svg"
+ );
+}
+```
+
+3. Run the `DbMigrator` project to seed the new Hangfire application.
+
+### Adding Hangfire Dashboard to the `API` Project 📦
+
+1. Add the following packages and modules dependencies to the `API` project:
+
+```bash
+
+
+
+```
+
+```cs
+typeof(AbpBackgroundJobsHangfireModule),
+typeof(AbpAspNetCoreAuthenticationOpenIdConnectModule)
+```
+
+2. Add the `HangfireClientId` and `HangfireClientSecret` to the `appsettings.json` file in the `API` project:
+
+```csharp
+"AuthServer": {
+ "Authority": "https://localhost:44358",
+ "RequireHttpsMetadata": true,
+ "MetaAddress": "https://localhost:44358",
+ "SwaggerClientId": "AbpHangfireDemoApp_Swagger",
+ "HangfireClientId": "AbpHangfireDemoApp_Hangfire",
+ "HangfireClientSecret": "1q2w3e*"
+}
+```
+
+3. Add the `ConfigureHangfire` method to the `API` project to configure Hangfire:
+
+```csharp
+public override void ConfigureServices(ServiceConfigurationContext context)
+{
+ var configuration = context.Services.GetConfiguration();
+ var hostingEnvironment = context.Services.GetHostingEnvironment();
+
+ //...
+
+ //Add Hangfire
+ ConfigureHangfire(context, configuration);
+ //...
+}
+
+private void ConfigureHangfire(ServiceConfigurationContext context, IConfiguration configuration)
+{
+ context.Services.AddHangfire(config =>
+ {
+ config.UseSqlServerStorage(configuration.GetConnectionString("Default"));
+ });
+}
+```
+
+4. Modify the `ConfigureAuthentication` method to add new `Cookies` and `OpenIdConnect` authentication schemes:
+
+```csharp
+private void ConfigureAuthentication(ServiceConfigurationContext context, IConfiguration configuration)
+{
+ context.Services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
+ .AddAbpJwtBearer(options =>
+ {
+ options.Authority = configuration["AuthServer:Authority"];
+ options.RequireHttpsMetadata = configuration.GetValue("AuthServer:RequireHttpsMetadata");
+ options.Audience = "AbpHangfireDemoApp";
+
+ options.ForwardDefaultSelector = httpContext => httpContext.Request.Path.StartsWithSegments("/hangfire", StringComparison.OrdinalIgnoreCase)
+ ? CookieAuthenticationDefaults.AuthenticationScheme
+ : null;
+ })
+ .AddCookie(CookieAuthenticationDefaults.AuthenticationScheme)
+ .AddAbpOpenIdConnect(OpenIdConnectDefaults.AuthenticationScheme, options =>
+ {
+ options.Authority = configuration["AuthServer:Authority"];
+ options.RequireHttpsMetadata = Convert.ToBoolean(configuration["AuthServer:RequireHttpsMetadata"]);
+ options.ResponseType = OpenIdConnectResponseType.Code;
+
+ options.ClientId = configuration["AuthServer:HangfireClientId"];
+ options.ClientSecret = configuration["AuthServer:HangfireClientSecret"];
+
+ options.UsePkce = true;
+ options.SaveTokens = true;
+ options.GetClaimsFromUserInfoEndpoint = true;
+
+ options.Scope.Add("roles");
+ options.Scope.Add("email");
+ options.Scope.Add("phone");
+ options.Scope.Add("AbpHangfireDemoApp");
+
+ options.SignInScheme = CookieAuthenticationDefaults.AuthenticationScheme;
+ });
+
+ //...
+}
+```
+
+5. Add a custom middleware and `UseAbpHangfireDashboard` after `UseAuthorization` in the `OnApplicationInitialization` method:
+
+```csharp
+//...
+app.UseAuthorization();
+
+app.Use(async (httpContext, next) =>
+{
+ if (httpContext.Request.Path.StartsWithSegments("/hangfire", StringComparison.OrdinalIgnoreCase))
+ {
+ var authenticateResult = await httpContext.AuthenticateAsync(CookieAuthenticationDefaults.AuthenticationScheme);
+ if (!authenticateResult.Succeeded)
+ {
+ await httpContext.ChallengeAsync(
+ OpenIdConnectDefaults.AuthenticationScheme,
+ new AuthenticationProperties
+ {
+ RedirectUri = httpContext.Request.Path + httpContext.Request.QueryString
+ });
+ return;
+ }
+ }
+ await next.Invoke();
+});
+app.UseAbpHangfireDashboard("/hangfire", options =>
+{
+ options.AsyncAuthorization = new[]
+ {
+ new AbpHangfireAuthorizationFilter()
+ };
+});
+
+//...
+```
+
+Perfect! 🎉 Now you can run the `AuthServer` and `API` projects and access the Hangfire Dashboard at `https://localhost:44371/hangfire`.
+
+> **Note:** Replace `44371` with your `API` project's port.
+
+The first time you access the Hangfire Dashboard, you'll be redirected to the login page of the `AuthServer` project. After you log in, you'll be redirected back to the Hangfire Dashboard.
+
+
+
+## Key Points 🔑
+
+### 1. Authentication Scheme Selection
+
+The default authentication scheme in API websites is `JWT Bearer`. We've implemented `Cookies` and `OpenIdConnect` specifically for the Hangfire Dashboard.
+
+We've configured the `JwtBearerOptions`'s `ForwardDefaultSelector` to use `CookieAuthenticationDefaults.AuthenticationScheme` for Hangfire Dashboard requests.
+
+This means that if the request path starts with `/hangfire`, the request will be authenticated using the `Cookies` authentication scheme; otherwise, it will use the `JwtBearer` authentication scheme.
+
+```csharp
+options.ForwardDefaultSelector = httpContext => httpContext.Request.Path.StartsWithSegments("/hangfire", StringComparison.OrdinalIgnoreCase)
+ ? CookieAuthenticationDefaults.AuthenticationScheme
+ : null;
+```
+
+### 2. Custom Middleware for Authentication
+
+We've also implemented a custom middleware to handle `Cookies` authentication for the Hangfire Dashboard. If the current request isn't authenticated with the `Cookies` authentication scheme, it will be redirected to the login page.
+
+```csharp
+app.Use(async (httpContext, next) =>
+{
+ if (httpContext.Request.Path.StartsWithSegments("/hangfire", StringComparison.OrdinalIgnoreCase))
+ {
+ var authenticateResult = await httpContext.AuthenticateAsync(CookieAuthenticationDefaults.AuthenticationScheme);
+ if (!authenticateResult.Succeeded)
+ {
+ await httpContext.ChallengeAsync(
+ OpenIdConnectDefaults.AuthenticationScheme,
+ new AuthenticationProperties
+ {
+ RedirectUri = httpContext.Request.Path + httpContext.Request.QueryString
+ });
+ return;
+ }
+ }
+ await next.Invoke();
+});
+```
+
+## References 📚
+
+- [ABP Hangfire Background Job Manager](https://abp.io/docs/latest/framework/infrastructure/background-jobs/hangfire)
+- [Use cookie authentication in ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/security/authentication/cookie?view=aspnetcore-9.0)
diff --git a/docs/en/Community-Articles/2025-06-20-Using-Hangfire-Dashboard-in-ABP-API-website/gif.gif b/docs/en/Community-Articles/2025-06-20-Using-Hangfire-Dashboard-in-ABP-API-website/gif.gif
new file mode 100644
index 0000000000..e4fa879eb4
Binary files /dev/null and b/docs/en/Community-Articles/2025-06-20-Using-Hangfire-Dashboard-in-ABP-API-website/gif.gif differ
diff --git a/docs/en/Community-Articles/2025-07-17-summar-campaign/post.md b/docs/en/Community-Articles/2025-07-17-summar-campaign/post.md
new file mode 100644
index 0000000000..d1ac596c29
--- /dev/null
+++ b/docs/en/Community-Articles/2025-07-17-summar-campaign/post.md
@@ -0,0 +1,28 @@
+**It is going to get hotter with ABP’s Summer Campaign!**
+
+Since it’s summer time, we wanted to make it even hotter by announcing a summer campaign! From July 21 to 31 we are offering a 20% discount on all ABP licenses. Now is the best time to invest in ABP and start developing asp net applications faster without wasting your time with repetitive tasks.
+
+## Summer Campaign Terms
+
+Please review the following terms and conditions carefully.
+
+* This offer is available for extensions and new purchases.
+* Developer seat purchases are also included to the campaign.
+* Campaign is available from July 21st to July 31st.
+* Discounts are valid on selected licenses only.
+* This offer cannot be combined with other promotions or discounts.
+
+**Why Choose ABP?**
+
+ABP offers a powerful infrastructure, simplifying modern ASP.NET core development. It helps develop modern ASP.NET applications, including ASP.NET core MVC web applications, blazor front-end projects, and angular .NET Core solutions.
+
+-The core framework and pre-built modules are designed with microservice architecture in mind.
+-ABP provides a module system that allows you to develop reusable application modules.
+-Helps implement a DDD based layered architecture and build a maintainable code base.
+-Easily manage SaaS applications with integrated multi-tenancy, from database to UI.
+
+**This Offer Ends July 31, So Hurry Up!**
+
+This summer campaign is running from July 21 to July 31, so don’t miss your chance. Now is the perfect opportunity to enhance your asp net web development with ABP and benefit from our exclusive features.
+
+Get Your Discount Now: [https://abp.io/pricing?utm_source=abpwebsite&utm_medium=referral&utm_campaign=summer25_blog](https://abp.io/pricing?utm_source=abpwebsite&utm_medium=referral&utm_campaign=summer25_blog)
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/Drawings.pptx b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/Drawings.pptx
new file mode 100644
index 0000000000..7a59c08c25
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/Drawings.pptx differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md
new file mode 100644
index 0000000000..e63db935a5
--- /dev/null
+++ b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md
@@ -0,0 +1,480 @@
+# Multi-Tenancy with Separate Databases in .NET and ABP Framework
+
+[Multi-tenancy](https://abp.io/architecture/multi-tenancy) is a common architectural concept for modern SaaS applications, enabling a single application to serve multiple customers (each known as a tenant) while maintaining data isolation, scalability, and operational efficiency. The "Separate database per tenant" approach offers the highest level of data isolation, making it ideal for scenarios with strict data privacy, security, and performance requirements.
+
+In this article, we’ll explore how to use this advanced multi-tenancy model using the powerful capabilities of the ABP Framework and the .NET platform.
+
+> In this article, I will use [ABP Studio](https://abp.io/studio) for creating the application. ABP Studio allows to select "separate database per tenant" option only for [commercial licenses](https://abp.io/pricing).
+
+## Understanding Database Models for a Multi-Tenant Application
+
+In the next sections, I will explain various models for database models of a multi-tenant solution:
+
+* Single (shared) Database Model
+* Separate Tenant Databases Model
+* Hybrid Multi-Tenant Database Model
+
+Let's start with the first one...
+
+### Single (shared) Database Model
+
+In the shared database model, all the application data stored in a single physical database. In the following diagram, you see different kind of users use the application, and the application stored their data in a main database:
+
+
+
+This is the default behavior when you [create a new ABP application](https://abp.io/docs/latest/get-started), because it is simple to begin with and proper for most applications.
+
+In this model, a single database table may contain data of multiple tenants. Each row in these tables have a `TenantId` field which is used to distinguish the tenant data and isolate a tenant's data from other tenant users. To make your entities multi-tenant aware, all you have to do is to implement the `IMultiTenant` interface provided by the ABP Framework.
+
+Here, is an example `Product` entity that should support multi-tenancy:
+
+````csharp
+using System;
+using Volo.Abp.Domain.Entities;
+using Volo.Abp.MultiTenancy;
+
+namespace MtDemoApp
+{
+ public class Product : AggregateRoot, IMultiTenant //Implementing the interface
+ {
+ public Guid? TenantId { get; set; } //Defined by the IMultiTenant interface
+ public string Name { get; set; }
+ public float Price { get; set; }
+ }
+}
+````
+
+In this way, ABP Framework automatically isolates data using the `TenantId` property. You don't need to care about how to set `TenantId` or filter data when you need to query from database - all automated.
+
+### Separate Tenant Databases Model
+
+In the separate tenant database model, each tenant has a dedicated physical database (with a separate connection string), as shown below:
+
+
+
+ABP Framework can automatically select the right database from the current user's tenant context. Again, it is completely automated. You just need to set a connection string for a tenant, as we will do later in this article.
+
+Even each tenant has a separate database, we still need to a main database to store host-side data, like a table of tenants, their connection strings and some other management data for tenants. Also, tenant-independent (or tenant-shared) application data is stored in the main database.
+
+### Hybrid Multi-Tenant Database Model
+
+Lastly, you may want to have a hybrid model, where some tenants shares a single database (they don't have separate databases) but some of them have dedicated databases. In the following figure, Tenant C has its own physical database, but all other tenants data stored in the main database of the application.
+
+
+
+ABP Framework handles the complexity: If a tenant has a separate database it uses that tenant's database, otherwise it filters the tenant data by the `TenantId` field in shared tables.
+
+## Understanding the Separate Tenant Schema Approach
+
+When you create a new ABP solution, it has a single `DbContext` class (for Entity Framework Core) by default. It also includes the necessary EF Core code-first database migrations to create and update the database. As a result of this approach, the main database schema (tables and their fields) will be identical with a tenant database schema. As a drawback of that, tenant databases have some tables that are not meaningful and not used. For example, Tenants table (a list of tenants) will be created in the tenant database, but will never be used (because tenant list is stored in the main database).
+
+As a solution to that problem, ABP Studio provides a "Use separate tenant schema" option on the Multi-Tenancy step of the solution creation wizard:
+
+
+
+This option is only available for the [Layered Monolith (optionally Modular) Solution Template](https://abp.io/docs/latest/get-started/layered-web-application). We don't provide that option in other templates, because:
+
+* [Single-Layer](https://abp.io/docs/latest/get-started/single-layer-web-application) template is recommended for more simpler applications with an easy-to-understand architecture. We don't want to add these kind of complications in that template.
+* [Microservice](https://abp.io/docs/latest/get-started/microservice) template already has a separate database for each service. Having multiple database schema (and multiple `DbContext` classes) for each service makes it over complicated without bringing much value.
+
+While you can manually convert your applications so they support separate database schema approach (ABP is flexible), it is not recommended to do it for these solution types.
+
+> Note that "Separate database per tenant" approach is already supported by default for the Single-Layer template too. "Separate tenant schema" is something different as I explained in this section.
+
+## Creating a new Application
+
+Follow the *[Get Started tutorial](https://abp.io/docs/latest/get-started/layered-web-application)* to create a new ABP application. Remember to select the "*Use separate tenant schema*" option since I want to demonstrate it in this article.
+
+## Understanding the DbContext Structure
+
+When you open the solution in your IDE, you will see the following structure under the `.EntityFrameworkCore` project:
+
+
+
+There are 3 DbContext-related classes here (MtDemoApp is your application name):
+
+* `MtDemoAppDbContext` class is used to map entities for the main (host + shared) database.
+* `MtDemoAppTenantDbContext` class is used to map entities for tenant that have separate physical databases.
+* `MtDemoAppDbContextBase` is an abstract base class for the classes explained above. In this way, you can configure common mapping logic here.
+
+Let's see these classes a bit closer...
+
+### The Main `DbContext` Class
+
+Here the main `DbContext` class:
+
+````csharp
+public class MtDemoAppDbContext : MtDemoAppDbContextBase
+{
+ public MtDemoAppDbContext(DbContextOptions options)
+ : base(options)
+ {
+ }
+
+ protected override void OnModelCreating(ModelBuilder builder)
+ {
+ builder.SetMultiTenancySide(MultiTenancySides.Both);
+
+ base.OnModelCreating(builder);
+ }
+}
+````
+
+* It inherits from the `MtDemoAppDbContextBase` as I mentioned before. So, any configuration made in the base class is also valid here.
+* `OnModelCreating` overrides the base method and sets the multi-tenancy side as `MultiTenancySides.Both`. `Both` means this database can store host data as well as tenant data. This is needed because we store data in this database for the tenants who don't have a separate database.
+
+### The Tenant `DbContext` class
+
+Here is the tenant-specific `DbContext` class:
+
+````csharp
+public class MtDemoAppTenantDbContext : MtDemoAppDbContextBase
+{
+ public MtDemoAppTenantDbContext(DbContextOptions options)
+ : base(options)
+ {
+ }
+
+ protected override void OnModelCreating(ModelBuilder builder)
+ {
+ builder.SetMultiTenancySide(MultiTenancySides.Tenant);
+
+ base.OnModelCreating(builder);
+ }
+}
+````
+
+The only difference is that we used `MultiTenancySides.Tenant` as the multi-tenancy side here, since this `DbContext` will only have entities/tables for tenants that have separate databases.
+
+### The Base `DbContext` Class
+
+Here is the base `DbContext` class:
+
+````csharp
+public abstract class MtDemoAppDbContextBase : AbpDbContext
+ where TDbContext : DbContext
+{
+
+ public MtDemoAppDbContextBase(DbContextOptions options)
+ : base(options)
+ {
+
+ }
+
+ protected override void OnModelCreating(ModelBuilder builder)
+ {
+ base.OnModelCreating(builder);
+
+ /* Include modules to your migration db context */
+
+ builder.ConfigurePermissionManagement();
+ builder.ConfigureSettingManagement();
+ builder.ConfigureBackgroundJobs();
+ builder.ConfigureAuditLogging();
+ builder.ConfigureIdentityPro();
+ builder.ConfigureOpenIddictPro();
+ builder.ConfigureFeatureManagement();
+ builder.ConfigureLanguageManagement();
+ builder.ConfigureSaas();
+ builder.ConfigureTextTemplateManagement();
+ builder.ConfigureBlobStoring();
+ builder.ConfigureGdpr();
+
+ /* Configure your own tables/entities inside here */
+
+ //builder.Entity(b =>
+ //{
+ // b.ToTable(MtDemoAppConsts.DbTablePrefix + "YourEntities", MtDemoAppConsts.DbSchema);
+ // b.ConfigureByConvention(); //auto configure for the base class props
+ // //...
+ //});
+
+ //if (builder.IsHostDatabase())
+ //{
+ // /* Tip: Configure mappings like that for the entities only
+ * available in the host side,
+ // * but should not be in the tenant databases. */
+ //}
+ }
+}
+````
+
+This `DbContext` class configures database mappings for all the [application modules](https://abp.io/docs/latest/modules) used by this application by calling their extension methods, like `builder.ConfigureBackgroundJobs()`. Each of these extension methods are defined as multi-tenancy aware and care about what you've set for the multi-tenancy side.
+
+### Where to Configure Your Entities?
+
+You can configure your entity mappings in the `OnModelCreating` method in any of the `DbContext` classes that was explained:
+
+* If you configure in the main `DbContext` class, these configuration will be valid only for the main database. So, don't configure tenant-related configuration here, otherwise, it won't be applied for the tenants who have separate databases.
+* If you configure in the tenant `DbContext` class, it will be valid only for the tenants with separate databases. You rarely need to do that. You typically want to make same configuration in the base `DbContext` to support hybrid scenarios (some tenants use the main (shared) database and some tenants have separate databases).
+* If you configure in the base `DbContext` class, it will be valid for the main database and tenant databases. You typically define tenant-related configuration here. That means, if you have a multi-tenant `Product` entity, then you should define its EF Core database mapping configuration here, so the Products table is created in the main database as well as in the tenant databases.
+
+The recommended approach is to configure all the mapping in the base class, but add controls like `builder.IsHostDatabase()` and `builder.IsTenantDatabase()` to conditionally configure the mappings:
+
+
+
+## Adding Database Migrations
+
+In this section, I will show how to configure your entity mappings, generate database migrations and apply to the database.
+
+### Defining an Entity
+
+Let's define a `Product` entity in the `.Domain` layer of your application:
+
+````csharp
+using System;
+using Volo.Abp.Domain.Entities;
+using Volo.Abp.MultiTenancy;
+
+namespace MtDemoApp
+{
+ public class Product : AggregateRoot, IMultiTenant
+ {
+ public Guid? TenantId { get; set; }
+ public string Name { get; set; }
+ public float Price { get; set; }
+ }
+}
+````
+
+### Configuring the Database Mapping
+
+Open the `MtDemoAppDbContextBase` class and add the following property to the class:
+
+````csharp
+public DbSet Products { get; set; }
+````
+
+Then add the following mapping code inside the `OnModelCreating` method (after all other existing code):
+
+````csharp
+builder.Entity(b =>
+{
+ b.ToTable(MtDemoAppConsts.DbTablePrefix + "Products", MtDemoAppConsts.DbSchema);
+ b.ConfigureByConvention(); //auto-configure for the base class props
+ b.Property(x => x.Name).IsRequired().HasMaxLength(100);
+});
+````
+
+We made the configuration in the base class since the `Products` table should be created in all databases, not only in the main database.
+
+>`DbTablePrefix` and `DbSchema` are optional and configurable in your application. You can change or remove them.
+
+### Add a New Database Migration for the Main Database
+
+To add a new EF Core database migration, we can use ABP Studio UI or EF Core command-line commands. I will show both of these approaches here.
+
+#### Using the ABP Studio "Add Migrations" UI
+
+You can right-click the `.EntityFrameworkCore` package in the ABP Studio's *Solution Explorer* panel and select *EF Core CLI* -> *Add Migration* command as shown below:
+
+
+
+You set a migration name on the opened dialog:
+
+
+
+If you select the *Update Database* checkbox it will apply changes to the database after generating the migration code.
+
+Lastly, select the main DbContext class for this migration:
+
+
+
+This dialog is shown when your application has multiple `DbContext` classes. Once you click the *OK* button, a new migration class is added under the `Migrations` folder of the `.EntityFrameworkCore` project (you can see in your coding editor):
+
+
+
+Since we selected the *Update Database* option, the database table is also created. The following screenshot shows the `AppProducts` table (`App` is the default prefix for your tables, but you can change or remove it) in Microsoft SQL Server Management Studio:
+
+
+
+#### Using a Command-Line Terminal
+
+If you prefer to use the command-line terminal (instead of ABP Studio UI), open a command-line terminal in the directory of the `.EntityFrameworkCore` project. As a shortcut, you can right-click the `.EntityFrameworkCore` project in ABP Studio, then select *Open with* -> *Terminal* command as shown in the following figure:
+
+
+
+Then you can use the [EF Core command-line tool](https://learn.microsoft.com/en-us/ef/core/cli/dotnet) to add a new database migration:
+
+````bash
+dotnet ef migrations add "Added_Product_Entity" --context MtDemoAppDbContext
+````
+
+It is important to set the `--context` parameter since we have two DbContext classes in the same project.
+
+After adding the migration, you can update the database:
+
+````bash
+dotnet ef database update "Added_Product_Entity" --context MtDemoAppDbContext
+````
+
+> If you are using Visual Studio, you can also use the [Package Manager Console](https://learn.microsoft.com/en-us/ef/core/cli/powershell) inside your IDE to add migrations and update the database.
+
+### Add a New Database Migration for the Tenant Database
+
+We added a database migration for the main (shared) database. We also need to add a new database migration for tenants who have separate databases.
+
+This time, no need to configure the DbContext since we did it in the base DbContext class, so it is valid for both of the DbContext classes. Just right-click the `.EntityFrameworkCore` package in the ABP Studio's *Solution Explorer* panel and select *EF Core CLI* -> *Add Migration* command as shown below:
+
+
+
+You can set the same or a different migration name here:
+
+
+
+The important part is to select the Tenant DbContext in the next dialog, because we want to change the tenant database this time:
+
+
+
+After clicking the *OK* button, it will add a new database migration class, but this time to the `TenantMigrations` folder:
+
+
+
+ABP Studio is smart enough to select the right folder name for the new migration by mapping with the DbContext name. However, you could manually type `TenantMigrations` in the *Output directory* textbox.
+
+Since we selected the *Update Database* option, it also applied changes to the database. But, which database? Interestingly, it automatically creates a second database for tenants with the project name + `_Tenant` suffix:
+
+
+
+> This new database is never used on runtime or production. It is only created to allow you to see the schema (tables and their fields) on development time to be sure that everything is as expected. As you see, some tables (like `Saas*` and `OpenIddict*`) are not available in that database, since they are used on the host side and only necessary to be in the main database.
+>
+> So, where is the real tenant database? If a tenant's database is dedicated (separate), it is created on runtime as I will explain in the *Managing Tenant Databases and Connection Strings* section later.
+
+You can see that database's connection string in the `appsettings.development.json` file of the `.DbMigrator` project in the solution. If you want to understand how it works, you can check source code of the `DbContextFactory` classes in the `.EntityFrameworkCore` project:
+
+
+
+These factory classes are used to create `DbContext` instances when you execute *Add Migration* and *Update Database* commands.
+
+## Managing Tenant Databases and Connection Strings
+
+Until now, we even didn't run the application. It is the time to do it.
+
+### Running the Application with ABP Studio
+
+You can run the `.Web` project in your IDE. But I prefer to use ABP Studio's *[Solution Runner](https://abp.io/docs/latest/studio/running-applications)* feature here. You can open the *Solution Runner* panel in *ABP Studio* and click the play icon near to the solution root (`MyDemoApp`):
+
+
+
+Once the application runs (and you see the blue link icon near to it), right click and select the *Browse* command:
+
+
+
+It will open the application's UI in the built-in browser of ABP Studio. You can Login the application (with `admin` as user name and `1q2w3E*` as the default password) and navigate to the *Saas* -> *Tenants* page.
+
+### Creating a New Tenant with the Shared Database
+
+The *Tenants* page of the [SaaS module](https://abp.io/modules/Volo.SaaS) is shown below:
+
+
+
+As you see, there is no tenant at the beginning. I can click the *+ New tenant* button to create the first tenant:
+
+
+
+On this screen, we can set the base tenant information. If you click the *Database connection strings* tab, you can see the following UI:
+
+
+
+For this first tenant, I will keep it as default and use the shared (main) database for this tenant's data. After clicking the *Save* button, the tenant is created and an initial [data seed](https://abp.io/docs/latest/framework/infrastructure/data-seeding) operation is automatically performed for us. To see an example, you can open the database, show rows of the `AbpUsers` table:
+
+
+
+As you see, a new `admin` user has been created with a `TenantId`. The first row is the `admin` user of the host side. So, ABP allows to define same user name in different tenants, because their data (users in this example) are completely isolated from each other.
+
+### Sign in with the new Tenant
+
+We created a new tenant. In this step, we will sign in with the new tenant's `admin` user to see the application UI by that new tenant. To do that, we should logout from the host admin user first. Click the user name (`admin`) on the top right area of the application and select the *Log out* command:
+
+
+
+Click the *Login* button again, which redirects you to the *Login* page:
+
+
+
+In this page, click the *switch* button near to the *TENANT* selection area and type `acme` as *Name*:
+
+
+
+Once you click the *Save* button, you are now in the acme tenant's context. You can see it on the *TENANT* selection area:
+
+
+
+> This kind of tenant switch feature is very useful in development to quickly change tenants to test your application. However, in production, you typically want to use subdomain/domain names or another mechanism to determine tenants automatically. When you configure domain based resolution, the tenant selection area is automatically disappears from the login page. You can check the [multi-tenant document](https://abp.io/docs/latest/framework/architecture/multi-tenancy) to learn how to configure it.
+
+After switching to the `acme` tenant, we can use `admin` as user name and the password you set during the tenant creation (I had set it as `1q2w3E*`) to login to the application.
+
+Here a screenshot from the *Roles* page after signing in as the `acme` tenant's `admin` user:
+
+
+
+> Notice that each tenant has its own roles, users, permissions, and other data. If you change roles here, it doesn't affect other tenants or the host side.
+>
+> Also, you can see that there are less menu items compared to host side. For example, tenant management page is not available for tenants as you can expect.
+
+### Switch Back to the Host Side
+
+To switch back to the host side to add a new tenant, logout from the application, click the *Login* button again to open the login page and then again click the *switch* button to change the current tenant context:
+
+
+
+In this dialog, clear the *Name* field and then *Save* the dialog to switch back to the host side. Then you can use the standard `admin` user name with `1q2w3E*` password to login to the application as the host administrator.
+
+### Creating a New Tenant with a Separate Database
+
+Finally, we came to the point that we will create a new tenant with a separate, dedicated database. Open the *Tenants* page of the SaaS module and click the *+ New tenant* button:
+
+
+
+Just fill these information as you wish, then open the *Database connection strings* tab:
+
+
+
+Uncheck the *Use the shared database* option and set a connection string to the *Default connection string* for this tenant. I used `Server=(LocalDb)\MSSQLLocalDB;Database=MtDemoApp_Volosoft;Trusted_Connection=True;TrustServerCertificate=true` as the connection string value. The database name is `MtDemoApp_Volosoft`. You can Test the connection string to be sure that it is a valid connection string.
+
+Once you click the *Save* button, the new tenant is created, a new database is created on the fly, all the database migrations are applied and the initial data seed is performed. You can open the SQL Server Management Studio to see the new database:
+
+
+
+You can check the tables (e.g. `AbpUsers`) to see that only this new tenant's data is stored in this database. To test the application, switch to the Volosoft tenant (as like explained in the *Sign in with the new Tenant* section before), create a new role or user and check the database.
+
+## Migrating Existing Tenant Databases
+
+In the previous section, we've seen that a tenant database is automatically created on runtime if you set a connection string for that tenant. Also, all the current migrations are automatically applied to the database, so it becomes up to date.
+
+But what about existing tenant databases when a new migration is added to the application? Maybe you have a few tenants with their separate databases, or you may have thousands of tenants with separate databases. How will you apply database schema changes to all of these databases?
+
+The startup template comes with a solution to this problem. There is a `.DbMigrator` console application in the solution that is responsible to apply schema (table and their fields) changes to all of the databases in the system (the main database and all the separate tenant databases). It also executes the data seeding if seed data is available. All you need to do is to execute this application on your production environment while deploying a new version of your application (of course, it is also very useful in the development environment). It checks and upgrades all the databases before the new version of your application is deployed.
+
+Here is the console log screen when I run the `.DbMigrator` application on my development environment:
+
+
+
+As you can see in the logs, it first migrates for the main (host) database, then migrates the tenant databases one by one. It doesn't make schema migration for the `acme` tenant since it has not a separate database, but uses the main database.
+
+In brief, when you make changes on your entity classes;
+
+1) Add a new migration for the main DbContext class as I explained in this article.
+2) Add a new migration for the tenant DbContext class as I explained in this article.
+3) Run the `.DbMigrator` application in your development environment to ensure all the databases are up to date.
+4) When you deploy your application to production or test environments, remember to run the `.DbMigrator` application first, then update your application. Or better, setup a CI/CD pipeline that automates this process. You can run the `.DbMigrator` every time while deploying the application, regardless of whether there is a schema change or not.
+
+> If you have too many tenants with separate database, then the migration process may take too much time. `.DbMigrator` provides the fundamental solution. But for more advanced scenarios or bigger systems, you can always develop your own solution. Just check the `.DbMigrator` application to understand how it was implemented. All the necessary code located in your solution, so you can easily understand and freely customize.
+
+## Conclusion
+
+In this article, I covered two important aspects of multi-tenant application development:
+
+* How ABP startup templates provide a multi-tenant application setup, so some tenants may store their data in a single (main, shared) database while some others may have their own dedicated database.
+* Demonstrate how it can manage database migration process on the fly for multiple databases.
+
+I started by defining different database models for multi-tenant applications (Single database, separate databases, and hybrid), showed how to create an ABP application that supports hybrid model, explained the DbContext structure that is coming with the solution template, demonstrated how to define entities, create and apply database migrations in such an application.
+
+I hope this article gives you a good understanding the problem and the solution provided by the ABP Framework. Please write your questions or comments under this article.
+
+Enjoy coding! :)
+
+## Further Reading
+
+* [ABP Multi-Tenancy document](https://abp.io/docs/latest/framework/architecture/multi-tenancy)
+* [Multi-Tenancy Architecture with .NET](https://abp.io/architecture/multi-tenancy)
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-saas-tenants-page.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-saas-tenants-page.png
new file mode 100644
index 0000000000..9f3a0ce5ca
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-saas-tenants-page.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration-select-dbcontext.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration-select-dbcontext.png
new file mode 100644
index 0000000000..17b89bee80
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration-select-dbcontext.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration-set-name.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration-set-name.png
new file mode 100644
index 0000000000..9ff5ea75f4
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration-set-name.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration.png
new file mode 100644
index 0000000000..fe59e93230
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-add-migration.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-browse.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-browse.png
new file mode 100644
index 0000000000..3134203343
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-browse.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-context-selection.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-context-selection.png
new file mode 100644
index 0000000000..dc1a993088
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-context-selection.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-open-with-terminal.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-open-with-terminal.png
new file mode 100644
index 0000000000..17dd1fa4dd
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-open-with-terminal.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-solution-runner.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-solution-runner.png
new file mode 100644
index 0000000000..a246d01c81
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/abp-studio-solution-runner.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/acme-tenant-screen.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/acme-tenant-screen.png
new file mode 100644
index 0000000000..65f7aa5b48
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/acme-tenant-screen.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/added-product-entity-migration-main-context.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/added-product-entity-migration-main-context.png
new file mode 100644
index 0000000000..a727bcea86
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/added-product-entity-migration-main-context.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/added-product-entity-migration-tenant-context.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/added-product-entity-migration-tenant-context.png
new file mode 100644
index 0000000000..f77c5e1e75
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/added-product-entity-migration-tenant-context.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/builder-check-tenant-side.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/builder-check-tenant-side.png
new file mode 100644
index 0000000000..8b913d4292
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/builder-check-tenant-side.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/dbcontext-factories.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/dbcontext-factories.png
new file mode 100644
index 0000000000..b7f72d9a32
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/dbcontext-factories.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/dbmigrator-logs.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/dbmigrator-logs.png
new file mode 100644
index 0000000000..648d9ccaa8
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/dbmigrator-logs.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/hybrid-database-multi-tenancy.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/hybrid-database-multi-tenancy.png
new file mode 100644
index 0000000000..45930e7fb9
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/hybrid-database-multi-tenancy.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/multi-tenancy-dbcontext-structure.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/multi-tenancy-dbcontext-structure.png
new file mode 100644
index 0000000000..5bb7ad8410
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/multi-tenancy-dbcontext-structure.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-1.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-1.png
new file mode 100644
index 0000000000..76a2a33087
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-1.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-2.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-2.png
new file mode 100644
index 0000000000..614689552e
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-2.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-conn-string-1.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-conn-string-1.png
new file mode 100644
index 0000000000..5c6aee61d9
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-conn-string-1.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-conn-string-2.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-conn-string-2.png
new file mode 100644
index 0000000000..9404e38a26
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/new-tenant-dialog-conn-string-2.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/product-database-table.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/product-database-table.png
new file mode 100644
index 0000000000..58ef8463f2
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/product-database-table.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-database.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-database.png
new file mode 100644
index 0000000000..1ec6c36ad7
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-database.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-tenant-database-multi-tenancy.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-tenant-database-multi-tenancy.png
new file mode 100644
index 0000000000..69c2bb4940
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-tenant-database-multi-tenancy.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-tenant-schema-option.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-tenant-schema-option.png
new file mode 100644
index 0000000000..40c9c42770
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/separate-tenant-schema-option.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/single-shared-database.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/single-shared-database.png
new file mode 100644
index 0000000000..4363dc792e
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/single-shared-database.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/switch-host-side.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/switch-host-side.png
new file mode 100644
index 0000000000..e4e5f8943d
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/switch-host-side.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/switch-tenant-dialog.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/switch-tenant-dialog.png
new file mode 100644
index 0000000000..2828906d1e
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/switch-tenant-dialog.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/tenant-acme-name.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/tenant-acme-name.png
new file mode 100644
index 0000000000..a08537ee4e
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/tenant-acme-name.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/tenant-database.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/tenant-database.png
new file mode 100644
index 0000000000..32f7292e3c
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/tenant-database.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/user-login.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/user-login.png
new file mode 100644
index 0000000000..39cdac5aaf
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/user-login.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/user-logout.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/user-logout.png
new file mode 100644
index 0000000000..ae7885fa0e
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/user-logout.png differ
diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/users-table-new-tenant.png b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/users-table-new-tenant.png
new file mode 100644
index 0000000000..0433da73b5
Binary files /dev/null and b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/users-table-new-tenant.png differ
diff --git a/docs/en/Community-Articles/2025-07-31-How-to-build-persistent-background-jobs-with-abp-framework-and-quartz/Post.md b/docs/en/Community-Articles/2025-07-31-How-to-build-persistent-background-jobs-with-abp-framework-and-quartz/Post.md
new file mode 100644
index 0000000000..eb69c93908
--- /dev/null
+++ b/docs/en/Community-Articles/2025-07-31-How-to-build-persistent-background-jobs-with-abp-framework-and-quartz/Post.md
@@ -0,0 +1,548 @@
+
+# How to Build Persistent Background Jobs with ABP Framework and Quartz
+
+## Introduction
+
+In modern SaaS applications, automated background processing is essential for delivering reliable user experiences. Whether you're sending subscription reminders, processing payments, or generating reports, background jobs ensure critical tasks happen on schedule without blocking your main application flow.
+
+### What is `Quartz.NET`?
+
+`Quartz.NET` is a powerful, open-source job scheduling library for .NET applications that provides cron-based scheduling for complex time patterns, job persistence across application restarts, clustering support for high-availability scenarios, flexible trigger types, and the ability to pass parameters to jobs through job data maps. It's the de facto standard for enterprise-grade job scheduling in the .NET ecosystem.
+
+### Quartz Storage Options: In-Memory vs Persistent
+
+When configuring **Quartz**, you have two primary storage options, each with significant implications for how your application behaves:
+
+### 🧠 In-Memory Storage (`RAMJobStore`)
+- Keeps all job information in application memory.
+- **Very fast** – no database overhead.
+- **Volatile** – all jobs, triggers, and schedules are lost when the application stops or restarts.
+- Best suited for:
+ - Development environments.
+ - Scenarios where job loss is acceptable.
+
+### 🗃️ Persistent Storage (`JobStoreTX` or similar)
+- Stores all job information in a database.
+- **Reliable** – schedules persist across:
+ - Application restarts
+ - Server crashes
+ - Deployments
+- **Supports horizontal scaling** – multiple application instances can share the same job queue.
+- **Slight performance overhead** due to database I/O.
+- Best choice for:
+ - Production systems.
+ - Any scenario where **business continuity and reliability** are critical.
+
+### How ABP Simplifies Quartz Integration
+
+ABP handles Quartz configuration, dependency injection, and lifecycle management automatically. Developers define jobs using `QuartzBackgroundWorkerBase` and access services via `ICachedServiceProvider`, following ABP's standard conventions and leveraging optimal service caching for background job scenarios.
+
+### Benefits of the Integration
+
+- Full support for ABP’s cross-cutting concerns (e.g., multi-tenancy, localization)
+- Robust scheduling powered by Quartz
+- Built-in logging, error handling, and performance monitoring
+- Scales easily without modifying business logic
+
+### Real-World Use Case: Subscription Reminders
+
+In this tutorial, we'll build a subscription reminder system that monitors client subscriptions, identifies those nearing expiration, sends professional email reminders seven days before expiration, tracks reminder history to prevent duplicates, and runs automatically every day at 9:00 AM using Quartz scheduling with PostgreSQL persistence. This system demonstrates how ABP and Quartz work together to solve real business problems with clean, maintainable code that follows enterprise-grade patterns.
+
+## Installing and Configuring Quartz
+
+Getting Quartz up and running in an ABP application is straightforward thanks to ABP's dedicated integration package. We'll replace the default background job system with Quartz for persistent job storage and robust scheduling capabilities.
+
+### Adding the Quartz Package
+
+The easiest way to add Quartz support to your ABP application is using the ABP CLI. Open a terminal in your project directory and run:
+
+```bash
+abp add-package Volo.Abp.BackgroundWorkers.Quartz
+```
+
+This command automatically adds the necessary NuGet package reference and updates your module dependencies. The ABP CLI handles all the heavy lifting, ensuring you get the correct version that matches your ABP Framework version.
+
+### Configuring Quartz for Persistent Storage
+
+Once the package is installed, you need to configure Quartz to use your database (in my case it is PostgreSQL) for job persistence. This configuration goes in your main module's `PreConfigureServices` method:
+
+```csharp
+[DependsOn(
+ // ... other dependencies
+ typeof(AbpBackgroundJobsQuartzModule),
+ typeof(AbpBackgroundWorkersQuartzModule)
+)]
+public class MySaaSApplicationModule : AbpModule
+{
+ public override void PreConfigureServices(ServiceConfigurationContext context)
+ {
+ var hostingEnvironment = context.Services.GetHostingEnvironment();
+ var configuration = context.Services.GetConfiguration();
+
+ ConfigureAuthentication(context, configuration);
+ ConfigureUrls(configuration);
+ ConfigureImpersonation(context, configuration);
+ ConfigureQuartz(); // Add this line
+ }
+
+ private void ConfigureQuartz()
+ {
+ PreConfigure(options =>
+ {
+ options.Properties = new NameValueCollection
+ {
+ ["quartz.scheduler.instanceName"] = "QuartzScheduler",
+ ["quartz.jobStore.type"] = "Quartz.Impl.AdoJobStore.JobStoreTX, Quartz",
+ ["quartz.jobStore.tablePrefix"] = "qrtz_",
+ ["quartz.jobStore.dataSource"] = "myDS",
+ ["quartz.dataSource.myDS.connectionString"] = _configuration.GetConnectionString("Default"),
+ ["quartz.dataSource.myDS.provider"] = "Npgsql",
+ ["quartz.serializer.type"] = "json"
+ };
+ });
+ }
+}
+```
+
+This configuration tells Quartz to store all job information in your PostgreSQL database using tables prefixed with "qrtz_". The key points are:
+
+- **Job Store Type**: Uses ADO.NET with transaction support for reliable job persistence
+- **Connection String**: Shares your application's existing database connection
+- **Table Prefix**: Keeps Quartz tables separate with the "qrtz_" prefix
+- **JSON Serialization**: Makes job data readable and debuggable
+- **PostgreSQL Provider**: Uses Npgsql for optimal PostgreSQL integration
+
+When your application starts, ABP automatically initializes the Quartz scheduler with these settings. Any background workers you create will be registered and scheduled automatically, with their state persisted to the database for reliability across application restarts.
+
+For detailed installation options and advanced configuration scenarios, check the official [ABP documentation.](https://abp.io/docs/latest/framework/infrastructure/background-workers/quartz)
+
+
+## Database Setup for Quartz
+
+With Quartz configured for persistent storage, we need to create the necessary database tables where Quartz will store job definitions, triggers, and execution history. Rather than running SQL scripts directly against the database, we'll use Entity Framework migrations to maintain consistency with ABP's database management approach.
+
+### Creating an Empty Migration for Quartz Tables
+
+Instead of executing raw SQL scripts against the database, we created an empty Entity Framework migration and populated it with the required Quartz table definitions. This approach keeps all database changes within the migration system, ensuring they're version-controlled, repeatable, and consistent across different environments.
+
+To create the empty migration, we used the standard Entity Framework CLI command:
+
+```bash
+dotnet ef migrations add AddQuartzTables
+```
+
+This generates a new migration file with empty `Up` and `Down` methods that we can populate with the Quartz table creation scripts.
+
+### Adding Quartz SQL Schema to Migration
+
+Once the empty migration was created, we populated it with the PostgreSQL-specific SQL needed to create all Quartz tables. The SQL scripts were obtained from the official Quartz repository, which provides database schema scripts for various database providers:
+
+```csharp
+public partial class AddQuartzTables : Migration
+{
+ protected override void Up(MigrationBuilder migrationBuilder)
+ {
+ migrationBuilder.Sql(@"
+ CREATE TABLE qrtz_job_details (
+ sched_name VARCHAR(120) NOT NULL,
+ job_name VARCHAR(200) NOT NULL,
+ job_group VARCHAR(200) NOT NULL,
+ description VARCHAR(250) NULL,
+ job_class_name VARCHAR(250) NOT NULL,
+ is_durable BOOLEAN NOT NULL,
+ is_nonconcurrent BOOLEAN NOT NULL,
+ is_update_data BOOLEAN NOT NULL,
+ requests_recovery BOOLEAN NOT NULL,
+ job_data BYTEA NULL,
+ PRIMARY KEY (sched_name, job_name, job_group)
+ );
+
+ CREATE TABLE qrtz_triggers (
+ sched_name VARCHAR(120) NOT NULL,
+ trigger_name VARCHAR(200) NOT NULL,
+ trigger_group VARCHAR(200) NOT NULL,
+ job_name VARCHAR(200) NOT NULL,
+ job_group VARCHAR(200) NOT NULL,
+ -- ... additional columns and constraints
+ PRIMARY KEY (sched_name, trigger_name, trigger_group),
+ FOREIGN KEY (sched_name, job_name, job_group) REFERENCES qrtz_job_details(sched_name, job_name, job_group)
+ );
+
+ -- Additional tables: qrtz_simple_triggers, qrtz_cron_triggers,
+ -- qrtz_simprop_triggers, qrtz_blob_triggers, qrtz_calendars,
+ -- qrtz_paused_trigger_grps, qrtz_fired_triggers, qrtz_scheduler_state, qrtz_locks
+ ");
+ }
+
+ protected override void Down(MigrationBuilder migrationBuilder)
+ {
+ migrationBuilder.Sql(@"
+ DROP TABLE IF EXISTS qrtz_locks;
+ DROP TABLE IF EXISTS qrtz_scheduler_state;
+ -- ... drop all other Quartz tables in reverse order
+ DROP TABLE IF EXISTS qrtz_triggers;
+ DROP TABLE IF EXISTS qrtz_job_details;
+ ");
+ }
+}
+```
+
+The complete SQL scripts for all supported database providers, including PostgreSQL, MySQL, SQL Server, and others, can be found in the official `Quartz.NET` repository. You should use the script that matches your specific database provider and version requirements.
+
+### Why Use Migrations Instead of Direct SQL Scripts?
+
+This migration-based approach offers several important advantages over running SQL scripts directly:
+
+**Version Control Integration**: The migration becomes part of your codebase, tracked in source control alongside your application changes. This means every developer and deployment environment gets the exact same database schema.
+
+**Rollback Capability**: The `Down` method provides a clean way to remove Quartz tables if needed, something that's much harder to manage with standalone SQL scripts.
+
+**Environment Consistency**: Whether you're setting up a development machine, staging server, or production deployment, running DBMigrator or `dotnet ef database update` command ensures the same schema is created everywhere.
+
+**Integration with ABP's Database Management**: This approach aligns perfectly with how ABP manages all other database changes, keeping your database evolution strategy consistent.
+
+The Quartz tables created by this migration handle all aspects of job persistence - from storing job definitions and triggers to tracking execution history and managing scheduler state. With these tables in place, your Quartz scheduler can reliably persist jobs across application restarts and coordinate work across multiple application instances if needed.
+
+After creating this migration, running DBMigrator `dotnet ef database update` will create all the necessary Quartz infrastructure in your PostgreSQL database, ready to store and manage your background jobs.
+
+For complete SQL scripts for your specific database provider, visit the official [Quartz documentation.](https://www.quartz-scheduler.net/documentation/quartz-3.x/quick-start.html#creating-and-initializing-database)
+## Building the Business Logic
+
+Before implementing our Quartz background job, we needed to create the essential business entities and services that our subscription reminder system would work with. Since this article focuses on Quartz integration rather than general ABP development patterns, we'll keep this section brief and move quickly to the background job implementation.
+
+### Core Entities and Services
+
+For our subscription reminder system, we created the following core components:
+
+**Entities:**
+- **`Client`**: Represents customers with subscription information (Name, Email, SubscriptionEnd, IsActive)
+- **`ReminderLog`**: Tracks when reminder emails have been sent to prevent duplicates
+
+**Application Services:**
+- **`ClientAppService`**: Handles CRUD operations and provides methods to find clients with expiring subscriptions
+- **`ReminderLogAppService`**: Manages reminder history and prevents duplicate notifications
+- **`EmailService`**: Sends professional HTML reminder emails via SMTP
+
+**Data Transfer Objects (DTOs):**
+- Complete set of DTOs for both entities following ABP conventions
+- Input/output DTOs for all service operations
+
+### Business Logic Overview
+
+The system follows standard ABP patterns with entities inheriting from `FullAuditedAggregateRoot`, services implementing `ICrudAppService` interfaces, and proper AutoMapper configurations for entity-DTO mapping. We also included a data seeder to create sample clients for testing purposes.
+
+The key business methods our background job will use are:
+- `GetExpiringClientsAsync()` - Finds clients whose subscriptions expire in the next 7 days
+- `CreateAsync()` - Logs when a reminder has been sent
+- `SendSubscriptionExpiryReminderAsync()` - Sends professional email reminders
+
+### Focus on Background Operations
+
+Rather than diving deep into ABP entity creation, repository patterns, or service layer implementation details, we'll move directly to the heart of this article: implementing robust background jobs with Quartz. The entities and services we created simply provide the business context for our background job to operate within.
+
+The real value of this tutorial lies in showing how ABP's `QuartzBackgroundWorkerBase` integrates seamlessly with your business logic to create reliable, persistent background operations that survive application restarts and scale across multiple instances.
+
+Let's now implement the background job that ties everything together and demonstrates the power of ABP + Quartz integration.
+
+
+## Implementing the Background Job (The ABP Way)
+
+This is where the magic happens. ABP's integration with Quartz provides a clean, powerful way to create background jobs that follow framework conventions while leveraging Quartz's robust scheduling capabilities. Let's dive into how we implemented our subscription reminder job and explore the advanced features ABP provides.
+
+### Creating a QuartzBackgroundWorkerBase Job
+
+Instead of implementing Quartz's raw `IJob` interface, ABP provides `QuartzBackgroundWorkerBase`, which integrates seamlessly with ABP's dependency injection, logging, and lifecycle management systems:
+
+```csharp
+public class SubscriptionExpiryNotifierJob : QuartzBackgroundWorkerBase
+{
+ public SubscriptionExpiryNotifierJob()
+ {
+ // Configure the job to run daily at 9:00 AM
+ JobDetail = JobBuilder.Create()
+ .WithIdentity(nameof(SubscriptionExpiryNotifierJob))
+ .Build();
+
+ Trigger = TriggerBuilder.Create()
+ .WithIdentity(nameof(SubscriptionExpiryNotifierJob))
+ .WithCronSchedule("0 0 9 * * ?") // Every day at 9:00 AM
+ .Build();
+
+ ScheduleJob = async scheduler =>
+ {
+ if (!await scheduler.CheckExists(JobDetail.Key))
+ {
+ await scheduler.ScheduleJob(JobDetail, Trigger);
+ }
+ };
+ }
+
+ public override async Task Execute(IJobExecutionContext context)
+ {
+ // Use ICachedServiceProvider for better performance and proper scoping
+ var serviceProvider = ServiceProvider.GetRequiredService();
+
+ // These services will be cached and reused throughout the job execution
+ var clientAppService = serviceProvider.GetRequiredService();
+ var reminderLogAppService = serviceProvider.GetRequiredService();
+ var emailService = serviceProvider.GetRequiredService();
+
+ Logger.LogInformation("🔄 Starting subscription expiry notification job...");
+
+ // 1. Get clients expiring in 7 days
+ var expiringClients = await clientAppService.GetExpiringClientsAsync(7);
+
+ Logger.LogInformation("📋 Found {Count} clients with expiring subscriptions", expiringClients.Count);
+
+ // 2. Process each client
+ foreach (var client in expiringClients)
+ {
+ await ProcessClientAsync(client, emailService, reminderLogAppService);
+ }
+
+ Logger.LogInformation("✅ Job completed successfully");
+ }
+}
+```
+
+### Key Implementation Features
+
+**Constructor-Based Configuration**: Unlike traditional Quartz jobs that require external scheduling code, ABP's approach lets you define both the job and its schedule directly in the constructor. This keeps related configuration together and makes the job self-contained.
+
+**ABP Service Integration**: The `ICachedServiceProvider` gives you access to any service in ABP's dependency injection container, enabling you to use application services, repositories, domain services, or any other ABP component with optimized caching and proper scoping.
+
+**Built-in Logging**: The `Logger` property provides access to ABP's logging infrastructure, automatically including context like correlation IDs and tenant information in multi-tenant applications.
+
+**Custom Scheduling Logic**: The `ScheduleJob` property allows you to customize how the job gets registered with Quartz. In our example, we check if the job already exists before scheduling it, preventing duplicate registrations during application restarts.
+
+### Understanding Quartz Trigger Types
+
+Quartz provides several trigger types to handle different scheduling requirements. Choosing the right trigger type is crucial for your job's behavior and performance.
+
+#### CronTrigger - Complex Time-Based Scheduling
+
+CronTrigger uses cron expressions for sophisticated scheduling patterns. This is what we used for our daily subscription reminders:
+
+```csharp
+// Daily at 9:00 AM
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("DailyReminder")
+ .WithCronSchedule("0 0 9 * * ?")
+ .Build();
+
+// Every weekday at 2:30 PM
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("WeekdayReport")
+ .WithCronSchedule("0 30 14 ? * MON-FRI")
+ .Build();
+
+// First day of every month at midnight
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("MonthlyCleanup")
+ .WithCronSchedule("0 0 0 1 * ?")
+ .Build();
+```
+
+**Cron Expression Format**: `Seconds Minutes Hours Day-of-Month Month Day-of-Week Year(optional)`
+- `0 0 9 * * ?` = 9:00 AM every day
+- `0 */15 * * * ?` = Every 15 minutes
+- `0 0 12 ? * SUN` = Every Sunday at noon
+
+#### SimpleTrigger - Interval-Based Scheduling
+
+SimpleTrigger is perfect for jobs that need to run at regular intervals or a specific number of times:
+
+```csharp
+// Run every 30 seconds indefinitely
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("HealthCheck")
+ .StartNow()
+ .WithSimpleSchedule(x => x
+ .WithIntervalInSeconds(30)
+ .RepeatForever())
+ .Build();
+
+// Run every 5 minutes, but only 10 times
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("LimitedRetry")
+ .StartNow()
+ .WithSimpleSchedule(x => x
+ .WithIntervalInMinutes(5)
+ .WithRepeatCount(9)) // 0-based, so 9 = 10 executions
+ .Build();
+
+// One-time execution after 1 hour delay
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("DelayedCleanup")
+ .StartAt(DateTimeOffset.UtcNow.AddHours(1))
+ .Build();
+```
+
+#### CalendarIntervalTrigger - Calendar-Aware Intervals
+
+CalendarIntervalTrigger handles intervals that need to respect calendar boundaries:
+
+```csharp
+// Every month on the same day (handles varying month lengths)
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("MonthlyBilling")
+ .WithCalendarIntervalSchedule(x => x
+ .WithIntervalInMonths(1))
+ .Build();
+
+// Every week, starting Monday
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("WeeklyReport")
+ .WithCalendarIntervalSchedule(x => x
+ .WithIntervalInWeeks(1))
+ .Build();
+```
+
+#### DailyTimeIntervalTrigger - Time Windows
+
+DailyTimeIntervalTrigger runs jobs within specific time windows on certain days:
+
+```csharp
+// Every 2 hours between 8 AM and 6 PM, Monday through Friday
+Trigger = TriggerBuilder.Create()
+ .WithIdentity("BusinessHoursSync")
+ .WithDailyTimeIntervalSchedule(x => x
+ .OnMondayThroughFriday()
+ .StartingDailyAt(TimeOfDay.HourAndMinuteOfDay(8, 0))
+ .EndingDailyAt(TimeOfDay.HourAndMinuteOfDay(18, 0))
+ .WithIntervalInHours(2))
+ .Build();
+```
+
+### Choosing the Right Trigger Type
+
+For different scenarios, you'd choose different trigger types:
+
+- **Daily/Weekly/Monthly Operations**: Use **CronTrigger** for maximum flexibility
+- **High-Frequency Tasks**: Use **SimpleTrigger** for performance (every few seconds/minutes)
+- **Business Calendar Operations**: Use **CalendarIntervalTrigger** for month-end reports, quarterly tasks
+- **Business Hours Operations**: Use **DailyTimeIntervalTrigger** for operations that should only run during specific hours
+
+### Automatic Job Registration
+
+One of ABP's most powerful features is automatic job discovery and registration. When your application starts, ABP automatically:
+
+1. **Scans for Background Workers**: ABP discovers all classes inheriting from `QuartzBackgroundWorkerBase`
+2. **Registers with DI Container**: Each job is registered as a service in the dependency injection container
+3. **Schedules with Quartz**: ABP calls the `ScheduleJob` delegate to register the job with the Quartz scheduler
+4. **Handles Lifecycle**: ABP manages starting and stopping jobs with the application lifecycle
+
+This means you simply create your job class, and ABP handles everything else. No manual registration, no startup code, no configuration files - it just works.
+
+### Understanding Misfire Handling
+
+Misfires occur when a scheduled job cannot execute at its intended time, typically due to system downtime, resource constraints, or the scheduler being paused. Quartz provides several misfire instructions to handle these scenarios:
+
+#### CronTrigger Misfire Instructions
+
+For cron-based schedules like our daily reminder job, Quartz offers these misfire behaviors:
+
+**`MisfireInstruction.DoNothing`** (Default):
+```csharp
+Trigger = TriggerBuilder.Create()
+ .WithIdentity(nameof(SubscriptionExpiryNotifierJob))
+ .WithCronSchedule("0 0 9 * * ?", x => x.WithMisfireHandlingInstructionDoNothing())
+ .Build();
+```
+- Skips all missed executions
+- Waits for the next naturally scheduled time
+- Best for jobs where missing executions is acceptable
+
+**`MisfireInstruction.FireOnceNow`**:
+```csharp
+.WithCronSchedule("0 0 9 * * ?", x => x.WithMisfireHandlingInstructionFireAndProceed())
+```
+- Immediately executes one missed job upon recovery
+- Then continues with the normal schedule
+- Useful when you need to catch up on missed work
+
+**`MisfireInstruction.IgnoreMisfires`**:
+```csharp
+.WithCronSchedule("0 0 9 * * ?", x => x.WithMisfireHandlingInstructionIgnoreMisfires())
+```
+- Executes all missed jobs immediately upon recovery
+- Can cause a burst of executions after extended downtime
+- Use carefully to avoid overwhelming the system
+
+#### SimpleTrigger Misfire Instructions
+
+Simple triggers have their own set of misfire behaviors:
+
+**`MisfireInstruction.FireNow`**: Execute immediately when recovered
+**`MisfireInstruction.RescheduleNowWithExistingRepeatCount`**: Start over with remaining repeat count
+**`MisfireInstruction.RescheduleNowWithRemainingRepeatCount`**: Continue as if no misfire occurred
+**`MisfireInstruction.RescheduleNextWithExistingCount`**: Wait for next interval, keep original repeat count
+
+### Real-World Misfire Considerations
+
+For our subscription reminder system, we chose the default `DoNothing` behavior because:
+
+- **Business Logic**: Sending yesterday's reminder today might confuse customers
+- **Duplicate Prevention**: Our job checks for existing reminders, so running late won't cause duplicate emails
+- **Resource Management**: We avoid overwhelming the email system after extended downtime
+
+However, for other scenarios you might choose differently:
+- **Financial reporting**: Use `FireOnceNow` to ensure reports are always generated
+- **Data synchronization**: Use `IgnoreMisfires` to process all missed sync operations
+- **Cache warming**: Use `DoNothing` since stale cache warming provides no value
+
+### Advanced Job Features
+
+**Error Handling and Resilience**: Our job implementation includes comprehensive error handling for individual client processing, ensuring one failed email doesn't stop the entire batch:
+
+```csharp
+try
+{
+ await emailService.SendSubscriptionExpiryReminderAsync(/*...*/);
+ await LogReminderAsync(client.Id, client.SubscriptionEnd, "Email sent successfully", reminderLogAppService);
+}
+catch (Exception ex)
+{
+ Logger.LogError(ex, "❌ Failed to send reminder to {ClientName}", client.Name);
+ await LogReminderAsync(client.Id, client.SubscriptionEnd, $"Failed: {ex.Message}", reminderLogAppService);
+}
+```
+
+**Duplicate Prevention**: The job checks for existing reminders to prevent sending multiple emails on the same day, even if the job runs multiple times:
+
+```csharp
+private async Task AlreadySentTodayAsync(Guid clientId, IReminderLogAppService reminderLogAppService)
+{
+ var todayReminders = await reminderLogAppService.GetByClientIdAsync(clientId);
+ var today = DateTime.UtcNow.Date;
+
+ return todayReminders.Any(r => r.ReminderDate.Date == today);
+}
+```
+
+This implementation demonstrates how ABP's `QuartzBackgroundWorkerBase` provides a clean, powerful foundation for building robust background jobs that integrate seamlessly with your business logic while leveraging Quartz's enterprise-grade scheduling capabilities.
+
+## Conclusion
+
+You've successfully built a production-ready subscription reminder system that demonstrates the powerful synergy between ABP Framework and `Quartz.NET`. This isn't just a tutorial example - it's a robust, enterprise-grade solution that handles real business requirements.
+
+### What We Accomplished
+
+**✅ Enterprise-Grade Reliability**: PostgreSQL persistence ensures jobs survive restarts and deployments
+**✅ ABP Best Practices**: Used `QuartzBackgroundWorkerBase`, `ICachedServiceProvider`, and ABP's logging infrastructure
+**✅ Real Business Value**: Automated subscription reminders with duplicate prevention and audit logging
+**✅ Flexible Scheduling**: Explored cron expressions, trigger types, and misfire handling strategies
+
+### The Power of ABP + Quartz Integration
+
+The combination delivers exceptional value through automatic job discovery, persistent scheduling, built-in dependency injection, and seamless framework integration. You get enterprise reliability with developer-friendly simplicity.
+
+### Final Thoughts
+
+Complex background processing doesn't have to be complicated to implement. ABP's thoughtful abstractions combined with Quartz's proven engine create a development experience that's both powerful and enjoyable.
+
+Whether you're building subscription management, financial reporting, or data synchronization, these patterns provide a solid foundation for reliable, maintainable solutions.
+
+You can reach sample project's source code from [here](https://github.com/MansurBesleney/MySaaSApplication)
+
+**Happy coding, and may your background jobs never miss a beat!** 🚀
diff --git a/docs/en/Community-Articles/2025-08-12-Integration-Services-Explained/integration-services.jpeg b/docs/en/Community-Articles/2025-08-12-Integration-Services-Explained/integration-services.jpeg
new file mode 100644
index 0000000000..19b1392843
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-12-Integration-Services-Explained/integration-services.jpeg differ
diff --git a/docs/en/Community-Articles/2025-08-12-Integration-Services-Explained/post.md b/docs/en/Community-Articles/2025-08-12-Integration-Services-Explained/post.md
new file mode 100644
index 0000000000..0e11c505da
--- /dev/null
+++ b/docs/en/Community-Articles/2025-08-12-Integration-Services-Explained/post.md
@@ -0,0 +1,138 @@
+# Integration Services in ABP — What they are, when to use them, and how they behave 🚦
+
+If you’ve been building with ABP for a while, you’ve probably used Application Services for your UI and APIs in your .NET and ASP.NET Core apps. Integration Services are similar—but with a different mission: they exist for service-to-service or module-to-module communication, not for end users.
+
+If you want the formal spec, see the official doc: [Integration Services](../../framework/api-development/integration-services.md). This post is the practical, no-fluff guide.
+
+## What is an Integration Service?
+
+An Integration Service is an application service or ASP.NET Core MVC controller marked with the `[IntegrationService]` attribute. That marker tells ABP “this endpoint is for internal communication.”
+
+- They are not exposed by default (safer for reusable modules and monoliths).
+- When exposed, their route prefix is `/integration-api` (so you can easily protect them at your gateway or firewall).
+- Auditing is disabled by default for them (less noise for machine-to-machine calls).
+
+Quick look:
+
+```csharp
+[IntegrationService]
+public interface IProductIntegrationService : IApplicationService
+{
+ Task> GetProductsByIdsAsync(List ids);
+}
+
+public class ProductIntegrationService : ApplicationService, IProductIntegrationService
+{
+ public Task> GetProductsByIdsAsync(List ids)
+ {
+ // fetch and return minimal product info for other services/modules
+ }
+}
+```
+
+## Are they HTTP endpoints?
+
+- By default: no (they won’t be reachable over HTTP in the ASP.NET Core routing pipeline).
+- If you need them over HTTP (typically for microservices), explicitly enable:
+
+```csharp
+Configure(options =>
+{
+ options.ExposeIntegrationServices = true;
+});
+```
+
+Once exposed, ABP puts them under `/integration-api/...` instead of `/api/...` in the ASP.NET Core routing pipeline. That’s your hint to restrict them from public internet access.
+
+## Enable auditing (optional)
+
+If you want audit logs for integration calls, enable it explicitly:
+
+```csharp
+Configure(options =>
+{
+ options.IsEnabledForIntegrationServices = true;
+});
+```
+
+## When should you use Integration Services?
+
+- Internal, synchronous operations between services or modules.
+- You need a “thin” API designed for other services (not for UI): minimal DTOs, no view concerns, predictable contracts.
+- You want to hide these endpoints from public clients, or only allow them inside your private network or k8s cluster.
+- You’re packaging a reusable module that might be used in both monolith and microservice deployments.
+
+## When NOT to use them
+
+- Public APIs or anything intended for browsers/mobile apps → use regular application services/controllers.
+- Asynchronous cross-service workflows → consider domain events + outbox/inbox; use Integration Services for sync calls.
+- Complex, chatty UI endpoints → those belong to your external API surface, not internal integration.
+
+## Common use-cases and examples
+
+- Identity lookups across services: an Ordering service needs basic user info from the Identity service.
+- Permission checks from another module: a CMS module asks a Permission service for access decisions.
+- Product data hydrations: a Cart service needs minimal product details (price, name) from Catalog.
+- Internal admin/maintenance operations that aren’t meant for end users but are needed by other services.
+
+## Example: microservice-to-microservice call
+
+1) Mark and expose the integration service in the target service:
+
+```csharp
+[IntegrationService]
+public interface IUserIntegrationService : IApplicationService
+{
+ Task FindByIdAsync(Guid id);
+}
+
+Configure(o => o.ExposeIntegrationServices = true);
+```
+
+2) In the caller service, add an HTTP client proxy only for Integration Services if you like to keep things clean:
+
+```csharp
+services.AddHttpClientProxies(
+ typeof(TargetServiceApplicationModule).Assembly,
+ remoteServiceConfigurationName: "TargetService",
+ asDefaultServices: true,
+ applicationServiceTypes: ApplicationServiceTypes.IntegrationServices);
+```
+
+3) Call it just like a local service (ABP’s HTTP proxy handles the wire):
+
+```csharp
+public class OrderAppService : ApplicationService
+{
+ private readonly IUserIntegrationService _userIntegrationService;
+
+ public OrderAppService(IUserIntegrationService userIntegrationService)
+ {
+ _userIntegrationService = userIntegrationService;
+ }
+
+ public async Task PlaceOrderAsync(CreateOrderDto input)
+ {
+ var user = await _userIntegrationService.FindByIdAsync(CurrentUser.GetId());
+ // validate user status, continue placing order...
+ }
+}
+```
+
+## Monolith vs. Microservices
+
+- Monolith: keep them unexposed and call via DI in-process. You get the same clear contract with zero network overhead.
+- Microservices: expose them and route behind your gateway. The `/integration-api` prefix makes it easy to firewall/gateway-restrict.
+
+## Practical tips
+
+- Keep integration DTOs lean and stable. These are machine contracts—don’t mix UI concerns.
+- Name them clearly (e.g., `UserIntegrationService`) so intent is obvious.
+- Guard your ASP.NET Core gateway application: block `/integration-api/*` from public traffic.
+- Enable auditing only if you truly need the logs for these calls.
+
+## Further reading
+
+- Official docs: [Integration Services](../../framework/api-development/integration-services.md)
+
+That’s it! Integration Services give you a clean, intentional way to design internal APIs—great in monoliths, essential in microservices.
diff --git a/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/0-cover.png b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/0-cover.png
new file mode 100644
index 0000000000..4864281a32
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/0-cover.png differ
diff --git a/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/1-pipeline-yaml.png b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/1-pipeline-yaml.png
new file mode 100644
index 0000000000..63cebfca62
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/1-pipeline-yaml.png differ
diff --git a/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/3-release.png b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/3-release.png
new file mode 100644
index 0000000000..a974610907
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/3-release.png differ
diff --git a/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/4-safe-deploy.png b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/4-safe-deploy.png
new file mode 100644
index 0000000000..c5771a8447
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/4-safe-deploy.png differ
diff --git a/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/5-summarizing.png b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/5-summarizing.png
new file mode 100644
index 0000000000..5afe59b991
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/5-summarizing.png differ
diff --git a/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/POST.md b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/POST.md
new file mode 100644
index 0000000000..e297aedb13
--- /dev/null
+++ b/docs/en/Community-Articles/2025-08-19-Best-Practices-Azure-Devops/POST.md
@@ -0,0 +1,83 @@
+# 🚀 Best Practices for Azure DevOps CI/CD Pipelines
+
+**CI/CD (Continuous Integration / Continuous Delivery)** is not just fancy tech talk - it's now a must-have for modern software teams.
+Microsoft's **Azure DevOps** helps make these processes easier to manage.
+But how do you create pipelines that work well for your team? Let's look at some practical tips that will make your life easier.
+
+---
+
+## 1. 📜 Define Your Pipeline as Code
+
+Don't use the manual setup method that's hard to track. Azure DevOps lets you use **YAML files** for your pipelines, which gives you:
+
+- A record of all changes - who made them and when
+- The same setup across all environments
+- The ability to undo changes when something goes wrong
+
+This stops the common problem where something works on one computer but not another.
+
+
+
+---
+
+## 2. 🔑 Store Sensitive Information Safely
+
+Never put passwords directly in your code, even temporarily.
+Each environment should have its own settings, and keep sensitive information in **Azure Key Vault** or **Library Variable Groups**.
+
+You'll avoid security problems later.
+
+
+---
+
+## 3. 🏗️ Keep Building and Releasing Separate
+
+Think of **Building** like cooking a meal - you prepare everything and package it up.
+**Releasing** is like delivering that meal to different people.
+
+Keeping these as separate steps means:
+
+- You create your package once, then send it to multiple places
+- You save time and resources by not rebuilding the same thing over and over
+
+
+
+---
+
+## 4. 🧪 Add Automatic Testing
+
+Don't waste time testing the same things manually over and over.
+Set up **different types of tests** to run automatically. When tests run every time you make changes:
+
+- You catch problems before your customers do
+- Your software quality stays high without extra manual work
+
+Azure DevOps has tools to help you see test results easily without searching through technical logs.
+
+---
+
+## 5. 🛡️ Add Safety Checks
+
+Automatic doesn't mean pushing everything to your live system right away.
+For important environments, add **human approval steps** or **automatic checks** like security scans.
+
+This helps you avoid emergency problems in the middle of the night.
+
+
+
+
+---
+
+## ✅ Conclusion
+
+Good Azure DevOps pipelines aren't just about automation - they help you feel confident in your process.
+Remember these main points:
+
+✔ Use YAML files to keep everything visible and trackable
+✔ Keep passwords and sensitive data in secure storage (not in your code)
+✔ Build once, deploy to many places
+✔ Let automatic tests find problems before users do
+✔ Add safety checks for important systems
+
+
+---
diff --git a/docs/en/Community-Articles/2025-08-19-abp-now-supports-angular-standalone-applications/POST.md b/docs/en/Community-Articles/2025-08-19-abp-now-supports-angular-standalone-applications/POST.md
new file mode 100644
index 0000000000..1f5c284cb1
--- /dev/null
+++ b/docs/en/Community-Articles/2025-08-19-abp-now-supports-angular-standalone-applications/POST.md
@@ -0,0 +1,398 @@
+# ABP Now Supports Angular Standalone Applications
+
+We are excited to announce that **ABP now supports Angular’s standalone component structure** in the latest Studio update. This article walks you through how to generate a standalone application, outlines the migration steps, and highlights the benefits of this shift over traditional module-based architecture.
+
+---
+
+## Why Standalone?
+
+Angular's standalone component architecture, which is introduced in version 14 and made default in version 19, is a major leap forward for Angular development. Here is why it matters:
+
+### 🔧 Simplified Project Structure
+
+Standalone components eliminate the need for `NgModule` wrappers. This leads to:
+
+- Fewer files to manage
+- Cleaner folder organization
+- Reduced boilerplate
+
+Navigating and understanding your codebase becomes easier for everyone on your team.
+
+### 🚀 Faster Bootstrapping
+
+Standalone apps simplify app initialization:
+
+```ts
+bootstrapApplication(AppComponent, appConfig);
+```
+
+This avoids the need for `AppModule` and speeds up startup times.
+
+### 📦 Smaller Bundle Sizes
+
+Since components declare their own dependencies, Angular can more effectively tree-shake unused code. Result? Smaller bundle sizes and faster load times.
+
+### 🧪 Easier Testing & Reusability
+
+Standalone components are self-contained. They declare their dependencies within the `imports` array, making them:
+
+- Easier to test in isolation
+- Easier to reuse in different contexts
+
+### 🧠 Clearer Dependency Management
+
+Standalone components explicitly define what they need. No more hidden dependencies buried in shared modules.
+
+### 🔄 Gradual Adoption
+
+You can mix and match standalone and module-based components. This allows for **incremental migration**, reducing risk in larger codebases. Here is the related document for the [standalone migration](https://angular.dev/reference/migrations/standalone).
+
+---
+
+## Getting Started: Creating a Standalone Angular App
+
+Angular CLI makes it easy to start:
+
+```bash
+ng new my-app
+```
+
+With Angular 19, new apps follow this bootstrapping model:
+
+```ts
+// main.ts
+import { bootstrapApplication } from "@angular/platform-browser";
+import { appConfig } from "./app/app.config";
+import { AppComponent } from "./app/app.component";
+
+bootstrapApplication(AppComponent, appConfig).catch((err) =>
+ console.error(err)
+);
+```
+
+The `app.config.ts` file replaces `AppModule`:
+
+```ts
+// app.config.ts
+import { ApplicationConfig, provideZoneChangeDetection } from "@angular/core";
+import { provideRouter } from "@angular/router";
+import { routes } from "./app.routes";
+
+export const appConfig: ApplicationConfig = {
+ providers: [
+ provideZoneChangeDetection({ eventCoalescing: true }),
+ provideRouter(routes),
+ ],
+};
+```
+
+Routing is defined in a simple `Routes` array:
+
+```ts
+// app.routes.ts
+import { Routes } from "@angular/router";
+
+export const routes: Routes = [];
+```
+
+---
+
+## ABP Studio Support for Standalone Structure
+
+Starting with the latest release (insert version number here), ABP Studio fully supports Angular's standalone structure. While the new format is encouraged, module-based structure will continue to be supported for backwards compatibility.
+
+To try it out, simply update your ABP Studio to create apps with the latest version.
+
+---
+
+## What’s New in ABP Studio Templates?
+
+When you generate an app using the latest ABP Studio, the project structure aligns with Angular's standalone architecture.
+
+This migration is split into four parts:
+
+1. **Package updates**
+2. **Schematics updates**
+3. **Suite code generation updates**
+4. **Template refactors**
+
+---
+
+## Package Migration Details
+
+Migration has been applied to packages in the [ABP GitHub repository](https://github.com/abpframework/abp/tree/dev/npm/ng-packs/packages). Here is an example from the Identity package.
+
+### 🧩 Migrating Components
+
+Components are made standalone, using:
+
+```bash
+ng g @angular/core:standalone
+```
+
+Example:
+
+```ts
+@Component({
+ selector: 'abp-roles',
+ templateUrl: './roles.component.html',
+ providers: [...],
+ imports: [
+ ReactiveFormsModule,
+ LocalizationPipe,
+ ...
+ ],
+})
+export class RolesComponent implements OnInit { ... }
+```
+
+### 🛣 Updating Routing
+
+Old lazy-loaded routes using `forLazy()`:
+
+```ts
+{
+ path: 'identity',
+ loadChildren: () => import('@abp/ng.identity').then(m => m.IdentityModule.forLazy({...}))
+}
+```
+
+Now replaced with:
+
+```ts
+{
+ path: 'identity',
+ loadChildren: () => import('@abp/ng.identity').then(c => c.createRoutes({...}))
+}
+```
+
+### 🧱 Replacing Module Declarations
+
+The old setup:
+
+```ts
+// identity.module.ts
+@NgModule({
+ imports: [IdentityRoutingModule, RolesComponent, UsersComponent],
+})
+export class IdentityModule {...}
+```
+
+```ts
+//identity-routing.module
+const routes: Routes = [...];
+@NgModule({
+ imports: [RouterModule.forChild(routes)],
+ exports: [RouterModule],
+})
+export class IdentityRoutingModule {}
+```
+
+New setup:
+
+```ts
+// identity-routes.ts
+export function provideIdentity(options: IdentityConfigOptions = {}): Provider[] {
+ return [...];
+}
+export const createRoutes = (options: IdentityConfigOptions = {}): Routes => [
+ {
+ path: '',
+ component: RouterOutletComponent,
+ providers: provideIdentity(options),
+ children: [
+ {
+ path: 'roles',
+ component: ReplaceableRouteContainerComponent,
+ data: {
+ requiredPolicy: 'AbpIdentity.Roles',
+ replaceableComponent: {
+ key: eIdentityComponents.Roles,
+ defaultComponent: RolesComponent,
+ },
+ },
+ title: 'AbpIdentity::Roles',
+ },
+ ...
+ ],
+ },
+];
+```
+
+---
+
+## ABP Schematics Migration Details
+
+You can reach details by checking [ABP Schematics codebase](https://github.com/abpframework/abp/tree/dev/npm/ng-packs/packages/schematics).
+
+### 📚 Library creation
+
+When you run the `abp create-lib` command, the prompter will ask you the `templateType`. It supports both module and standalone templates.
+
+```ts
+"templateType": {
+ "type": "string",
+ "description": "Type of the template",
+ "enum": ["module", "standalone"],
+ "x-prompt": {
+ "message": "Select the type of template to generate:",
+ "type": "list",
+ "items": [
+ { "value": "module", "label": "Module Template" },
+ { "value": "standalone", "label": "Standalone Template" }
+ ]
+ }
+},
+```
+
+---
+
+## ABP Suite Code Generation Migration Details
+
+ABP Suite will also be supporting both structures. If you have a project that is generated with the previous versions, the Suite will detect the structure in that way and generate the related code accordingly. Conversely, here is what is changed for the standalone migration:
+
+**❌ Discarded module files**
+
+```ts
+// entity-one.module.ts
+@NgModule({
+ declarations: [],
+ imports: [EntityOneComponent, EntityOneRoutingModule],
+})
+export class EntityOneModule {}
+```
+
+```ts
+// entity-one-routing.module.ts
+export const routes: Routes = [
+ {
+ path: "",
+ component: EntityOneComponent,
+ canActivate: [authGuard, permissionGuard],
+ },
+];
+
+@NgModule({
+ imports: [RouterModule.forChild(routes)],
+ exports: [RouterModule],
+})
+export class EntityOneRoutingModule {}
+```
+
+```ts
+// app-routing.module.ts
+{
+ path: 'entity-ones',
+ loadChildren: () =>
+ import('./entity-ones/entity-one/entity-one.module').then(m => m.EntityOneModule),
+},
+```
+
+**✅ Added routes configuration**
+
+```ts
+// entity-one.routes.ts
+export const ENTITY_ONE_ROUTES: Routes = [
+ {
+ path: "",
+ loadComponent: () => {
+ return import("./components/entity-one.component").then(
+ (c) => c.EntityOneComponent
+ );
+ },
+ canActivate: [authGuard, permissionGuard],
+ },
+];
+```
+
+```ts
+// app.routes.ts
+{ path: 'entity-ones', children: ENTITY_ONE_ROUTES },
+```
+
+---
+
+## Template Migration Details
+
+### 🧭 Routing: `app.routes.ts`
+
+```ts
+// app.routes.ts
+import { Routes } from '@angular/router';
+
+export const APP_ROUTES: Routes = [
+ {
+ path: '',
+ pathMatch: 'full',
+ loadComponent: () => import('./home/home.component').then(m => m.HomeComponent),
+ },
+ {
+ path: 'account',
+ loadChildren: () => import('@abp/ng.account').then(m => m.createRoutes()),
+ },
+ ...
+];
+```
+
+### ⚙ Configuration: `app.config.ts`
+
+```ts
+// app.config.ts
+export const appConfig: ApplicationConfig = {
+ providers: [
+ provideRouter(APP_ROUTES),
+ APP_ROUTE_PROVIDER,
+ provideAbpCore(
+ withOptions({
+ environment,
+ registerLocaleFn: registerLocale(),
+ ...
+ })
+ ),
+ provideAbpOAuth(),
+ provideAbpThemeShared(),
+ ...
+ ],
+};
+
+```
+
+### 🧼 Removed: `shared.module.ts`
+
+This file has been removed to reduce unnecessary shared imports. Components now explicitly import what they need—leading to better encapsulation and less coupling.
+
+---
+
+## Common Problems
+
+You may encounter these common problems that you would need to manage.
+
+### 1. Missing Imports
+
+In standalone structure, components must declare all their dependencies in `imports`. Forgetting this often causes template errors.
+
+### 2. Mixed Structures
+
+Combining modules and standalone in the same feature leads to confusion. Migrate features fully or keep them module-based.
+
+### 3. Routing Errors
+
+Incorrect migration from `forLazy()` to `createRoutes()` or `loadComponent` can break navigation. Double-check route configs.
+
+### 4. Service Injection
+
+Services provided in old modules may be missing. Add them in the component’s `providers` or `app.config.ts`.
+
+### 5. Shared Module Habit
+
+Reintroducing a shared module reduces the benefits of standalone. Import dependencies directly where needed.
+
+---
+
+## Conclusion
+
+Angular’s standalone component architecture is a significant improvement for scalability, simplicity, and performance. With latest version of ABP Studio, you can adopt this modern approach with ease—without losing support for existing module-based projects.
+
+**Ready to modernize your Angular development?**
+
+Update your ABP Studio today and start building with standalone power!
diff --git a/docs/en/Community-Articles/2025-08-25-App-Services-vs-Domain-Services/POST.md b/docs/en/Community-Articles/2025-08-25-App-Services-vs-Domain-Services/POST.md
new file mode 100644
index 0000000000..534dc1abe1
--- /dev/null
+++ b/docs/en/Community-Articles/2025-08-25-App-Services-vs-Domain-Services/POST.md
@@ -0,0 +1,213 @@
+# App Services vs Domain Services: Deep Dive into Two Core Service Types in ABP Framework
+
+In ABP's layered architecture, we frequently encounter two types of services that appear similar but serve distinctly different purposes: Application Services and Domain Services. Understanding the differences between them is crucial for building clear and maintainable enterprise applications.
+
+## Architectural Positioning
+
+In ABP's layered architecture:
+
+- **Application Services** reside in the application layer and are responsible for coordinating use case execution
+- **Domain Services** reside in the domain layer and are responsible for implementing core business logic
+
+This layered design follows Domain-Driven Design (DDD) principles, ensuring clear separation of business logic and system maintainability.
+
+## Application Services: Use Case Orchestrators
+
+### Core Responsibilities
+
+Application Services are stateless services primarily used to implement application use cases. They act as a bridge between the presentation layer and domain layer, responsible for:
+
+- **Parameter Validation**: Input validation is automatically handled by ABP using data annotations
+- **Authorization**: Checking user permissions and access control using `[Authorize]` attribute or manual authorization checks via `IAuthorizationService`
+- **Transaction Management**: Methods automatically run as Unit of Work (transactional by default)
+- **Use Case Orchestration**: Organizing and coordinating multiple domain objects to complete specific business use cases
+- **Data Transformation**: Handling conversion between DTOs and domain objects using ObjectMapper
+
+### Design Principles
+
+1. **DTO Boundaries**: Application service methods should only accept and return DTOs, never directly expose domain entities
+2. **Use Case Oriented**: Each method should correspond to a clear user use case
+3. **Thin Layer Design**: Avoid implementing complex business logic in application services
+
+### Typical Execution Flow
+
+A standard application service method typically follows this pattern:
+
+```csharp
+[Authorize(BookPermissions.Create)] // Declarative authorization
+public virtual async Task CreateBookAsync(CreateBookDto input) // input is automatically validated
+{
+ // Get related data
+ var author = await _authorRepository.GetAsync(input.AuthorId);
+
+ // Call domain service to execute business logic (if needed)
+ // You can also use the entity constructor directly if no complex business logic is required
+ var book = await _bookManager.CreateAsync(input.Title, author, input.Price);
+
+ // Persist changes
+ await _bookRepository.InsertAsync(book);
+
+ // Return DTO
+ return ObjectMapper.Map(book);
+}
+```
+
+### Integration Services: Special kind of Application Service
+
+It's worth mentioning that ABP also provides a special type of application service—Integration Services. They are application services marked with the `[IntegrationService]` attribute, designed for inter-module or inter-microservice communication.
+
+We have a community article dedicated to integration services: [Integration Services Explained — What they are, when to use them, and how they behave](https://abp.io/community/articles/integration-services-explained-what-they-are-when-to-use-lienmsy8)
+
+## Domain Services: Guardians of Business Logic
+
+### Core Responsibilities
+
+Domain Services implement core business logic and are particularly needed when:
+
+- **Core domain logic depends on services**: You need to implement logic that requires repositories or other external services
+- **Logic spans multiple aggregates**: The business logic is related to more than one aggregate/entity and doesn't properly fit in any single aggregate
+- **Complex business rules**: Complex domain rules that don't naturally belong in a single entity
+
+### Design Principles
+
+1. **Domain Object Interaction**: Method parameters and return values should be domain objects (entities, value objects), never DTOs
+2. **Business Logic Focus**: Focus on implementing pure business rules
+3. **Stateless Design**: Maintain the stateless nature of services
+4. **State-Changing Operations Only**: Domain services should only define methods that mutate data, not query methods
+5. **No Authorization Logic**: Domain services should not perform authorization checks or depend on current user context
+6. **Specific Method Names**: Use descriptive, business-meaningful method names (e.g., `AssignToAsync`) instead of generic names (e.g., `UpdateAsync`)
+
+### Implementation Example
+
+```csharp
+public class IssueManager : DomainService
+{
+ private readonly IRepository _issueRepository;
+
+ public virtual async Task AssignToAsync(Issue issue, Guid userId)
+ {
+ // Business rule: Check user's unfinished task count
+ var openIssueCount = await _issueRepository.GetCountAsync(i => i.AssignedUserId == userId && !i.IsClosed);
+
+ if (openIssueCount >= 3)
+ {
+ throw new BusinessException("IssueTracking:ConcurrentOpenIssueLimit");
+ }
+
+ // Execute assignment logic
+ issue.AssignedUserId = userId;
+ issue.AssignedDate = Clock.Now;
+ }
+}
+```
+
+## Key Differences Comparison
+
+| Dimension | Application Services | Domain Services |
+|-----------|---------------------|-----------------|
+| **Layer Position** | Application Layer | Domain Layer |
+| **Primary Responsibility** | Use Case Orchestration | Business Logic Implementation |
+| **Data Interaction** | DTOs | Domain Objects |
+| **Callers** | Presentation Layer/Client Applications | Application Services/Other Domain Services |
+| **Authorization** | Responsible for permission checks | No authorization logic |
+| **Transaction Management** | Manages transaction boundaries (Unit of Work) | Participates in transactions but doesn't manage |
+| **Current User Context** | Can access current user information | Should not depend on current user context |
+| **Return Types** | Returns DTOs | Returns domain objects only |
+| **Query Operations** | Can perform query operations | Should not define GET/query methods |
+| **Naming Convention** | `*AppService` | `*Manager` or `*Service` |
+
+## Collaboration Patterns in Practice
+
+In real-world development, these two types of services typically work together:
+
+```csharp
+// Application Service
+public class BookAppService : ApplicationService
+{
+ private readonly BookManager _bookManager;
+ private readonly IRepository _bookRepository;
+
+ [Authorize(BookPermissions.Update)]
+ public virtual async Task UpdatePriceAsync(Guid id, decimal newPrice)
+ {
+ var book = await _bookRepository.GetAsync(id);
+
+ await _bookManager.ChangePriceAsync(book, newPrice);
+
+ await _bookRepository.UpdateAsync(book);
+
+ return ObjectMapper.Map(book);
+ }
+}
+
+// Domain Service
+public class BookManager : DomainService
+{
+ public virtual async Task ChangePriceAsync(Book book, decimal newPrice)
+ {
+ // Domain service focuses on business rules
+ if (newPrice <= 0)
+ {
+ throw new BusinessException("Book:InvalidPrice");
+ }
+
+ if (book.IsDiscounted && newPrice > book.OriginalPrice)
+ {
+ throw new BusinessException("Book:DiscountedPriceCannotExceedOriginal");
+ }
+
+ if (book.Price == newPrice)
+ {
+ return;
+ }
+
+ // Additional business logic: Check if price change requires approval
+ if (await RequiresApprovalAsync(book, newPrice))
+ {
+ throw new BusinessException("Book:PriceChangeRequiresApproval");
+ }
+
+ book.ChangePrice(newPrice);
+ }
+
+ private Task RequiresApprovalAsync(Book book, decimal newPrice)
+ {
+ // Example business rule: Large price increases require approval
+ var increasePercentage = ((newPrice - book.Price) / book.Price) * 100;
+ return Task.FromResult(increasePercentage > 50); // 50% increase threshold
+ }
+}
+```
+
+## Best Practice Recommendations
+
+### Application Services
+- Create a corresponding application service for each aggregate root
+- Use clear naming conventions (e.g., `IBookAppService`)
+- Implement standard CRUD operation methods (`GetAsync`, `CreateAsync`, `UpdateAsync`, `DeleteAsync`)
+- Avoid inter-application service calls within the same module/application
+- Always return DTOs, never expose domain entities directly
+- Use the `[Authorize]` attribute for declarative authorization or manual checks via `IAuthorizationService`
+- Methods automatically run as Unit of Work (transactional)
+- Input validation is handled automatically by ABP
+
+### Domain Services
+- Use the `Manager` suffix for naming (e.g., `BookManager`)
+- Only define state-changing methods, avoid query methods (use repositories directly in Application Services for queries)
+- Throw `BusinessException` with clear, unique error codes for domain validation failures
+- Keep methods pure, avoid involving user context or authorization logic
+- Accept and return domain objects only, never DTOs
+- Use descriptive, business-meaningful method names (e.g., `AssignToAsync`, `ChangePriceAsync`)
+- Do not implement interfaces unless there's a specific need for multiple implementations
+
+## Summary
+
+Application Services and Domain Services each have their distinct roles in the ABP framework: Application Services serve as use case orchestrators, handling authorization, validation, transaction management, and DTO transformations; Domain Services focus purely on business logic implementation without any infrastructure concerns. Integration Services are a special type of Application Service designed for inter-service communication.
+
+Correctly understanding and applying these service patterns is key to building high-quality ABP applications. Through clear separation of responsibilities, we can not only build more maintainable code but also flexibly switch between monolithic and microservice architectures—this is precisely the elegance of ABP framework design.
+
+## References
+
+- [Application Services](https://abp.io/docs/latest/framework/architecture/domain-driven-design/application-services)
+- [Integration Services](https://abp.io/docs/latest/framework/api-development/integration-services)
+- [Domain Services](https://abp.io/docs/latest/framework/architecture/domain-driven-design/domain-services)
diff --git a/docs/en/Community-Articles/2025-08-25-App-Services-vs-Domain-Services/cover.png b/docs/en/Community-Articles/2025-08-25-App-Services-vs-Domain-Services/cover.png
new file mode 100644
index 0000000000..a59643d12a
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-25-App-Services-vs-Domain-Services/cover.png differ
diff --git a/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/AutoMapper-Alternatives.md b/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/AutoMapper-Alternatives.md
new file mode 100644
index 0000000000..e9c4dec4ee
--- /dev/null
+++ b/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/AutoMapper-Alternatives.md
@@ -0,0 +1,338 @@
+# Best Free Alternatives to AutoMapper in .NET — Why We Moved to Mapperly
+
+---
+
+## Introduction
+
+[AutoMapper](https://automapper.io/) has been one of the most popular mapping library for .NET apps. It has been free and [open-source](https://github.com/LuckyPennySoftware/AutoMapper) since 2009. On 16 April 2025, Jimmy Bogard (the owner of the project) decided to make it commercial for his own reasons. You can read [this announcement](https://www.jimmybogard.com/automapper-and-mediatr-licensing-update/) about what happened to AutoMapper.
+
+
+
+### Why AutoMapper’s licensing change matters
+
+In ABP Framework we have been also using AutoMapper for object mappings. After its commercial transition, we also needed to replace it. Because ABP Framework is open-source and under [LGPL-3.0 license](https://github.com/abpframework/abp#LGPL-3.0-1-ov-file).
+
+**TL;DR**
+
+> That's why, **we decided to replace AutoMapper with Mapperly**.
+
+In this article, we'll discuss the alternatives of AutoMapper so that you can cut down on costs and maximize performance while retaining control over your codebase. Also I'll explain why we chose Mapperly.
+
+Also AutoMapper uses heavily reflection. And reflection comes with a performance cost if used indiscriminately, and compile-time safety is limited. Let's see how we can overcome these...
+
+
+
+## Cost-Free Alternatives to AutoMapper
+
+Check out the comparison table for key features vs. AutoMapper.
+
+| | **AutoMapper (Paid)** | **Mapster (Free)** | **Mapperly (Free)** | **AgileMapper (Free)** | **Manual Mapping** |
+| ------------------- | ----------------------------------------------- | ----------------------------------------- | -------------------------------------------- | ------------------------------------------- | ------------------------------------------------ |
+| **License & Cost** | Paid/commercial | Free, MIT License | Free, MIT License | Free, Apache 2.0 | Free (no library) |
+| **Performance** | Slower due to reflection & conventions | Very fast (runtime & compile-time modes) | Very fast (compile-time code generation) | Good, faster than AutoMapper | Fastest (direct assignment) |
+| **Ease of Setup** | Easy, but configuration-heavy | Easy, minimal config | Easy, but different approach from AutoMapper | Simple, flexible configuration | Manual coding required |
+| **Features** | Rich features, conventions, nested mappings | Strong typed mappings, projection support | Strong typed, compile-time safe mappings | Dynamic & conditional mapping | Whatever you code |
+| **Maintainability** | Hidden mappings can be hard to debug | Explicit & predictable | Very explicit, compiler-verified mappings | Readable, good balance | Very explicit, most maintainable |
+| **Best For** | Large teams used to AutoMapper & willing to pay | Teams wanting performance + free tool | Teams prioritizing type-safety & performance | Developers needing flexibility & simplicity | Small/medium projects, performance-critical apps |
+
+There are other libraries such as [**ExpressMapper**](https://github.com/fluentsprings/ExpressMapper) **(308 GitHub stars)**, [**ValueInjecter**](https://github.com/omuleanu/ValueInjecter) **(258 GitHub stars)**, [**AgileMapper**](https://github.com/agileobjects/AgileMapper) **(463 GitHub stars)**. These are not very popular but also free and offer a different balance of simplicity and features.
+
+
+
+## Why We Chose Mapperly
+
+We filtered down all the alternatives into 2: **Mapster** and **Mapperly**.
+
+The crucial factor was maintainability! As you see from the screenshots below, Mapster is already stopped development. Mapster’s development appears stalled, and its future maintenance is uncertain. On the other hand, Mapperly regularly gets commits. The community support is valuable.
+
+We looked up different alternatives of AutoMapper also, here's the initial issue of AutoMapper replacement [github.com/abpframework/abp/issues/23243](https://github.com/abpframework/abp/issues/23243).
+
+The ABP team started Mapperly integration with this initial commit [github.com/abpframework/abp/commit/178d3f56d42b4e5acb7e349470f4a644d4c5214e](https://github.com/abpframework/abp/commit/178d3f56d42b4e5acb7e349470f4a644d4c5214e). And this is our Mapperly integration package : [github.com/abpframework/abp/tree/dev/framework/src/Volo.Abp.Mapperly.](https://github.com/abpframework/abp/tree/dev/framework/src/Volo.Abp.Mapperly.)
+
+
+
+Here are some considerations for developers who are used to ABP and AutoMapper.
+
+### [Mapster](https://github.com/MapsterMapper/Mapster):
+
+* ✔ It is similar to AutoMapper, configuring mappings through code.
+* ✔ Support for dependency injection and complex runtime configuration.
+* ❌ It is looking additional Mapster maintainers ([Call for additional Mapster maintainers MapsterMapper/Mapster#752](https://github.com/MapsterMapper/Mapster/discussions/752))
+
+### [Mapperly](https://github.com/riok/Mapperly):
+
+- ✔ It generates mapping code(` source generator`) during the build process.
+- ✔ It is actively being developed and maintained.
+- ❌ It is a static `map` method, which is not friendly to dependency injection.
+- ❌ The configuration method is completely different from AutoMapper, and there is a learning curve.
+
+
+
+**Mapperly** → generates mapping code at **compile time** using source generators.
+
+**Mapster** → has two modes:
+
+- By default, it uses **runtime code generation** (via expression trees and compilation).
+
+- But with **Mapster.Tool** (source generator), it can also generate mappings at **compile time**.
+
+
+
+This is important because it guarantees the mappings are working well. Also they provide type safety and improved performance. Another advantages of these libraries, they eliminate runtime surprises and offer better IDE support.
+
+---
+
+## When Mapperly Will Come To ABP
+
+Mapperly integration will be delivered with ABP v10. If you have already defined AutoMapper configurations, you can still keep and use them. But the framework will use Mapperly. So there'll be 2 mapping integrations in your app. You can also remove AutoMapper from your final application and use one mapping library: Mapperly. It's up to you! Check [AutoMapper pricing table](https://automapper.io/#pricing).
+
+
+
+## Migrating from AutoMapper to Mapperly
+
+In ABP v10, we will be migrating from AutoMapper to Mapperly. The document about the migration is not delivered by the time I wrote this article, but you can reach the document in our dev docs branch
+
+* [github.com/abpframework/abp/blob/dev/docs/en/release-info/migration-guides/AutoMapper-To-Mapperly.md](https://github.com/abpframework/abp/blob/dev/docs/en/release-info/migration-guides/AutoMapper-To-Mapperly.md).
+
+Also for ABP, you can check out how you will define DTO mappings based on Mapperly at this document
+
+* [github.com/abpframework/abp/blob/dev/docs/en/framework/infrastructure/object-to-object-mapping.md](https://github.com/abpframework/abp/blob/dev/docs/en/framework/infrastructure/object-to-object-mapping.md)
+
+
+
+## Mapping Code Examples for AutoMapper, Mapster, AgileMapper
+
+### AutoMapper vs Mapster vs Mapperly Performance
+
+Here are concise, drop-in **side-by-side C# snippets** that map the same model with AutoMapper, Mapster, AgileMapper, and manual mapping.
+
+ Models used in all examples
+
+We'll use these models to show the mapping examples for AutoMapper, Mapster, AgileMapper.
+
+```csharp
+public class Order
+{
+ public int Id { get; set; }
+ public Customer Customer { get; set; } = default!;
+ public List Lines { get; set; } = new();
+ public DateTime CreatedAt { get; set; }
+}
+
+public class Customer
+{
+ public int Id { get; set; }
+ public string Name { get; set; } = "";
+ public string? Email { get; set; }
+}
+
+public class OrderLine
+{
+ public int ProductId { get; set; }
+ public int Quantity { get; set; }
+ public decimal UnitPrice { get; set; }
+}
+
+public class OrderDto
+{
+ public int Id { get; set; }
+ public string CustomerName { get; set; } = "";
+ public int ItemCount { get; set; }
+ public decimal Total { get; set; }
+ public string CreatedAtIso { get; set; } = "";
+}
+```
+
+
+
+#### AutoMapper Example (Paid)
+
+```csharp
+public sealed class OrderProfile : Profile
+{
+ public OrderProfile()
+ {
+ CreateMap()
+ .ForMember(d => d.CustomerName, m => m.MapFrom(s => s.Customer.Name))
+ .ForMember(d => d.ItemCount, m => m.MapFrom(s => s.Lines.Sum(l => l.Quantity)))
+ .ForMember(d => d.Total, m => m.MapFrom(s => s.Lines.Sum(l => l.Quantity * l.UnitPrice)))
+ .ForMember(d => d.CreatedAtIso,m => m.MapFrom(s => s.CreatedAt.ToString("O")));
+ }
+}
+
+// registration
+services.AddAutoMapper(typeof(OrderProfile));
+
+// mapping
+var dto = mapper.Map(order);
+
+// EF Core projection (common pattern)
+var list = dbContext.Orders
+ .ProjectTo(mapper.ConfigurationProvider)
+ .ToList();
+```
+
+**NuGet Packages:**
+
+- https://www.nuget.org/packages/AutoMapper
+- https://www.nuget.org/packages/AutoMapper.Extensions.Microsoft.DependencyInjection
+
+---
+
+#### Mapperly (Free, Apache-2.0)
+
+This is compile-time generated mapping.
+
+```csharp
+[Mapper] // generates the implementation at build time
+public partial class OrderMapper
+{
+ // Simple property mapping: Customer.Name -> CustomerName
+ [MapProperty(nameof(Order.Customer) + "." + nameof(Customer.Name), nameof(OrderDto.CustomerName))]
+ public partial OrderDto ToDto(Order source);
+
+ // Update an existing target (like MapToExisting)
+ [MapProperty(nameof(Order.Customer) + "." + nameof(Customer.Name), nameof(OrderDto.CustomerName))]
+ public partial void UpdateDto(Order source, OrderDto target);
+
+ public OrderDto Map(Order s)
+ {
+ var d = ToDto(s);
+ AfterMap(s, d);
+ return d;
+ }
+
+ public void Map(Order source, OrderDto d)
+ {
+ UpdateDto(source, d);
+ AfterMap(source, d);
+ }
+
+ private void AfterMap(Order source, OrderDto d)
+ {
+ d.ItemCount = source.Lines.Sum(l => l.Quantity);
+ d.Total = source.Lines.Sum(l => l.Quantity * l.UnitPrice);
+ d.CreatedAtIso = source.CreatedAt.ToString("O");
+ }
+}
+
+
+//USAGE
+var mapper = new OrderMapper();
+var order = new Order
+{
+ Id = 1,
+ Customer = new Customer { Id = 1, Name = "John Doe", Email = "johndoe@abp.io" },
+ Lines =
+ [
+ new OrderLine {ProductId = 1, Quantity = 2, UnitPrice = 10.0m},
+ new OrderLine {ProductId = 2, Quantity = 1, UnitPrice = 20.0m}
+ ]
+};
+
+// Map to a new object
+var dto = mapper.Map(order);
+
+// Map to an existing object
+var target = new OrderDto();
+mapper.Map(order, target);
+```
+
+**NuGet Packages:**
+
+* https://www.nuget.org/packages/Riok.Mapperly/
+
+---
+
+#### Mapster Example (Free, MIT)
+
+```csharp
+TypeAdapterConfig.NewConfig()
+ .Map(d => d.CustomerName, s => s.Customer.Name)
+ .Map(d => d.ItemCount, s => s.Lines.Sum(l => l.Quantity))
+ .Map(d => d.Total, s => s.Lines.Sum(l => l.Quantity * l.UnitPrice))
+ .Map(d => d.CreatedAtIso, s => s.CreatedAt.ToString("O"));
+
+// one-off
+var dto = order.Adapt();
+
+// DI-friendly registration
+services.AddSingleton(TypeAdapterConfig.GlobalSettings);
+services.AddScoped();
+
+// EF Core projection (strong suit)
+var mappedList = dbContext.Orders
+ .ProjectToType() // Mapster projection
+ .ToList();
+```
+
+**NuGet Packages:**
+
+- https://www.nuget.org/packages/Mapster
+- https://www.nuget.org/packages/Mapster.DependencyInjection
+- https://www.nuget.org/packages/Mapster.SourceGenerator (for performance improvement)
+
+---
+
+#### AgileMapper Example (Free, Apache-2.0)
+
+```csharp
+var mapper = Mapper.CreateNew(cfg =>
+{
+ cfg.WhenMapping
+ .From()
+ .To()
+ .Map(ctx => ctx.Source.Customer.Name).To(dto => dto.CustomerName)
+ .Map(ctx => ctx.Source.Lines.Sum(l => l.Quantity)).To(dto => dto.ItemCount)
+ .Map(ctx => ctx.Source.Lines.Sum(l => l.Quantity * l.UnitPrice)).To(dto => dto.Total)
+ .Map(ctx => ctx.Source.CreatedAt.ToString("O")).To(dto => dto.CreatedAtIso);
+});
+
+var mappedDto = mapper.Map(order).ToANew();
+```
+
+**NuGet Packages:**
+
+* https://www.nuget.org/packages/AgileObjects.AgileMapper
+
+
+---
+
+#### Manual (Pure) Mapping (no library)
+
+Straightforward, fastest, and most explicit. Good for simple applications which doesn't need long term maintenance. Hand-written mapping is faster, safer, and more maintainable. And for tiny mappings, you can still use manual mapping.
+
+* Examples of when manual mapping is better than libraries.
+
+```csharp
+public static class OrderMapping
+{
+ public static OrderDto ToDto(this Order s) => new()
+ {
+ Id = s.Id,
+ CustomerName = s.Customer.Name,
+ ItemCount = s.Lines.Sum(l => l.Quantity),
+ Total = s.Lines.Sum(l => l.Quantity * l.UnitPrice),
+ CreatedAtIso = s.CreatedAt.ToString("O")
+ };
+}
+
+// usage
+var dto = order.ToDto();
+
+// EF Core projection (best for perf + SQL translation)
+var mappedList = dbContext.Orders.Select(s => new OrderDto
+ {
+ Id = s.Id,
+ CustomerName = s.Customer.Name,
+ ItemCount = s.Lines.Sum(l => l.Quantity),
+ Total = s.Lines.Sum(l => l.Quantity * l.UnitPrice),
+ CreatedAtIso = s.CreatedAt.ToString("O")
+ }).ToList();
+```
+
+
+
+### Conclusion
+
+If you rely on AutoMapper today, it’s time to evaluate alternatives. For ABP Framework, we chose **Mapperly** due to active development, strong community, and compile-time performance. But your team may prefer **Mapster** for flexibility or even manual mapping for small apps. Your requirements might be different, your project is not a framework so you decide the best one for you.
diff --git a/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/cover.png b/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/cover.png
new file mode 100644
index 0000000000..d1c7e26166
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/cover.png differ
diff --git a/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/mapster-mapperly-community-powers.png b/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/mapster-mapperly-community-powers.png
new file mode 100644
index 0000000000..c2e3adbbfc
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-25-AutoMapper-Alternatives/mapster-mapperly-community-powers.png differ
diff --git a/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/POST.md b/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/POST.md
new file mode 100644
index 0000000000..2d6c98102f
--- /dev/null
+++ b/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/POST.md
@@ -0,0 +1,174 @@
+# Building a Permission-Based Authorization System for ASP.NET Core
+
+In this article, we'll explore different authorization approaches in ASP.NET Core and examine how ABP's permission-based authorization system works.
+
+First, we'll look at some of the core authorization types that come with ASP.NET Core, such as role-based, claims-based, policy-based, and resource-based authorization. We'll briefly review the pros and cons of each approach.
+
+Then, we'll dive into [ABP's Permission-Based Authorization System](https://abp.io/docs/latest/framework/fundamentals/authorization#permission-system). This is a more advanced approach that gives you fine-grained control over what users can do in your application. We'll also explore ABP's Permission Management Module, which makes managing permissions through the UI easily.
+
+## Understanding ASP.NET Core Authorization Types
+
+Before diving into permission-based authorization, let's examine some of the core authorization types available in ASP.NET Core:
+
+- **[Role-Based Authorization](https://learn.microsoft.com/en-us/aspnet/core/security/authorization/roles?view=aspnetcore-9.0)** checks if the current user belongs to specific roles (like **"Admin"** or **"User"**) and grants access based on these roles. (For example, only users in the **"Manager"** role can access the employee salary management page.)
+
+- **[Claims-Based Authorization](https://learn.microsoft.com/en-us/aspnet/core/security/authorization/claims?view=aspnetcore-9.0)** uses key-value pairs (claims) that describe user attributes, such as age, department, or security clearance. (For example, only users with a **"Department=Finance"** claim can view financial reports.) This provides more granular control but requires careful claim management (such as grouping claims under policies).
+
+- **[Policy-Based Authorization](https://learn.microsoft.com/en-us/aspnet/core/security/authorization/policies?view=aspnetcore-9.0)** combines multiple requirements (roles, claims, custom logic) into reusable policies. It offers flexibility and centralized management, and **this is exactly why ABP's permission system is built on top of it!** (We'll discuss this in more detail later.)
+
+- **[Resource-Based Authorization](https://learn.microsoft.com/en-us/aspnet/core/security/authorization/resourcebased?view=aspnetcore-9.0)** determines access by examining both the user and the specific item they want to access. (For example, a user can edit only their own blog posts, not others' posts.) Unlike policy-based authorization which applies the same rules everywhere, resource-based authorization makes decisions based on the actual data being accessed, requiring more complex implementation.
+
+Here's a quick comparison of these approaches:
+
+| Authorization Type | Pros | Cons |
+|-------------------|------|------|
+| **Role-Based** | Simple implementation, easy to understand | Becomes inflexible with complex role hierarchies |
+| **Claims-Based** | Granular control, flexible user attributes | Complex claim management, potential for claim explosion |
+| **Policy-Based** | Centralized logic, combines multiple requirements | Can become complex with numerous policies |
+| **Resource-Based** | Fine-grained per-resource control | Implementation complexity, resource-specific code |
+
+## What is Permission-Based Authorization?
+
+Permission-based authorization takes a different approach from other authorization types by defining specific permissions (like **"CreateUser"**, **"DeleteOrder"**, **"ViewReports"**) that represent granular actions within your application. These permissions can be assigned to users directly or through roles, providing both flexibility and clear action-based access control.
+
+ABP Framework's permission system is built on top of this approach and extends ASP.NET Core's policy-based authorization system, working seamlessly with it.
+
+## ABP Framework's Permission System
+
+ABP extends [ASP.NET Core Authorization](https://learn.microsoft.com/en-us/aspnet/core/security/authorization/introduction?view=aspnetcore-9.0) by adding **permissions** as automatic [policies](https://learn.microsoft.com/en-us/aspnet/core/security/authorization/policies?view=aspnetcore-9.0) and allows the authorization system to be used in application services as well.
+
+This system provides a clean abstraction while maintaining full compatibility with ASP.NET Core's authorization infrastructure.
+
+ABP also provides a [Permission Management Module](https://abp.io/docs/latest/modules/permission-management) that offers a complete UI and API for managing permissions. This allows you to easily manage permissions in the UI, assign permissions to roles or users, and much more. (We'll see how to use it in the following sections.)
+
+### Defining Permissions in ABP
+
+In ABP, permissions are defined in classes (typically under the `*.Application.Contracts` project) that inherit from the `PermissionDefinitionProvider` class. Here's how you can define permissions for a book management system:
+
+```csharp
+public class BookStorePermissionDefinitionProvider : PermissionDefinitionProvider
+{
+ public override void Define(IPermissionDefinitionContext context)
+ {
+ var bookStoreGroup = context.AddGroup("BookStore");
+
+ var booksPermission = bookStoreGroup.AddPermission("BookStore.Books", L("Permission:Books"));
+ booksPermission.AddChild("BookStore.Books.Create", L("Permission:Books.Create"));
+ booksPermission.AddChild("BookStore.Books.Edit", L("Permission:Books.Edit"));
+ booksPermission.AddChild("BookStore.Books.Delete", L("Permission:Books.Delete"));
+ }
+
+ private static LocalizableString L(string name)
+ {
+ return LocalizableString.Create(name);
+ }
+}
+```
+
+ABP automatically discovers this class and registers the permissions/policies in the system. You can then assign these permissions/policies to users/roles. There are two ways to do this:
+
+* Using the [Permission Management Module](https://abp.io/docs/latest/modules/permission-management)
+* Using the `IPermissionManager` service (via code)
+
+#### Setting Permissions to Roles and Users via Permission Management Module
+
+When you define a permission, it also becomes usable in the ASP.NET Core authorization system as a **policy name**. If you are using the [Permission Management Module](https://abp.io/docs/latest/modules/permission-management), you can manage the permissions through the UI:
+
+
+
+In the permission management UI, you can grant permissions to roles and users through the **Role Management** and **User Management** pages within the "permissions" modals. You can then easily check these permissions in your code. In the screenshot above, you can see the permission modal for the user's page, clearly showing the permissions granted to the user by their role. (**(R)** in the UI indicates that the permission is granted by one of the current user's roles.)
+
+#### Setting Permissions to Roles and Users via Code
+
+You can also set permissions for roles and users programmatically. You just need to inject the `IPermissionManager` service and use its `SetForRoleAsync` and `SetForUserAsync` methods (or similar methods):
+
+```csharp
+public class MyService : ITransientDependency
+{
+ private readonly IPermissionManager _permissionManager;
+
+ public MyService(IPermissionManager permissionManager)
+ {
+ _permissionManager = permissionManager;
+ }
+
+ public async Task GrantPermissionForUserAsync(Guid userId, string permissionName)
+ {
+ await _permissionManager.SetForUserAsync(userId, permissionName, true);
+ }
+
+ public async Task ProhibitPermissionForUserAsync(Guid userId, string permissionName)
+ {
+ await _permissionManager.SetForUserAsync(userId, permissionName, false);
+ }
+}
+```
+
+### Checking Permissions in AppServices and Controllers
+
+ABP provides multiple ways to check permissions. The most common approach is using the `[Authorize]` attribute and passing the permission/policy name.
+
+Here is an example of how to check permissions in an application service:
+
+```csharp
+[Authorize("BookStore.Books")]
+public class BookAppService : ApplicationService, IBookAppService
+{
+ [Authorize("BookStore.Books.Create")]
+ public async Task CreateAsync(CreateBookDto input)
+ {
+ //logic here
+ }
+}
+```
+
+> Notice that you can use the `[Authorize]` attribute at both class and method levels. In the example above, the `CreateAsync` method is marked with the `[Authorize]` attribute, so it will check the user's permission before executing the method. Since the application service class also has a permission requirement, both permissions must be granted to the user to execute the method!
+
+And here is an example of how to check permissions in a controller:
+
+```csharp
+[Authorize("BookStore.Books")]
+public class CreateBookController : AbpController
+{
+ //omitted for brevity...
+}
+```
+
+### Programmatic Permission Checking
+
+To conditionally control authorization in your code, you can use the `IAuthorizationService` service:
+
+```csharp
+public class BookAppService : ApplicationService, IBookAppService
+{
+ public async Task CreateAsync(CreateBookDto input)
+ {
+ // Checks the permission and throws an exception if the user does not have the permission
+ await AuthorizationService.CheckAsync(BookStorePermissions.Books.Create);
+
+ // Your logic here
+ }
+
+ public async Task CanUserCreateBooksAsync()
+ {
+ // Checks if the permission is granted for the current user
+ return await AuthorizationService.IsGrantedAsync(BookStorePermissions.Books.Create);
+ }
+}
+```
+
+You can use the `IAuthorizationService`'s helpful methods for authorization checking, as shown in the example above:
+
+- `IsGrantedAsync` checks if the current user has the given permission.
+- `CheckAsync` throws an exception if the current user does not have the given permission.
+- `AuthorizeAsync` checks if the current user has the given permission and returns an `AuthorizationResult`, which has a `Succeeded` property that you can use to verify if the user has the permission.
+
+Also notice that we did not inject the `IAuthorizationService` in the constructor, because we are using the `ApplicationService` base class, which already provides property injection for it. This means we can directly use it in our application services, just like other helpful base services (such as `ICurrentUser` and `ICurrentTenant`).
+
+## Conclusion
+
+Permission-based authorization in ABP Framework provides a powerful and flexible approach to securing your applications. By building on ASP.NET Core's policy-based authorization, ABP offers a clean abstraction that simplifies permission management while maintaining the full power of the underlying system.
+
+The ability to check permissions in both application services and controllers makes ABP Framework's authorization system very flexible and powerful, yet easy to use.
+
+Additionally, the Permission Management Module makes it very easy to manage permissions and roles through the UI. You can learn more about how it works in the [documentation](https://abp.io/docs/latest/modules/permission-management).
diff --git a/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/cover-image.png b/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/cover-image.png
new file mode 100644
index 0000000000..f0a0796034
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/cover-image.png differ
diff --git a/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/permission-management-module.png b/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/permission-management-module.png
new file mode 100644
index 0000000000..e22de787af
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-27-Building-a-permission-based-authorization-system-for-net-core/permission-management-module.png differ
diff --git a/docs/en/Community-Articles/2025-08-27-backcompat-rest-apis-ms-dotnet/article.md b/docs/en/Community-Articles/2025-08-27-backcompat-rest-apis-ms-dotnet/article.md
new file mode 100644
index 0000000000..f88bb0e41c
--- /dev/null
+++ b/docs/en/Community-Articles/2025-08-27-backcompat-rest-apis-ms-dotnet/article.md
@@ -0,0 +1,169 @@
+# Best Practices for Designing Backward‑Compatible REST APIs in a Microservice Solution for .NET Developers
+
+## Introduction
+With microservice architecture, each service develops and ships independently at its own pace, and clients infrequently update in lockstep. **Backward compatibility** means that when you release new versions, current consumers continue to function without changing code. This article provides a practical, 6–7 minute tutorial specific to **.NET developers**.
+
+---
+## What Counts as “Breaking”? (and what doesn’t)
+A change is **breaking** if a client that previously conformed can **fail at compile time or runtime**, or exhibit **different business‑critical behavior**, **without** changing that client in any way. In other words: if an old client needs to be altered in order to continue functioning as it did, your change is breaking.
+
+### Examples of breaking changes
+- **Deleting or renaming an endpoint** or modifying its URL/route.
+- **Making an existing field required** (e.g., requiring `address`).
+- **Data type or format changes** (e.g., `price: string` → `price: number`, or date format changes).
+- **Altering default behavior or ordering** that clients implicitly depend on (hidden contracts).
+- **Changing the error model** or HTTP status codes in a manner that breaks pre-existing error handling.
+- **Renaming fields** or **making optional fields required** in requests or responses.
+- **Reinterpreting semantics** (e.g., `status="closed"` formerly included archived items, but no longer does).
+
+### Examples of non‑breaking changes
+- **Optional fields or query parameters can be added** (clients may disregard them).
+- **Adding new enum values** (if the clients default to a safe behavior for unrecognized values).
+- **Adding a new endpoint** while leaving the previous one unchanged.
+- **Performance enhancements** that leave input/output unchanged.
+- **Including metadata** (e.g., pagination links) without changing the current payload shape.
+
+> Golden rule: **Old clients should continue to work exactly as they did before—without any changes.**
+
+---
+## Versioning Strategy
+Versioning is your master control lever for managing change. Typical methods:
+
+1) **URI Segment** (simplest)
+```
+GET /api/v1/orders
+GET /api/v2/orders
+```
+Pros: Cache/gateway‑friendly; explicit in docs. Cons: URL noise.
+
+2) **Header‑Based**
+```
+GET /api/orders
+x-api-version: 2.0
+```
+Pros: Clean URLs; multiple reader support. Cons: Needs proxy/CDN rules.
+
+3) **Media Type**
+ Accept: application/json;v=2
+
+ Pros: Semantically accurate.
Cons: More complicated to test and implement.
**Recommendation:** For the majority of teams, favor **URI segments**, with an optional **`x-api-version`** header for flexibility.
+
+### Quick Setup in ASP.NET Core (Asp.Versioning)
+```csharp
+// Program.cs
+using Asp.Versioning;
+
+builder.Services.AddControllers();
+builder.Services.AddApiVersioning(o =>
+{
+ o.DefaultApiVersion = new ApiVersion(1, 0);
+ o.AssumeDefaultVersionWhenUnspecified = true;
+ o.ReportApiVersions = true; // response header: api-supported-versions
+ o.ApiVersionReader = ApiVersionReader.Combine(
+ new UrlSegmentApiVersionReader(),
+ new HeaderApiVersionReader("x-api-version")
+ );
+});
+
+builder.Services.AddVersionedApiExplorer(o =>
+{
+ o.GroupNameFormat = "'v'VVV"; // v1, v2
+ o.SubstituteApiVersionInUrl = true;
+});
+```
+```csharp
+// Controller
+using Asp.Versioning;
+
+[ApiController]
+[Route("api/v{version:apiVersion}/orders")]
+public class OrdersController : ControllerBase
+{
+ [HttpGet]
+ [ApiVersion("1.0", Deprecated = true)]
+ public IActionResult GetV1() => Ok(new { message = "v1" });
+
+ [HttpGet]
+ [MapToApiVersion("2.0")]
+ public IActionResult GetV2() => Ok(new { message = "v2", includes = new []{"items"} });
+}
+```
+
+---
+## Schema Evolution Playbook (JSON & DTO)
+Obey the following rules for compatibility‑safe evolution:
+
+- **Add‑only changes**: Favor adding **optional** fields; do not remove/rename fields.
+- **Maintain defaults**: When the new field is disregarded, the old functionality must not change.
+- **Enum extension**: Clients should handle unknown enum values gracefully (default behavior).
+- **Deprecation pipeline**: Mark fields/endpoints as deprecated **at least one version** prior to removal and publicize extensively. - **Stability by contract**: Record any unspoken contracts (ordering, casing, formats) that clients depend on.
+
+### Example: adding a non‑breaking field
+```csharp
+public record OrderDto(
+ Guid Id,
+ decimal Total,
+ string Currency,
+ string? SalesChannel // new, optional
+);
+```
+
+---
+## Compatibility‑Safe API Behaviors
+- **Error model**: Use a standard structure (e.g., RFC 7807 `ProblemDetails`). Avoid ad‑hoc error shapes on a per-endpoint basis.
+- **Versioning/Deprecation communication** through headers:
+- `api-supported-versions: 1.0, 2.0`
+- `Deprecation: true` (in deprecated endpoints)
+- `Sunset: Wed, 01 Oct 2025 00:00:00 GMT` (planned deprecation date)
+- **Idempotency**: Use an `Idempotency-Key` header for retry-safe POSTs.
+- **Optimistic concurrency**: Utilize `ETag`/`If-Match` to prevent lost updates.
+- **Pagination**: Prefer cursor tokens (`nextPageToken`) to protect clients from sorting/index changes.
+- **Time**: Employ ISO‑8601 in UTC; record time‑zone semantics and rounding conventions.
+
+---
+## Rollout & Deprecation Policy
+A good deprecation policy is **announce → coexist → remove**:
+
+1) **Announce**: Release changelog, docs, and comms (mail/Slack) with v2 information and the sunset date.
+2) **Coexist**: Operate v1 and v2 side by side. Employ gateway percentage routing for progressive cutover.
+3) **Observability**: Monitor errors/latency/usage **by version**. When v1 traffic falls below ~5%, plan for removal. 4) **Remove**: Post sunset date, return **410 (Gone)** with a link to migration documentation.
+
+**Canary & Blue‑Green**: Initialize v2 with a small traffic portion and compare error/latency budgets prior to scaling up.
+
+---
+## Contract & Compatibility Testing
+- **Consumer‑Driven Contracts**: Write expectations using Pact.NET; verify at provider CI.
+- **Golden files / snapshots**: Freeze representative JSON payloads and automatically detect regressions.
+- **Version-specific smoke tests**: Maintain separate, minimal test suites for v1 and v2.
+- **SemVer discipline**: Minor = backward‑compatible; Major = breaking (avoid when possible).
+
+Minimal example (xUnit + snapshot style):
+```csharp
+[Fact]
+public async Task Orders_v1_contract_should_match_snapshot()
+{
+ var resp = await _client.GetStringAsync("/api/v1/orders");
+ Approvals.VerifyJson(resp); // snapshot comparison
+}
+```
+
+---
+## Tooling & Docs (for .NET)
+- **Asp.Versioning (NuGet)**: API versioning + ApiExplorer integration.
+- **Swashbuckle / NSwag**: Generate an OpenAPI definition **for every version** (`/swagger/v1/swagger.json`, `/swagger/v2/swagger.json`). Display both in Swagger UI.
+- **Polly**: Client‑side retries/fallbacks to handle transient failures and ensure resilience.
+- **Serilog + OpenTelemetry**: Collect metrics/logs/traces by version for observability and SLOs.
+
+Swagger UI configuration by group name:
+```csharp
+app.UseSwagger();
+app.UseSwaggerUI(c =>
+{
+c.SwaggerEndpoint("/swagger/v1/swagger.json", "API v1");
+c.SwaggerEndpoint("/swagger/v2/swagger.json", "API v2");
+});
+```
+---
+
+## Conclusion
+Backward compatibility is not a version number—it is **disciplined change management**. When you use add‑only schema evolution, a well‑defined versioning strategy, strict contract testing, and rolling rollout, you maintain microservice independence and safeguard consumer experience.
diff --git a/docs/en/Community-Articles/2025-08-27-backcompat-rest-apis-ms-dotnet/cover.png b/docs/en/Community-Articles/2025-08-27-backcompat-rest-apis-ms-dotnet/cover.png
new file mode 100644
index 0000000000..07f0782775
Binary files /dev/null and b/docs/en/Community-Articles/2025-08-27-backcompat-rest-apis-ms-dotnet/cover.png differ
diff --git a/docs/en/Community-Articles/2025-09-02-training-campaign/post.md b/docs/en/Community-Articles/2025-09-02-training-campaign/post.md
new file mode 100644
index 0000000000..20f2bcf4bd
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-02-training-campaign/post.md
@@ -0,0 +1,29 @@
+# IMPROVE YOUR ABP SKILLS WITH 33% OFF LIVE TRAININGS!
+
+We have exciting news to share\! As you know, we offer live training packages to help you improve your skills and knowledge of ABP. From September 8th to 19th, we are giving you 33% OFF our live trainings, so you can learn more about the product at a discounted price\!
+
+#### Why Join ABP.IO Training?
+
+ABP training programs are designed to help developers, architects, and teams master the ABP Framework efficiently. Whether you're new to the framework or looking to deepen your knowledge, our courses cover everything you need to build robust and scalable applications with ABP.
+
+#### What You’ll Gain:
+
+✔ Comprehensive live training from ABP Experts
+✔ Hands-on learning with real-world applications
+✔ Best practices for building modern web applications
+✔ Certification to showcase your expertise
+
+#### [Limited-Time 33% Discount – Don’t Miss Out\!](https://abp.io/trainings?utm_source=referral&utm_medium=website&utm_campaign=training_abpblogpost)
+
+For a short period, all training packages are available at a 33% discount. This is a great opportunity to upskill yourself or train your team at a significantly reduced cost.
+
+#### How to Get the Discount?
+
+Simply visit our training page, select your preferred package, add your note if needed and send your training request, that's all\! ABP Training Team will reply to your request via email soon.
+
+#### Take Advantage of This Offer Today
+
+Invest in your skills and advance your career with ABP.IO training. This offer won’t last long, so grab your spot now\!
+
+### 🔗[Pick your package and send your training request now!](https://abp.io/trainings?utm_source=referral&utm_medium=website&utm_campaign=training_abpblogpost)
+
diff --git a/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/1.png b/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/1.png
new file mode 100644
index 0000000000..9168907741
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/1.png differ
diff --git a/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/2.png b/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/2.png
new file mode 100644
index 0000000000..ff84b51766
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/2.png differ
diff --git a/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/POST.md b/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/POST.md
new file mode 100644
index 0000000000..076e623ad8
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/POST.md
@@ -0,0 +1,335 @@
+# Keep Track of Your Users in an ASP.NET Core Application
+
+Tracking what users do in your app matters for security, debugging, and business insights. Doing it by hand usually means lots of boilerplate: managing request context, logging operations, tracking entity changes, and more. It adds complexity and makes mistakes more likely.
+
+## Why Applications Need Audit Logs
+
+Audit logs are time-ordered records that show what happened in your app.
+
+A good audit log should capture details for every web request, including:
+
+### 1. Request and Response Details
+- Basic info like **URL, HTTP method, browser**, and **HTTP status code**
+- Network info like **client IP address** and **user agent**
+- **Request parameters** and **response content** when needed
+
+### 2. Operations Performed
+- **Controller actions** and **application service method calls** with parameters
+- **Execution time** and **duration** for performance tracking
+- **Call chains** and **dependencies** where helpful
+
+### 3. Entity Changes
+- **Entity changes** that happen during requests
+- **Property-level changes**, with old and new values
+- **Change types** (create, update, delete) and timestamps
+
+### 4. Exception Information
+- **Errors and exceptions** during request execution
+- **Exception stack traces** and **error context**
+- Clear records of failed operations
+
+### 5. Request Duration
+- Key metrics for **measuring performance**
+- **Finding bottlenecks** and optimization opportunities
+- Useful data for **monitoring system health**
+
+## The Challenge with Doing It by Hand
+
+In ASP.NET Core, developers often use middleware or MVC filters for tracking. Here’s what that looks like and the common problems you’ll hit.
+
+### Using Middleware
+
+Middleware are components in the ASP.NET Core pipeline that run during request processing.
+
+Manual tracking typically requires:
+- Writing custom middleware to intercept HTTP requests
+- Extracting user info (user ID, username, IP address, and so on)
+- Recording request start time and execution duration
+- Handling both success and failure cases
+- Saving audit data to logs or a database
+
+### Tracking Inside Business Methods
+
+In your business code, you also need to:
+- Log the start and end of important operations
+- Capture errors and related context
+- Link business operations to the request-level audit data
+- Make sure you track all critical actions
+
+### Problems with Manual Tracking
+
+Manual tracking has some big downsides:
+
+**Code duplication and maintenance pain**: Each controller ends up repeating similar tracking logic. Changing the rules means touching many places, and it’s easy to miss some.
+
+**Consistency and reliability issues**: Different people implement tracking differently. Exception paths are easy to forget. It’s hard to ensure complete coverage.
+
+**Performance and scalability concerns**: Homegrown tracking can slow the app if not designed well. Tuning and extending it takes effort.
+
+**Entity change tracking is especially hard**. It often requires:
+- Recording original values before updates
+- Comparing old and new values for each property
+- Handling complex types, collections, and navigation properties
+- Designing and saving change records
+- Capturing data even when exceptions happen
+
+This usually leads to:
+- **A lot of code** in every update method
+- **Easy-to-miss edge cases** and subtle bugs
+- **High maintenance** when entity models change
+- **Extra queries and comparisons** that can hurt performance
+- **Incomplete coverage** for complex scenarios
+
+## ABP Framework’s Built-in Solution
+
+ABP Framework includes a built-in audit logging system. It solves the problems above and adds useful features on top.
+
+### Simple Setup vs. Manual Tracking
+
+Instead of writing lots of code, you configure it once:
+
+```csharp
+// Configure audit log options in the module's ConfigureServices method
+Configure(options =>
+{
+ options.IsEnabled = true; // Enable audit log system (default value)
+ options.IsEnabledForAnonymousUsers = true; // Track anonymous users (default value)
+ options.IsEnabledForGetRequests = false; // Skip GET requests (default value)
+ options.AlwaysLogOnException = true; // Always log on errors (default value)
+ options.HideErrors = true; // Hide audit log errors (default value)
+ options.EntityHistorySelectors.AddAllEntities(); // Track all entity changes
+});
+```
+
+```csharp
+// Add middleware in the module's OnApplicationInitialization method
+public override void OnApplicationInitialization(ApplicationInitializationContext context)
+{
+ var app = context.GetApplicationBuilder();
+
+ // Add audit log middleware - one line of code solves all problems!
+ app.UseAuditing();
+}
+```
+
+By contrast, manual tracking needs middleware, controller logic, exception handling, and often hundreds of lines. With ABP, a couple of lines enable it and it just works.
+
+## What You Get with ABP
+
+Here’s how ABP removes tracking code from your application and still captures what you need.
+
+### 1. Application Services: No Tracking Code
+
+Manual approach: You’d log inside each method and still risk missing cases.
+
+ABP approach: Tracking is automatic—no tracking code in your methods.
+
+```csharp
+public class BookAppService : ApplicationService
+{
+ private readonly IRepository _bookRepository;
+ private readonly IRepository _authorRepository;
+
+ [Authorize(BookPermissions.Create)]
+ public virtual async Task CreateAsync(CreateBookDto input)
+ {
+ // No need to write any tracking code!
+ // ABP automatically tracks:
+ // - Method calls and parameters
+ // - Calling user
+ // - Execution duration
+ // - Any exceptions thrown
+
+ var author = await _authorRepository.GetAsync(input.AuthorId);
+ var book = new Book(input.Title, author, input.Price);
+
+ await _bookRepository.InsertAsync(book);
+
+ return ObjectMapper.Map(book);
+ }
+
+ [Authorize(BookPermissions.Update)]
+ public virtual async Task UpdateAsync(Guid id, UpdateBookDto input)
+ {
+ var book = await _bookRepository.GetAsync(id);
+
+ // No need to write any entity change tracking code!
+ // ABP automatically tracks entity changes:
+ // - Which properties changed
+ // - Old and new values
+ // - When the change happened
+
+ book.ChangeTitle(input.Title);
+ book.ChangePrice(input.Price);
+
+ await _bookRepository.UpdateAsync(book);
+
+ return ObjectMapper.Map(book);
+ }
+}
+```
+
+With manual code, each method might need 20–30 lines for tracking. With ABP, it’s zero—and you still get richer data.
+
+For entity changes, ABP also saves you from writing comparison code. It handles:
+- Property change detection
+- Recording old and new values
+- Complex types and collections
+- Navigation property changes
+- All with no extra code to maintain
+
+### 2. Entity Change Tracking: One Line to Turn It On
+
+Manual approach: You’d compare properties, serialize complex types, track collection changes, and write to storage.
+
+ABP approach: Mark the entity or select entities globally.
+
+```csharp
+// Enable audit log for specific entity - one line of code solves all problems!
+[Audited]
+public class MyEntity : Entity
+{
+ public string Name { get; set; }
+ public string Description { get; set; }
+
+ [DisableAuditing] // Exclude sensitive data - security control
+ public string InternalNotes { get; set; }
+}
+```
+
+```csharp
+// Or global configuration - batch processing
+Configure(options =>
+{
+ // Track all entities - one line of code tracks all entity changes
+ options.EntityHistorySelectors.AddAllEntities();
+
+ // Or use custom selector - precise control
+ options.EntityHistorySelectors.Add(
+ new NamedTypeSelector(
+ "MySelectorName",
+ type => typeof(IEntity).IsAssignableFrom(type)
+ )
+ );
+});
+```
+
+### 3. Extension Features
+
+Manual approach: Adding custom tracking usually spreads across many places and is hard to test.
+
+ABP approach: Use a contributor for clean, centralized extensions.
+
+```csharp
+public class MyAuditLogContributor : AuditLogContributor
+{
+ public override void PreContribute(AuditLogContributionContext context)
+ {
+ var currentUser = context.ServiceProvider.GetRequiredService();
+
+ // Easily add custom properties - manual implementation needs lots of work
+ context.AuditInfo.SetProperty(
+ "MyCustomClaimValue",
+ currentUser.FindClaimValue("MyCustomClaim")
+ );
+ }
+
+ public override void PostContribute(AuditLogContributionContext context)
+ {
+ // Add custom comments - business logic integration
+ context.AuditInfo.Comments.Add("Some comment...");
+ }
+}
+
+// Register contributor - one line of code enables extension features
+Configure(options =>
+{
+ options.Contributors.Add(new MyAuditLogContributor());
+});
+```
+
+### 4. Precise Control
+
+Manual approach: You end up with complex conditional logic.
+
+ABP approach: Use attributes for simple, precise control.
+
+```csharp
+// Disable audit log for specific controller - precise control
+[DisableAuditing]
+public class HomeController : AbpController
+{
+ // Health check endpoints won't be audited - avoid meaningless logs
+}
+
+// Disable for specific action - method-level control
+public class HomeController : AbpController
+{
+ [DisableAuditing]
+ public async Task Home()
+ {
+ // This action won't be audited - public data access
+ }
+
+ public async Task OtherActionLogged()
+ {
+ // This action will be audited - important business operation
+ }
+}
+```
+
+### 5. Visual Management of Audit Logs
+
+ABP also provides a UI to browse and inspect audit logs:
+
+
+
+
+
+## Manual vs. ABP: A Quick Comparison
+
+The benefits of ABP’s audit log system compared to doing it by hand:
+
+| Aspect | Manual Implementation | ABP Audit Logs |
+|--------|----------------------|----------------|
+| **Setup Complexity** | High — Write middleware, services, repository code | Low — A few lines of config, works out of the box |
+| **Code Maintenance** | High — Tracking code spread across the app | Low — Centralized, convention-based |
+| **Consistency** | Variable — Depends on discipline | Consistent — Automated and standardized |
+| **Performance** | Risky without careful tuning | Built-in optimizations and scope control |
+| **Functionality Completeness** | Basic tracking only | Comprehensive by default |
+| **Error Handling** | Easy to miss edge cases | Automatic and reliable |
+| **Data Integrity** | Manual effort required | Handled by the framework |
+| **Extensibility** | Custom work is costly | Rich extension points |
+| **Development Efficiency** | Weeks to build | Minutes to enable |
+| **Learning Cost** | Understand many details | Convention-based, low effort |
+
+## Why ABP Audit Logs Matter
+
+ABP’s audit logging removes the boilerplate from user tracking in ASP.NET Core apps.
+
+### Core Idea
+
+Manual tracking is error-prone and hard to maintain. ABP gives you a convention-based, automated system that works with minimal setup.
+
+### Key Benefits
+
+ABP runs by convention, so you don’t need repetitive code. You can control behavior at the request, entity, and method levels. It automatically captures request details, operations, entity changes, and exceptions, and you can extend it with contributors when needed.
+
+### Results in Practice
+
+| Metric | Manual Implementation | ABP Implementation | Improvement |
+|--------|----------------------|-------------------|-------------|
+| Development Time | Weeks | Minutes | **99%+** |
+| Lines of Code | Hundreds of lines | 2 lines of config | **99%+** |
+| Maintenance Cost | High | Low | **Significant** |
+| Functionality Completeness | Basic | Comprehensive | **Significant** |
+| Error Rate | Higher risk | Lower risk | **Improved** |
+
+### Recommendation
+
+If you need audit logs, start with ABP’s built-in system. It reduces effort, improves consistency, and stays flexible as your app grows. You can focus on your business logic and let the framework handle the infrastructure.
+
+## References
+
+- [ABP Audit Logging](https://abp.io/docs/latest/framework/infrastructure/audit-logging)
+- [ABP Audit Logging UI](https://abp.io/modules/Volo.AuditLogging.Ui)
diff --git a/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/cover.png b/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/cover.png
new file mode 100644
index 0000000000..7030e285b2
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-03-Keep-Track-of-Your-Users-in-an-ASP.NET-Core-Application/cover.png differ
diff --git a/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/Post.md b/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/Post.md
new file mode 100644
index 0000000000..3de235e86d
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/Post.md
@@ -0,0 +1,173 @@
+# .NET 10: What You Need to Know (LTS Release, Coming November 2025)
+
+The next version of .NET is .NET 10 and it is coming with **Long-Term Support (LTS)**, scheduled for **November 2025**.
+
+On **September 9, 2025**, Microsoft released **.NET 10 Release Candidate 1 (RC1)**, which supports go-live usage and is compatible with [Visual Studio 2026 Insider](https://visualstudio.microsoft.com/insiders/) and [Visual Studio Code Insider](https://code.visualstudio.com/insiders/) via the [C# Dev Kit](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit) extension.
+
+------
+
+## .NET 10 Runtime Enhancements
+
+- **JIT Speed-ups**: Enhanced struct argument handling—members now go directly into registers, reducing memory load/store operations.
+- **Advanced Loop Optimization**: New graph-based loop inversion improves precision and boosts further optimizations.
+- **Array Interface De-virtualization**: Critical for performance, now array-based enumerations inline and skip virtual calls including de-abstraction of array enumeration and small-array stack allocation.
+- **General JIT Improvements**: Better code layout and branch reduction support overall efficiency.
+
+------
+
+## Language & Library Upgrades
+
+### C# 14 Enhancements
+
+- Field-backed properties: easier custom getters/setters.
+- `nameof` for unbound generics like `List<>`.
+- Implicit conversions for `Span` and `ReadOnlySpan`.
+- Lambda parameter modifiers (`ref`, `in`, `out`).
+- Partial constructors/events.
+- `extension` blocks for static extension members.
+- Null-conditional assignment (`?.=`) and custom compound/increment operators.
+
+### F# & Visual Basic Enhancements
+
+- F# improvements via `preview`, updated `FSharp.Core`, and compiler fixes.
+- VB compiler supports `unmanaged` generics and respects `OverloadResolutionPriorityAttribute` for performance and overload clarity.
+
+## .NET Libraries & SDK
+
+### Libraries:
+
+- Better ZipArchive performance (lazy entry loading).
+- JSON improvements, including `JsonSourceGenerationOptions` and reference-handling tweaks.
+- Enhanced `OrderedDictionary`, ISOWeek date APIs, PEM data and certificate handling, `CompareOptions.NumericOrdering`
+
+### SDK & CLI:
+
+- No major new SDK features in RC1—you should expect stability fixes rather than additions.
+- Earlier previews brought JSON support improvements (e.g., `PipeReader` for JSON, WebSocketStream, ML-DSA crypto, AES KeyWrap), TLS 1.3 for macOS
+
+------
+
+## ASP.NET Core & Blazor
+
+### Blazor & Web App Security:
+
+Enhanced OIDC and Microsoft Entra ID integration, including encrypted token caching and Key Vault use.
+
+### UI Enhancements:
+
+- `QuickGrid` gains `RowClass` for conditional styling.
+- Scripts now served as static assets with compression and fingerprinting.
+- NavigationManager no longer scrolls to top for same-page updates.
+
+### API Improvements:
+
+Full support for OpenAPI 3.1 (JSON Schema draft 2020-12), and metrics for authentication/authorization events (e.g., sign-ins, logins) .
+
+------
+
+## .NET MAUI
+
+Updates include multiple file selection, image compression, WebView request interception, and support for Android API 35/36.
+
+## EF Core
+
+LINQ enhancements, performance boosts, better Azure Cosmos DB support, and more flexible named query filters.
+
+
+
+## Breaking Changes in .NET 10
+
+### ASP.NET Core - Breaking Changes in .NET 10:
+
+.NET 10 Preview 7 brings **several deprecations + behavior changes**, while **RC1 removes the old WebHost model**.
+
+- **[Cookie login redirects disabled](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/cookie-authentication-api-endpoints)** → Redirects no longer occur for API endpoints; APIs now return `401`/`403`. *(Behavioral change)*
+- **[WithOpenApi deprecated](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/withopenapi-deprecated)** → Extension method removed; use updated OpenAPI generator features. *(Source incompatible)*
+- **[Exception diagnostics suppressed](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/exception-handler-diagnostics-suppressed)** → When `TryHandleAsync` returns true, exception details aren’t logged. *(Behavioral change)*
+- **[IActionContextAccessor obsolete](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/iactioncontextaccessor-obsolete)** → Marked obsolete; may break code depending on it. *(Source/behavioral change)*
+- **[IncludeOpenAPIAnalyzers deprecated](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/openapi-analyzers-deprecated)** → Property and MVC API analyzers removed. *(Source incompatible)*
+- **[IPNetwork & KnownNetworks obsolete](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/ipnetwork-knownnetworks-obsolete)** → Old networking APIs removed in favor of new ones. *(Source incompatible)*
+- **[ApiDescription.Client package deprecated](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/apidescription-client-deprecated)** → No longer maintained; migrate to other tools. *(Source incompatible)*
+- **[Razor run-time compilation obsolete](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/razor-runtime-compilation-obsolete)** → Disabled at runtime; precompilation required. *(Source incompatible)*
+- **[WebHostBuilder, IWebHost, WebHost obsolete](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/webhostbuilder-deprecated)** → Legacy hosting model deprecated; use `WebApplicationBuilder`. *(Source incompatible, RC1)*
+
+### EF Core - Breaking Changes in .NET 10:
+
+You can find the complete list at [Microsoft EF Core 10 Breaking Changes page](https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/breaking-changes). Here's the brief summary:
+
+#### EF Core - SQL Server
+
+- **JSON column type by default (Azure SQL / compat level ≥170).** Primitive collections and owned types mapped to JSON now use SQL Server’s native `json` type instead of `nvarchar(max)`. A migration may alter existing columns. Mitigate by setting compat level <170 or explicitly forcing `nvarchar(max)`.
+- **`ExecuteUpdateAsync` signature change.** Column setters now take a regular `Func<…>` (not an expression). Dynamic expression-tree code won’t compile; replace with imperative setters inside the lambda.
+
+#### Microsoft.Data.Sqlite
+
+- **`GetDateTimeOffset` (no offset) assumes UTC.** Previously assumed local time. You can temporarily revert via `AppContext.SetSwitch("Microsoft.Data.Sqlite.Pre10TimeZoneHandling", true)`.
+- **Writing `DateTimeOffset` to REAL stores UTC.** Conversion now happens before writing; revertable with the same switch.
+- **`GetDateTime` (with offset) returns UTC `DateTime` (`DateTimeKind.Utc`).** Was `Local` before. Same temporary switch if needed.
+
+#### Who’s most affected
+
+- Apps on **Azure SQL / SQL Server 2025** using JSON mapping.
+- Codebases building **expression trees** for bulk updates.
+- Apps using **SQLite** with date/time parsing or REAL timestamp storage.
+
+#### Quick mitigations
+
+- Set SQL Server compatibility <170 or force column type.
+- Rewrite `ExecuteUpdateAsync` callers to use the new delegate form.
+- For SQLite, update handling to UTC or use the temporary AppContext switch while transitioning.
+
+### Containers - Breaking Changes in .NET 10:
+
+Default .NET images now use [Ubuntu](https://learn.microsoft.com/en-us/dotnet/core/compatibility/containers/10.0/default-images-use-ubuntu).
+
+### Core Libraries - Breaking Changes in .NET 10:
+
+[ActivitySource](https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/10.0/activity-sampling) behavior tweaks; [generic math](https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/10.0/generic-math) shift behavior aligned; W3C trace context is [default](https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/10.0/default-trace-context-propagator); [DriveInfo](https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/10.0/driveinfo-driveformat-linux) reports Linux FS types; InlineArray size rules tightened; [System.Linq.AsyncEnumerable](https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/10.0/asyncenumerable) included in core libs...
+
+### Cryptography - Breaking Changes in .NET 10:
+
+[Stricter X500](https://learn.microsoft.com/en-us/dotnet/core/compatibility/cryptography/10.0/x500distinguishedname-validation) name validation; [OpenSSL](https://learn.microsoft.com/en-us/dotnet/core/compatibility/cryptography/10.0/openssl-macos-unsupported) primitives unsupported on macOS; [some key members](https://learn.microsoft.com/en-us/dotnet/core/compatibility/cryptography/10.0/mldsa-slhdsa-secretkey-to-privatekey) nullable/renamed; env var [rename to](https://learn.microsoft.com/en-us/dotnet/core/compatibility/cryptography/10.0/version-override) `DOTNET_OPENSSL_VERSION_OVERRIDE`.
+
+### Extensions - Breaking Changes in .NET 10:
+
+[Config preserves](https://learn.microsoft.com/en-us/dotnet/core/compatibility/extensions/10.0/configuration-null-values-preserved) nulls; [logging](https://learn.microsoft.com/en-us/dotnet/core/compatibility/extensions/10.0/console-json-logging-duplicate-messages)/[package](https://learn.microsoft.com/en-us/dotnet/core/compatibility/extensions/10.0/provideraliasattribute-moved-assembly)/trim annotations changes; some [trim-unsafe](https://learn.microsoft.com/en-us/dotnet/core/compatibility/extensions/10.0/dynamically-accessed-members-configuration) code annotations removed.
+
+### Globalization & Interop - Breaking Changes in .NET 10:
+
+[ICU](https://learn.microsoft.com/en-us/dotnet/core/compatibility/globalization/10.0/version-override) env var renamed; single-file apps stop probing executable dir for native libs; [DllImport](https://learn.microsoft.com/en-us/dotnet/core/compatibility/interop/10.0/search-assembly-directory) search path tightened.
+
+Networking:
+
+[HTTP/3 disabled ](https://learn.microsoft.com/en-us/dotnet/core/compatibility/networking/10.0/http3-disabled-with-publishtrimmed) by default when trimming; [default cert revocation](https://learn.microsoft.com/en-us/dotnet/core/compatibility/networking/10.0/ssl-certificate-revocation-check-default) check now Online; [browser clients](https://learn.microsoft.com/en-us/dotnet/core/compatibility/networking/10.0/default-http-streaming) stream responses by default; [URI length limits](https://learn.microsoft.com/en-us/dotnet/core/compatibility/networking/10.0/uri-length-limits-removed) removed.
+
+### SDK & MSBuild/NuGet - Breaking Changes in .NET 10:
+
+`dotnet --interactive` [defaults to true](https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/dotnet-cli-interactive); tool packages are [RID-specific](https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/dotnet-tool-pack-publish); [workload](https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/default-workload-config) sets default; `dotnet new sln` uses [SLNX](https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/dotnet-new-sln-slnx-default); restore audits transitives; [local tool](https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/dotnet-tool-install-local-manifest) install creates manifest by default; `project.json` [not supported](https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/dotnet-restore-project-json-unsupported); stricter NuGet [validation](https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/nuget-packageid-validation)/[errors](https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/http-warnings-to-errors).
+
+WinForms/WPF:
+
+Multiple [API obsoletions](https://learn.microsoft.com/en-us/dotnet/core/compatibility/windows-forms/10.0/obsolete-apis)/parameter [renames](https://learn.microsoft.com/en-us/dotnet/core/compatibility/windows-forms/10.0/insertadjacentelement-orientation); [rendering](https://learn.microsoft.com/en-us/dotnet/core/compatibility/windows-forms/10.0/statusstrip-renderer)/behavior tweaks; stricter XAML rules (e.g., [disallow empty row](https://learn.microsoft.com/en-us/dotnet/core/compatibility/wpf/10.0/empty-grid-definitions)/column definitions or incorrect usage of [DynamicResource](https://learn.microsoft.com/en-us/dotnet/core/compatibility/wpf/10.0/dynamicresource-crash) will crash).
+
+
+
+------
+
+
+
+## Support Policy for .NET 10
+As you can see from the picture below, **.NET 10 has long term support** therefore it will be maintained for 3 years **until November 2028**.
+
+[](https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core)
+
+
+
+## Download .NET10
+
+Click 👉 https://dotnet.microsoft.com/en-us/download/dotnet/10.0 to download the latest release candidate (currently RC.1).
+
+[](https://dotnet.microsoft.com/en-us/download/dotnet/10.0)
+
+Also to use the latest features, download/update your Visual Studio to the latest 👉 https://visualstudio.microsoft.com/downloads/
+
diff --git a/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/cover.png b/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/cover.png
new file mode 100644
index 0000000000..e85f53b9ec
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/cover.png differ
diff --git a/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/image-1.png b/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/image-1.png
new file mode 100644
index 0000000000..970f3194bc
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/image-1.png differ
diff --git a/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/image-2.png b/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/image-2.png
new file mode 100644
index 0000000000..6e5b57c588
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-10-NET10-What-You-Need-To-Know/image-2.png differ
diff --git a/docs/en/Community-Articles/2025-09-10-Truly-Layering-a-NET-Application-Based-on-DDD-Principles/coverimage.png b/docs/en/Community-Articles/2025-09-10-Truly-Layering-a-NET-Application-Based-on-DDD-Principles/coverimage.png
new file mode 100644
index 0000000000..41499bea9a
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-10-Truly-Layering-a-NET-Application-Based-on-DDD-Principles/coverimage.png differ
diff --git a/docs/en/Community-Articles/2025-09-10-Truly-Layering-a-NET-Application-Based-on-DDD-Principles/post.md b/docs/en/Community-Articles/2025-09-10-Truly-Layering-a-NET-Application-Based-on-DDD-Principles/post.md
new file mode 100644
index 0000000000..03981e04c6
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-10-Truly-Layering-a-NET-Application-Based-on-DDD-Principles/post.md
@@ -0,0 +1,191 @@
+# **Truly Layering a .NET Application Based on DDD Principles**
+
+Okay, so we ALL been there, right? You start new project thinking "this time will be different" - clean code, perfect architecture, everything organized. Fast forward 3 months and your codebase look like someone throw grenade into bowl of spaghetti. Business logic everywhere, your controllers doing database work, and every new feature feel like defusing bomb.
+
+I been there too many times, and honestly, it suck. But here thing - there actually way to build .NET apps that not turn into maintenance nightmare. It called **Layered Architecture** + **Domain-Driven Design (DDD)**, and once you get it, it game changer.
+
+Let me walk you through this step by step, no fluff, just practical stuff that actually work.
+
+### **Layered Architecture 101 (The Foundation)**
+
+So layered architecture basically about keeping your code organized. Instead of having everything mixed together like bad smoothie, you separate concerns into different layers. Think like organizing your room - clothes go in closet, books on shelf, etc.
+
+Here how it typically break down:
+
+ * **Presentation Layer (UI):** This what users actually see and click on - your ASP.NET Core MVC stuff, Razor Pages, Blazor, whatever float your boat.
+ * **Application Layer:** The conductor of orchestra. It not do heavy lifting itself, but tell everyone else what to do. It like middle manager of your code.
+ * **Domain Layer:** The VIP section. This where all your business rules live - entities, value objects, whole nine yards. This layer pure and not give damn about databases or UI.
+ * **Infrastructure Layer:** The "how-to" guy. Database stuff, email sending, API calls - basically all technical plumbing that make everything work.
+
+The golden rule? **Dependency Rule**: Layers can only talk to layers below them (or more central). UI talk to Application, Application talk to Domain, but Domain? Domain not talk to anyone. It the cool kid that everyone want to hang out with.
+
+### **DDD: Where Magic Happen**
+
+Alright, so DDD not some fancy framework you install from NuGet. It more like mindset - basically saying "hey, let make our code actually reflect business we building for." Instead of having bunch of random classes, we organize everything around actual business domain.
+
+Think like this: if you building e-commerce app, your code should scream "I'M E-COMMERCE APP" not "I'M BUNCH OF RANDOM CLASSES."
+
+Here toolkit DDD give you (all living in your Domain Layer):
+
+ * **Entity:** This something that have identity. Like `Customer` - two customers with same name still different people because they have different IDs. It like having two friends named John - they not same person.
+ * **Value Object:** Opposite of entity. It defined by what it contain, not who it is. `Address` perfect for this - if two addresses have same street, city, and zip code, they same address. Usually immutable too.
+ * **Aggregate & Aggregate Root:** This where it get interesting. Aggregate like family of related objects that stick together. **Aggregate Root** head of family - only one you talk to when you want change something. Like `Order` that contain `OrderItem`s. You not mess with `OrderItem` directly, you tell `Order` to handle it.
+ * **Repository (Interface):** Think like your data access contract. It say "here how you can get and save stuff" without caring about whether it SQL Server, MongoDB, or file on your desktop. Interface live in Domain, implementation go in Infrastructure.
+ * **Domain Service:** When business logic too complex for single entity or value object, this your go-to. It like utility class but for business rules.
+
+### **Putting It All Together: Real C# Code**
+
+Alright, enough theory. Let see what this actually look like in real .NET solution. You typically have projects like:
+
+ * `MyProject.Domain` (or `.Core`) - The VIP section
+ * `MyProject.Application` - The middle manager
+ * `MyProject.Infrastructure` - The technical guy
+ * `MyProject.Web` (or whatever UI you using) - The pretty face
+
+**1. The Domain Layer (`MyProject.Domain`) - The Heart**
+
+This where magic happen. Zero dependencies on other projects (maybe some basic utility libraries, but that it). Pure business logic, no database nonsense, no UI concerns.
+
+```csharp
+// In MyProject.Domain/Orders/Order.cs
+public class Order : AggregateRoot
+{
+ public Address ShippingAddress { get; private set; }
+ private readonly List _orderItems = new();
+ public IReadOnlyCollection OrderItems => _orderItems.AsReadOnly();
+
+ // Private constructor for ORM
+ private Order() { }
+
+ public Order(Guid id, Address shippingAddress) : base(id)
+ {
+ ShippingAddress = shippingAddress;
+ }
+
+ public void AddOrderItem(Guid productId, int quantity, decimal price)
+ {
+ if (quantity <= 0)
+ {
+ throw new BusinessException("Quantity must be greater than zero.");
+ }
+ // More business rules...
+ _orderItems.Add(new OrderItem(productId, quantity, price));
+ }
+}
+
+// In MyProject.Domain/Orders/IOrderRepository.cs
+public interface IOrderRepository
+{
+ Task GetAsync(Guid id);
+ Task AddAsync(Order order);
+ Task UpdateAsync(Order order);
+}
+```
+
+See what I mean? The `Order` class all about business rules (`AddOrderItem` with validation and all that jazz). It not give damn about databases or how it get saved. That someone else problem.
+
+**2. The Application Layer (`MyProject.Application`) - The Conductor**
+
+This where we orchestrate everything. It talk to domain objects and use repositories to get/save data. Think like middle manager that coordinate work but not do heavy lifting.
+
+```csharp
+// In MyProject.Application/Orders/OrderAppService.cs
+public class OrderAppService
+{
+ private readonly IOrderRepository _orderRepository;
+
+ public OrderAppService(IOrderRepository orderRepository)
+ {
+ _orderRepository = orderRepository;
+ }
+
+ public async Task CreateOrderAsync(CreateOrderDto input)
+ {
+ var shippingAddress = new Address(input.Street, input.City, input.ZipCode);
+ var order = new Order(Guid.NewGuid(), shippingAddress);
+
+ foreach (var item in input.Items)
+ {
+ order.AddOrderItem(item.ProductId, item.Quantity, item.Price);
+ }
+
+ await _orderRepository.AddAsync(order);
+ }
+}
+```
+
+The application service coordinate everything but let domain objects handle actual business rules. Clean separation!
+
+**3. The Infrastructure Layer (`MyProject.Infrastructure`) - The Technical Guy**
+
+This where we implement all interfaces we defined in domain. Entity Framework Core, email services, API clients - all technical plumbing live here.
+
+```csharp
+// In MyProject.Infrastructure/Orders/EfCoreOrderRepository.cs
+public class EfCoreOrderRepository : IOrderRepository
+{
+ private readonly MyDbContext _dbContext;
+
+ public EfCoreOrderRepository(MyDbContext dbContext)
+ {
+ _dbContext = dbContext;
+ }
+
+ public async Task GetAsync(Guid id)
+ {
+ // EF Core logic to get the order
+ return await _dbContext.Orders.FindAsync(id);
+ }
+
+ public async Task AddAsync(Order order)
+ {
+ await _dbContext.Orders.AddAsync(order);
+ }
+
+ // ... other implementations
+}
+```
+
+### **ABP Framework: The Shortcut (Because We Lazy)**
+
+Look, setting all this up from scratch pain. That where **ABP Framework** come in clutch. It basically DDD and layered architecture on steroids, and it do all boring setup work for you.
+
+ABP not just talk talk - it walk walk. When you create new ABP solution, boom! Perfect project structure, all layered and DDD-compliant, ready to go.
+
+Here what you get out of box:
+
+ * **Base Classes:** `AggregateRoot`, `Entity`, `ValueObject` - all with good stuff like optimistic concurrency and domain events. No more writing boilerplate.
+ * **Generic Repositories:** No more writing `IRepository` interfaces for every single entity. ABP give you `IRepository` with all standard CRUD methods. Just inject it and go.
+ * **Application Services:** Inherit from `ApplicationService` and boom - you done. It handle validation, authorization, exception handling, all that cross-cutting concern stuff without cluttering your actual business logic.
+
+With ABP, our `OrderAppService` become way cleaner:
+
+```csharp
+// In ABP project, this much cleaner
+public class OrderAppService : ApplicationService, IOrderAppService
+{
+ private readonly IRepository _orderRepository;
+
+ public OrderAppService(IRepository orderRepository)
+ {
+ _orderRepository = orderRepository;
+ }
+
+ public async Task CreateAsync(CreateOrderDto input)
+ {
+ // ... same logic as before, but using ABP generic repository
+ var order = new Order(...);
+ await _orderRepository.InsertAsync(order);
+ }
+}
+```
+
+### **Wrapping Up**
+
+Look, I get it - this stuff take discipline and it not always fastest way to get features out door. But here thing: when you actually layer your app properly and put solid Domain Model at center, you end up with software that not suck to maintain.
+
+Your code start speaking language of business instead of some random technical jargon. That whole point of DDD - make your code reflect what you actually building for.
+
+Yeah, it take work upfront, but payoff huge. And frameworks like ABP make journey way less painful. Trust me, your future self will thank you when you not debugging spaghetti code at 2 AM.
+
+What you think? You try this approach before, or you still stuck in spaghetti code phase? Let me know in comments!
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-09-11-Best-Practices-Guide-for-REST-API-Design/post.md b/docs/en/Community-Articles/2025-09-11-Best-Practices-Guide-for-REST-API-Design/post.md
new file mode 100644
index 0000000000..6a20336307
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-11-Best-Practices-Guide-for-REST-API-Design/post.md
@@ -0,0 +1,333 @@
+# Best Practices Guide for REST API Design
+
+This guide compiles best practices for building robust, scalable, and sustainable RESTful APIs, based on information gathered from various sources.
+
+## 1. Fundamentals of REST Architecture
+
+REST is based on specific constraints and principles that support features like simplicity, scalability, and statelessness. The six core principles of RESTful architecture are:
+
+- **Uniform Interface**: This is about consistency. You use standard HTTP methods (GET, POST, PUT, DELETE) and URIs to interact with resources. The client knows how to talk to the server without needing some custom instruction manual.
+
+- **Client-Server**: The client (e.g., a frontend app) and the server are separate. The server handles data and logic, the client handles the user interface. They can evolve independently as long as the API contract doesn't change.
+
+- **Stateless**: This is a big one. The server doesn't remember anything about the client between requests. Every single request must contain all the info needed to process it (like an auth token). This is key for scalability.
+
+- **Cacheable**: Responses should declare whether they can be cached or not. Good caching can massively improve performance and reduce server load.
+
+- **Layered System**: You can have things like proxies or load balancers between the client and the server without the client knowing. It just talks to one endpoint, and the layers in between handle the rest.
+
+- **Code on Demand (Optional)**: This is the only optional one. It means the server can send back executable code (like JavaScript) to the client. Less common in the world of modern SPAs, but it's part of the spec.
+
+## 2. URI Design and Naming Conventions
+
+The URI structure is critical for making your API understandable and intuitive.
+
+### Use Nouns Instead of Verbs
+
+Your URIs should represent things (resources), not actions. The HTTP method already tells you what the action is.
+
+- **Good:** `/api/users`
+
+- **Bad:** `/api/getUsers`
+
+### Use Plural Nouns for Resource Names
+
+Stick with plural nouns for collections. It keeps things consistent, even when you're accessing a single item from that collection.
+
+- **Get all users:** `GET /api/users`
+
+- **Get a single user:** `GET /api/users/{id}`
+
+### Use Nested Routes to Show Relationships
+
+If a resource only exists in the context of another (like a user's orders), reflect that in the URL.
+
+- **Good:** `/api/users/{userId}/orders` (All orders for a user)
+
+- **Bad:** `/api/orders?userId={userId}`
+
+- **Good:** `/api/users/{userId}/orders/{orderId}` (A specific order for a user)
+
+**Note:** Use this structure only if the child resource is tightly coupled to the parent. Avoid nesting deeper than two or three levels, as this can complicate the URIs.
+
+### Path Parameters vs. Query Parameters
+
+Use the correct parameter type based on its function.
+
+- **Path Parameters (`/users/{id}`):** Use these to identify a specific resource or a collection. They are mandatory for the endpoint to resolve.
+
+ - *Example:* `GET /api/users/123` uniquely identifies user 123.
+
+- **Query Parameters (`?key=value`):** Use these for optional actions like filtering, sorting, or pagination on a collection.
+
+ - *Example:* `GET /api/users?role=admin&sort=lastName` filters the user collection.
+
+### Keep the URL Structure Consistent
+
+- **Use lowercase letters:** Since some systems are case-sensitive, always use lowercase in URIs for consistency.
+
+ - *Example:* Use `/api/product-offers` instead of `/api/Product-Offers`.
+
+- **Use special characters correctly:** Use characters like `/`, `?`, and `#` only for their defined purposes.
+
+ - *Example:* To get comments for a specific post, use the path `/posts/123/comments`. To filter those comments, use a query parameter: `/posts/123/comments?authorId=45`.
+
+## 3. Correct Usage of HTTP Methods
+
+Each HTTP method has a specific purpose. Sticking to these standards makes your API predictable.
+
+| **HTTP Method** | **Description** | **Idempotent*** | **Safe**** |
+| --------------- | --------------------------------------------------------------------------- | --------------- | ---------- |
+| **GET** | Retrieves a resource or a collection of resources. | Yes | Yes |
+| **POST** | Creates a new resource. | No | No |
+| **PUT** | Updates an existing resource completely or creates it if it does not exist. | Yes | No |
+| **PATCH** | Partially updates an existing resource. | No | No |
+| **DELETE** | Deletes a resource. | Yes | No |
+
+- **Idempotent:** Doing it once has the same effect as doing it 100 times. Deleting a user is idempotent; once it's gone, it's gone.
+
+- **Safe:** The request doesn't change anything on the server. GET is safe.
+
+**Example in practice:**
+
+Let's consider a resource endpoint for a collection of articles: `/api/articles`.
+
+- **`GET /api/articles`**: Retrieves a list of all articles.
+
+- **`GET /api/articles/123`**: Retrieves the specific article with ID 123.
+
+- **`POST /api/articles`**: Creates a new article. The data for the new article is sent in the request body.
+
+- **`PUT /api/articles/123`**: Replaces the entire article with ID 123 using the new data sent in the request body.
+
+- **`PATCH /api/articles/123`**: Partially updates the article with ID 123. For example, you could send only the `{"title": "New Title"}` in the request body to update just the title.
+
+- **`DELETE /api/articles/123`**: Deletes the article with ID 123.
+
+## 4. Data Exchange and Responses
+
+### Prefer the JSON Format
+
+It's the standard. It's lightweight, human-readable, and every language can parse it easily. Send and receive your data as JSON.
+
+- *Example Request Body:*
+
+ ```
+ {
+ "title": "Best Practices for APIs",
+ "authorId": 5,
+ "content": "An article about designing great APIs..."
+ }
+ ```
+
+### Use Appropriate HTTP Status Codes
+
+Use standard HTTP status codes to provide clear information to the client about the outcome of their request.
+
+- **2xx (Success):**
+
+ - `200 OK`: The request was successful. (For GET, PUT, PATCH)
+
+ - `201 Created`: The resource was successfully created. (For POST) The response should include a `Location` header with the URI of the new resource.
+
+ - *Example:* `POST /api/articles` responds with `201 Created` and the header `Location: /api/articles/124`.
+
+ - `204 No Content`: The request was successful, but there is no response body. (For DELETE)
+
+- **4xx (Client Error):**
+
+ - `400 Bad Request`: Invalid request (e.g., missing or incorrect data).
+
+ - `401 Unauthorized`: Authentication is required.
+
+ - `403 Forbidden`: No permission.
+
+ - `404 Not Found`: The requested resource could not be found.
+
+- **5xx (Server Error):**
+
+ - `500 Internal Server Error`: An unexpected error occurred on the server.
+
+### Provide Clear and Consistent Error Responses
+
+When something goes wrong, give back a useful JSON error message. Your future self and any developer using your API will thank you.
+
+- *Example of a detailed error response:*
+
+```
+{
+ "type": "[https://---.com/probs/validation-error](https://example.com/probs/validation-error)",
+ "title": "Your request parameters didn't validate.",
+ "status": 400,
+ "detail": "The 'email' field must be a valid email address.",
+ "instance": "/api/users"
+}
+```
+
+## 5. Performance Optimization
+
+Optimizing API performance is crucial for providing a good user experience and ensuring the scalability of your service. Key strategies include caching, efficient data retrieval, and controlling traffic.
+
+### Caching
+
+Caching is one of the most effective ways to improve performance. By storing and reusing frequently accessed data, you can significantly reduce latency and server load.
+
+- **How it works:** Caching can be implemented at various levels (client-side, CDN, server-side). REST APIs can facilitate this by using standard HTTP caching headers.
+
+- **Key Headers:**
+
+ - `Cache-Control`: Tells the client how long to cache something (e.g., `public, max-age=600`).
+
+ - `ETag`: A unique version identifier for a resource. The client can send this back in an `If-None-Match` header. If the data hasn't changed, you can just return `304 Not Modified` with an empty body, saving bandwidth.
+
+ - `Last-Modified`: Indicates when the resource was last changed. Similar to `ETag`, it can be used for conditional requests with the `If-Modified-Since` header.
+
+- *Example Response Header for Caching:*
+
+ ```
+ Cache-Control: public, max-age=600
+ ETag: "x234dff"
+ ```
+
+### Filtering, Sorting, and Pagination
+
+For endpoints that return lists of resources, it's inefficient to return the entire dataset at once, especially if it's large. Implementing these features gives clients more control over the data they receive.
+
+- **Filtering:** Allows clients to narrow down the result set based on specific criteria. This reduces the amount of data transferred and makes it easier for the client to find what it needs.
+
+ - *Example:* `GET /api/orders?status=shipped&customer_id=123`
+
+- **Sorting:** Enables clients to request the data in a specific order. A common convention is to specify the field to sort by and the direction (ascending or descending).
+
+ - *Example:* `GET /api/users?sort=lastName_asc` or `GET /api/products?sort=-price` (the `-` indicates descending order).
+
+- **Pagination:** Breaks down a large result set into smaller, manageable chunks called "pages". This prevents overloading the server and client with massive amounts of data in a single response.
+
+ - *Example:* `GET /api/articles?page=2&pageSize=20` (retrieves the second page, with 20 articles per page).
+
+### Rate Limiting
+
+Protect your API from abuse by limiting how many requests a client can make in a given time. If they exceed the limit, return a `429 Too Many Requests`.
+It's also super helpful to return these headers so the client knows what's going on:
+
+- `X-RateLimit-Limit`: Total requests allowed.
+
+- `X-RateLimit-Remaining`: How many requests they have left.
+
+- `Retry-After`: How many seconds they should wait before trying again.
+
+## 6. Security
+
+Security is not an optional feature; it must be a core part of your API design.
+
+- **Always Use HTTPS (TLS):** Encrypt all traffic to prevent man-in-the-middle attacks. There are no exceptions to this rule for production APIs.
+
+- **Authentication & Authorization:**
+
+ - **Authentication** (Who are you?): Use a standard like OAuth 2.0 or JWT Bearer Tokens.
+
+ - **Authorization** (What are you allowed to do?): Check permissions for every request. Just because a user is logged in doesn't mean they can delete another user's data.
+
+- **Input Validation**: Always validate and sanitize data coming from the client to prevent injection attacks. If the data is bad, reject it with a `400 Bad Request`.
+
+- **Use Security Headers**: Add headers like `Strict-Transport-Security` and `Content-Security-Policy` to add extra layers of browser-level protection.
+
+## 7. API Lifecycle Management
+
+### Versioning
+
+Your API will change. Versioning lets you make breaking changes without messing up existing clients. The most common way is in the URI.
+
+- **URI Versioning (Most Common):** `https://api.example.com/v1/users`
+
+ - **Pros:** Simple, explicit, and easy to explore in a browser.
+
+- **Header Versioning:** The client requests a version via a custom HTTP header.
+
+ - *Example:* `Accept-Version: v1`
+
+ - **Pros:** Keeps the URI clean.
+
+- **Media Type Versioning (Content Negotiation):** The version is included in the `Accept` header.
+
+ - *Example:* `Accept: application/vnd.example.v1+json`
+
+ - **Pros:** Technically the "purest" REST approach.
+
+### Backward Compatibility & Deprecation
+
+When you release v2, don't just kill v1. Keep it running for a while and communicate a clear shutdown schedule to your users.
+
+### Documentation
+
+An API is only as good as its documentation. Use tools like the **OpenAPI Specification (formerly Swagger)** to generate interactive, machine-readable documentation. Good docs should include:
+
+- Authentication instructions.
+
+- Clear explanations of each endpoint.
+
+- Request/response examples.
+
+- Error code definitions.
+
+## 8. Monitoring and Testing
+
+### Monitoring and Logging
+
+To ensure your API is reliable, you must monitor its health and log important events.
+
+- **Structured Logging:** Log in a machine-readable format like JSON. Include a `correlationId` to track a single request across multiple services.
+
+- **Monitoring:** Track key metrics like latency (response time), error rate, and requests per second. Use tools like Prometheus, Grafana, or Datadog to visualize these metrics and set up alerts.
+
+### API Testing
+
+Thorough testing is essential to prevent bugs and regressions.
+
+- **Unit Tests:** Test individual components and business logic in isolation.
+
+- **Integration Tests:** Test the interaction between different parts of your API, including the database.
+
+- **Contract Tests:** Verify that your API adheres to its documented contract (e.g., the OpenAPI spec).
+
+## 9. Advanced Level: HATEOAS
+
+**HATEOAS (Hypermedia as the Engine of Application State)** is a REST principle that allows your API to be self-documenting and more discoverable. It involves including hyperlinks in responses for actions that can be performed on the relevant resource.
+
+For example, a response for a user resource might look like this:
+
+```
+{
+ "id": 1,
+ "name": "Deo Steel",
+ "links": [
+ { "rel": "self", "href": "/users/1", "method": "GET" },
+ { "rel": "update", "href": "/users/1", "method": "PUT" },
+ { "rel": "delete", "href": "/users/1", "method": "DELETE" }
+ ]
+}
+```
+
+This way, the client can follow the links in the response to take the next step, rather than manually constructing the URIs.
+
+## 10. A Practical Shortcut: Leveraging Frameworks like ABP.IO
+
+Okay, that was a lot. While it's crucial to understand all these principles, you don't have to build everything from scratch. Modern frameworks can handle a ton of this for you. I work a lot in the .NET space, and **ABP Framework** is a great example of this.
+
+Here’s how it automates many of the things we just talked about:
+
+- **Automatic API Controllers**: You write your business logic in an "Application Service," and ABP automatically creates the REST API endpoints for you, following all the correct naming and HTTP method conventions. (Covers sections 2 & 3).
+
+- **Built-in Best Practices**:
+
+ - **Standardized Error Responses**: It has a built-in exception handling system that automatically generates clean, consistent JSON error responses. (Covers section 4).
+
+ - **Input Validation**: It has automatic validation for your DTOs. If a request is invalid, it returns a detailed `400 Bad Request` without you writing a single line of code for it. (Covers section 6).
+
+ - **Paging, Sorting, Filtering**: You get these out of the box by just using their predefined interfaces. (Covers section 5).
+
+- **Integrated Security**: It comes with a full auth system. You just add an `[Authorize]` attribute to a method, and it handles the rest. It also automatically manages database transactions per API request (Unit of Work) to ensure data consistency. (Covers section 6).
+
+- **Automatic Documentation**: It automatically generates an OpenAPI/Swagger UI for your API, which is a massive help for anyone who needs to use it. (Covers section 7).
+
+Using a framework like this lets you focus on your core business logic, confident that the foundation is built on solid, established best practices.
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/BenchmarkDotnet.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/BenchmarkDotnet.png
new file mode 100644
index 0000000000..ed81071118
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/BenchmarkDotnet.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Disruptor.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Disruptor.png
new file mode 100644
index 0000000000..d66333865c
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Disruptor.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/MemoryPack.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/MemoryPack.png
new file mode 100644
index 0000000000..cdb4f81e38
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/MemoryPack.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/MessagePack.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/MessagePack.png
new file mode 100644
index 0000000000..dc7d76dd2f
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/MessagePack.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Polly.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Polly.png
new file mode 100644
index 0000000000..18a930df0e
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Polly.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Post.md b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Post.md
new file mode 100644
index 0000000000..fbe358c8cb
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/Post.md
@@ -0,0 +1,157 @@
+# High-Performance .NET Libraries You Didn’t Know You Needed
+
+Whether you’re building enterprise apps, microservices, or SaaS platforms, using the right libraries can help you ship faster and scale effortlessly.
+Here are some **high-performance .NET libraries** you might not know but definitely should.
+
+
+
+## 1. BenchmarkDotNet – Measure before you optimize
+
+
+
+BenchmarkDotNet makes it simple to **benchmark .NET code with precision**.
+
+- Easy setup with `[Benchmark]` attributes
+- Generates detailed performance reports
+- Works with .NET Core, .NET Framework, and Mono
+
+Perfect for spotting bottlenecks in APIs, background services, or CPU-bound operations.
+
+- **NuGet** (40M downloads) 🔗 https://www.nuget.org/packages/BenchmarkDotNet
+- **GitHub** (11k stars) 🔗 https://github.com/dotnet/BenchmarkDotNet
+
+
+
+## 2. MessagePack – Fastest JSON serializer
+
+Need speed beyond System.Text.Json or Newtonsoft.Json? MessagePack is the fastest serializer for C# (.NET, .NET Core, Unity, Xamarin). MessagePack has a compact binary size and a full set of general-purpose expressive data types. Ideal for high-traffic APIs, IoT data processing, and microservices.
+
+
+
+- **NuGet** (204M downloads) 🔗 https://www.nuget.org/packages/messagepack
+- **GitHub** (6.4K stars) 🔗 https://github.com/MessagePack-CSharp/MessagePack-CSharp
+
+
+
+## 3. Polly – Resilience at scale
+
+
+
+In distributed systems, failures are inevitable. **Polly** provides a fluent way to add **retry, circuit-breaker, and fallback** strategies.
+
+- Handle transient faults gracefully
+- Improve uptime and user experience
+- Works seamlessly with HttpClient and gRPC
+
+A must-have for cloud-native .NET applications.
+
+- **NuGet** (1B downloads) 🔗 https://www.nuget.org/packages/polly/
+- **GitHub** (14K stars) 🔗 https://github.com/App-vNext/Polly
+
+
+
+## 4. MemoryPack – Zero-cost binary serialization
+
+If you need **blazing-fast serialization** for in-memory caching or network transport, **MemoryPack** is a game-changer.
+
+- Zero-copy, zero-alloc serialization
+- Perfect for high-performance caching or game servers
+- Strongly typed and version-tolerant
+
+
+
+Great for real-time multiplayer games, chat apps, or financial systems.
+
+- **NuGet** (5.3M downloads) 🔗 https://www.nuget.org/packages/MemoryPack
+- **GitHub** (4K stars) 🔗 https://github.com/Cysharp/MemoryPack
+
+
+
+## 5. WolverineFx – Ultra-low latency messaging
+
+
+
+MediatR was one of the best mediator libraries, but now it's a paid library. Wolverine is a toolset for command execution and message handling within .NET applications. The killer feature of Wolverine is its very efficient command execution pipeline that can be used as:
+
+- An [inline "mediator" pipeline](https://wolverinefx.net/tutorials/mediator.html) for executing commands
+- A [local message bus](https://wolverinefx.net/guide/messaging/transports/local.html) for in-application communication
+- A full-fledged [asynchronous messaging framework](https://wolverinefx.net/guide/messaging/introduction.html) for robust communication and interaction between services when used in conjunction with low-level messaging infrastructure tools like RabbitMQ
+- With the [WolverineFx.Http](https://wolverinefx.net/guide/http/) library, Wolverine's execution pipeline can be used directly as an alternative ASP.NET Core Endpoint provider
+
+*image below is from [codecrash.net](https://www.codecrash.net/2024/02/06/Mediatr-versus-Wolverine-performance.html)*
+
+
+WolverineFx is great for cleanly separating business logic from controllers while unifying in-process mediator patterns with powerful distributed messaging in a single, high-performance .NET library.
+
+- **NuGet** (1.5M downloads) 🔗 https://www.nuget.org/packages/WolverineFx
+- **GitHub** (1.7K stars) 🔗 https://github.com/JasperFx/wolverine
+
+
+## 6. Disruptor-net – Next generation free .NET mediator
+
+The Disruptor is a high-performance inter-thread message passing framework. A lock-free ring buffer for ultra-low latency messaging.
+Features are:
+
+- Zero memory allocation after initial setup (the events are pre-allocated).
+
+- Push-based consumers.
+
+- Optionally lock-free.
+
+- Configurable wait strategies.
+
+
+
+- **NuGet** (1.2M downloads) 🔗 https://www.nuget.org/packages/Disruptor/
+- **GitHub** (1.3K stars) 🔗 https://github.com/disruptor-net/Disruptor-net
+
+
+## 7. CliWrap - Running command-line processes
+
+
+
+CliWrap makes it easy to **run and manage external CLI processes in .NET**.
+
+- Fluent, task-based API for starting commands
+- Streams standard input/output and error in real time
+- Supports cancellation, timeouts, and piping between processes
+
+Ideal for automation, build tools, and integrating external executables.
+
+- **NuGet** (14.1M downloads) 🔗 https://www.nuget.org/packages/CliWrap
+- **GitHub** (4.7K stars) 🔗 https://github.com/Tyrrrz/CliWrap
+
+
+---
+
+
+## Hidden Libs from the Community
+
+### Sylvan.Csv & **Sep**
+
+- **Sylvan.Csv**: Up to *10× faster* and *100× less memory allocations* than `CsvHelper`, making CSV processing lightning-fast. ([Reddit](https://www.reddit.com/r/csharp/comments/191rwgt/extremely_highperformance_libraries_for_common/?utm_source=chatgpt.com))
+- **Sep**: Even faster than Sylvan, but trades off some flexibility. Great when performance matters more than API richness. ([Reddit](https://www.reddit.com/r/csharp/comments/191rwgt/extremely_highperformance_libraries_for_common/?utm_source=chatgpt.com))
+
+### String Parsing: **csFastFloat**
+
+- Parses `float` and `double` around *8–9× faster* than `.Parse` methods—perfect for high-volume parsing tasks. ([Reddit](https://www.reddit.com/r/csharp/comments/191rwgt/extremely_highperformance_libraries_for_common/?utm_source=chatgpt.com))
+
+### CySharp’s Suite: MemoryPack, MasterMemory, SimdLinq
+
+- **MemoryPack**: One of the fastest serializers available, with low allocations and high throughput. Ideal for Web APIs or microservices. ([Reddit](https://www.reddit.com/r/csharp/comments/191rwgt/extremely_highperformance_libraries_for_common/?utm_source=chatgpt.com))
+- **MasterMemory**: Designed for databases or config storage. Claims *4,700× faster than SQLite* with zero-allocations per query. ([Reddit](https://www.reddit.com/r/csharp/comments/191rwgt/extremely_highperformance_libraries_for_common/?utm_source=chatgpt.com))
+- **SimdLinq**: SIMD-accelerated LINQ operations supporting a broader set of methods than .NET's built-in SIMD. Works when slight floating-point differences are acceptable. ([Reddit](https://www.reddit.com/r/csharp/comments/191rwgt/extremely_highperformance_libraries_for_common/?utm_source=chatgpt.com))
+
+### Jil – JSON Deserializer
+
+- Ultra-fast JSON (de)serializer with low memory overhead, used in high-scale systems. ([Performance is a Feature!](https://www.mattwarren.org/2014/09/05/stack-overflow-performance-lessons-part-2/?utm_source=chatgpt.com))
+
+### StackExchange.NetGain – WebSocket Efficiency
+
+- High-performance WebSocket server library designed for low-latency IO scenarios. (Now mostly replaced by Kestrel's built-in support, but worth knowing.) ([GitHub](https://github.com/StackExchange/NetGain?utm_source=chatgpt.com))
+
+### Math Libraries: Math.NET Numerics & ILNumerics
+
+- **Math.NET Numerics**: Core numerical methods and matrix math, similar to BLAS/LAPACK. ([Wikipedia](https://en.wikipedia.org/wiki/Math.NET_Numerics?utm_source=chatgpt.com))
+- **ILNumerics**: Efficient numerical arrays with parallelized processing, loop unrolling and cache optimizations. Great for scientific computing. ([Wikipedia](https://en.wikipedia.org/wiki/ILNumerics?utm_source=chatgpt.com))
+
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/cliwrap.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/cliwrap.png
new file mode 100644
index 0000000000..718d1b558b
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/cliwrap.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/cover.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/cover.png
new file mode 100644
index 0000000000..a1b4c825e2
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/cover.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/wolverine-logo.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/wolverine-logo.png
new file mode 100644
index 0000000000..b14dc2b7ed
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/wolverine-logo.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/wolverine.png b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/wolverine.png
new file mode 100644
index 0000000000..5ef73f0149
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-High-Perf-DotNet-Libs/wolverine.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_1.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_1.png
new file mode 100644
index 0000000000..9889c8d813
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_1.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_2.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_2.png
new file mode 100644
index 0000000000..5e00300c81
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_2.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_3.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_3.png
new file mode 100644
index 0000000000..3675376cb3
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_3.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_4.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_4.png
new file mode 100644
index 0000000000..e0b94bb47c
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_4.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_5.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_5.png
new file mode 100644
index 0000000000..4ed8c4eabe
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_5.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_6.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_6.png
new file mode 100644
index 0000000000..ad2640da1f
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_6.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_7.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_7.png
new file mode 100644
index 0000000000..cfdf76ea7e
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_7.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_8.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_8.png
new file mode 100644
index 0000000000..f399892ee8
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_8.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_9.png b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_9.png
new file mode 100644
index 0000000000..171ff61851
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/images/img_9.png differ
diff --git a/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/post.md b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/post.md
new file mode 100644
index 0000000000..cfd4db30bf
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-11-Web-Design-Basics-for-Graphic-Designers-Who-Dont-Code/post.md
@@ -0,0 +1,282 @@
+# Web Design Basics for Graphic Designers Who Don't Code
+
+## Introduction
+
+As a **designer**, I have been working on **logos**, **posters**, and **social media announcement** **visuals** for years. However, when it comes to the web, I used to hold back saying “I **don’t know how to code**.” We have all thought about this at some point and unfortunately, we still think about it from time to time.
+
+🚀 **Good news**: We can learn **web design** without writing code and design **user-friendly**, **aesthetic, and functional web interfaces** using basic knowledge.
+
+In this article, we will talk about the **basics of web design**, its **differences from graphic design**, and whether it is possible to do **web design without knowing how to code**.
+
+## Differences Between Graphic Design & Web Design
+
+
+
+### What is Graphic Design?
+
+Graphic design is creating **visual content** that conveys a message to a **specific audience**. Graphic designers use various **visual elements** such as **color**, **typography**, **imagery**, and **layout** to communicate a message effectively. They work on a wide range of projects, including **logos**, **websites**, **packaging**, **advertisements, and branding**.
+
+### What is Web Design?
+
+Web design is the process of creating a website that can be viewed on computers or mobile devices. Like graphic design, web design also involves creating **graphics**, **typography**, **and visuals**, but they use the **internet** as the communication channel.
+
+### Graphic Design
+
+* Graphic Design is concerned with **visuals** and **appearance**.
+* Graphic design focuses on visually conveying specific messages or ideas through **typography**, **visuals**, **colors**, and i**llustrations**.
+* Graphic design focuses on how objects **look**.
+* Graphic designers **do not need coding knowledge**.
+* Graphic design is **static**.
+
+### Web Design
+
+* Web design is user experience–focused.
+* Web design aims to create **functional** and **user-friendly** **websites** that provide the **best experience** for users.
+* Web design considers **search engine optimization** when creating websites.
+* Web designers need to have **knowledge of HTML**, **CSS**, and other web development languages to create **functional and responsive designs**.
+* Web design is **dynamic**.
+
+## Fundamental Principles of Web Design (Applicable Without Coding)
+
+Companies and **brands** from almost every sector request the **creation of their own websites**. This way, they gain the opportunity to introduce their **services**, **prices**, and themselves to their **target audiences**. However, for this to have the desired effect, the website must be **designed properly**. What are the **fundamental principles** to pay attention to when designing a website? Now, it’s time to answer this question by introducing the basics. Here are the **indispensable principles in web design**.
+
+ ### 1\) User-Centered Designs:
+
+Users always value **ease and practicality** when receiving a service. For this reason, it is important for websites to be designed in a user-centered way. **Easy to find menus**, **fast usage**, and the **easy to locate any information** are very important. With **user centered design**, it is possible to create websites that are **easy to use** and also **satisfy users**.
+
+
+ ### 2\) Responsive Designs:
+
+It is very important for the website and its design to be **usable on every digital platform**. Therefore, the designed sites must have a **responsive design**. This means easy access to the site on a **phone**, **tablet**, or **computer**. This also ensures that users continue to prefer the site.
+
+ ### 3\) Visual Hierarchy:
+
+The page must have **visuals related to itself**, and **product content** should be matched with the **correct visuals**. It is also very important for visual elements to be placed according to their order of importance. On web pages, content compatible with visuals must be provided with **sufficient and accurate information**.
+
+ ### 4\) Color and Typography Selection:
+
+Color and typography selection is very important for handling visuals, colors, and text in a certain **harmony**. For the site to **attract attention** or for the relevant pages to achieve the expected interaction, the use of color and the chosen font style and font color must be harmonious. A design that is both **easy to read** and **eye catching** without causing any disturbance should be preferred.
+
+ ### 5\) Content and Layout Structure:
+
+One of the most desired features on web pages is **content organization**. Content that is **unrelated to the pages, creates confusion while reading**, or **lacks simplicity**, such as overly frequent paragraphs, incorrect fonts, and similar factors, causes web pages to have less impact. **Content structure** also includes **placing related topics sequentially** and **adding them to the menu**. For example, on a website created for shoes, if shoe types are grouped separately, users find it easier. Options like high heels, sandals, and sneakers help users find what they are looking for more easily, which in turn ensures positive site feedback.
+
+ ### 6\) Speed Optimization:
+
+As with every type of service, speed is very important for services provided through web pages. Easy navigation between pages, error-free performance, and ease of use are very important for users. No one wants to shop or use a service on a website that takes a long time to load, because everyone prefers websites to save time.
+
+ ### 7\) Consistency:
+
+For a service to be preferred, it must first be reliable. This is directly related to the information, visuals, and everything on the website. The information in the content, visuals, and content details must be consistent and should not raise any questions in visitors’ minds. Otherwise, negative feedback can later affect customer preferences and damage the brand image.
+
+## Is It Possible to Do Web Design Without Coding?
+
+In the past, it was not possible to create a website without at least some basic coding knowledge. However, today, almost anyone can build a website. Even if you have not written a **single line of code**.
+
+The biggest helpers for those who want to do **web development without coding** are **No-Code** and **Low-Code** platforms. These tools help users **design websites** without dealing with **technical details**.
+
+Systems like **Wix**, **Webflow**, **Shopify**, and **WordPress** are very common in this area.
+
+
+
+The web development process on these platforms is carried out through practical methods such as **drag-and-drop**, selecting **ready-made templates**, and filling out forms.
+
+### **No Code**
+
+As the name suggests, it allows you to create websites, mobile applications, automations, and workflows **without writing a single line of code**.
+
+* **How Does It Work**? They usually have a visual editor. You create the skeleton of your application by dragging and dropping ready “building blocks” such as buttons, forms, and visuals onto your canvas. Then, you determine what these elements will do (for example, “go to this page when this button is clicked”) by selecting options from the menus.
+* **Who Uses It**? It is perfect for entrepreneurs, marketers, product managers, designers, and anyone who wants to quickly test an idea.
+* **Examples**: Platforms like Webflow, Bubble, Adalo, and Glide allow you to create a wide range of products, from complex web applications to mobile apps.
+
+### **Low Code**
+
+Low-Code systems require a bit more **technical knowledge** but still **do not require learning full-scale programming**.
+
+* **How Does It Work**? You handle 80% of the work with drag-and-drop, and for the remaining 20% that requires customization, you add small code snippets.
+* **Who Uses It**? It is generally preferred by IT departments of corporate companies and technical teams that want to develop more complex, scalable applications.
+* **Examples**: Platforms like OutSystems and Mendix are used to build large, integrated systems that manage a company’s internal processes.
+
+## What Should the Web Design Process be Like?
+
+
+
+**Web design** is a passionate field but can be **overwhelming** at times. When starting out, coming up with a plan on how to tackle your website or a web app idea often feels daunting: Where should you begin?Web designers often think about the **web design process** with a focus on **technical matters** such as wireframes, code, and content management. But great
+
+design isn’t about how you integrate the social media buttons or even slick visuals. **Great design** is actually about having **a website creation process** that aligns with an **overarching strategy.**
+
+Doing all the thinking beforehand ensures that you don’t forget anything crucial. It also frees up headspace for doing the actual work, avoids overwhelm, improves efficiency, and allows you to build better websites on repeat.
+
+But how do you achieve that harmonious synthesis of elements? Through a **holistic web design** process that takes both **form and function** into account.
+
+We have already covered the fundamentals, now, I'll share the steps to an **effective web design process.**
+
+Let's get started.
+
+### 1\) Goal Identification
+
+In this **initial stage**, the designer needs to identify the end goal of the website design, usually in close collaboration with the client or other stakeholders. Questions to explore and answer in this stage of the design and website development process include:
+
+* Who is the site for?
+* What do they hope to find or do there?
+* Is the main purpose of this website to inform, to sell (e-commerce, for everyone?), or to entertain?
+* Does the website need to clearly convey the **brand's core message**, or is it part of a broader **brand strategy** with its own unique focus?
+* If there are any, which **competitor sites** exist, and how should this site be **inspired by them** / how should it differ from them?
+
+To have clear answers to above questions will lead to the **successful execution** of the project.
+
+### What Purpose Will the Website Serve?
+
+Whatever the project you’re taking on, you always want each and every initiative you take to achieve the goals you’ve set for it. **Goal setting is critical** because it will be key in making decisions throughout the project by asking yourself the right questions and **prioritizing tasks and efforts**.
+
+As basic as it may seem, following the **SMART framework** is always a great idea when setting your goals, to **ensure effectiveness:**
+
+**S \- SPECIFIC**
+Your goal is direct, detailed, and meaningful.
+
+**M \- MEASURABLE**
+Your goal is quantifiable to track progress or success.
+
+**A \- ATTAINABLE**
+Your goal is realistic and you have the tools and/or resources to attain it.
+
+**R \- RELEVANT**
+Your goal aligns with your company mission.
+
+**T \- TIME-BASED**
+Your goal has a deadline.
+
+### 2\) Scope Definition
+
+This is easier said than done when starting out, so it is best to approach it with caution : Everyone has once been guilty of saying a project “will be done by next week” before realizing they dramatically **underestimated** how hard it would be.
+
+Nevertheless, **setting** a timeline will help a lot with **accountability**, both internal and external, and will help **break down the project in distinct stages**.
+
+You don’t have to reinvent anything from scratch, as a lot of tools such as Airtable’s timeline view will help you put the timeline together.
+
+
+
+Source: [Airtable](https://blog.airtable.com/introducing-airtables-new-timeline-view/)
+
+### 3\) Sitemap and Wireframe Creation
+
+The site map forms the foundation of a well-designed website. It gives web designers a clear idea of the **information architecture** of the website and explains the **relationships** between various **pages and content elements**.
+
+
+
+Building a web site without a site map is like building a house without a plan. And it rarely ends well.
+
+Time to start building the first iteration of your project\! To put it shortly, **wireframes** serve as a blueprint, a visual guide representing the skeletal framework of a website or application. It will be a raw version of your project, a great way to get your **initial idea down** in its first “physical” form.
+
+
+
+Source: [Afolayan Daniel](https://medium.com/fbdevclagos/4-reasons-why-wire-frame-is-important-during-website-or-mobile-app-development-46fabdf47190)
+
+While it won’t be functional yet, it’ll be a major web design step to share with your team, potential leads or even investors, and will highlight issues that you might not have thought about previously. Wireframes are a great opportunity to move fast, once they’re ready, you’ll be able to:
+
+* Gather early feedback;
+* Run UX testing groups;
+* Iterate on your timeline if necessary;
+* Get concept validation.
+
+There are different ways to create wireframes. You can of course sketch them out on paper to start with, but creating a digital version will eventually be much more practical to share them.
+
+#### Tools for sitemapping and wireframing;
+
+* Pen/pencil and paper.
+* Balsamiq.
+* Moqups.
+* Sketch.
+* Axure.
+* Webflow.
+* Slickplan.
+* Writemaps.
+* Mindnode.
+* Figma.
+* Sketch.
+
+### 4\) Content Creation
+A website should offer more than just a simple design and attractive graphics. An effective content strategy is essential to capture users’ interest and to make the site stand out in search engines.
+
+
+When it comes to content, search engine optimization is only
+half of the battle.
+
+There are two main goals that you need to focus on while creating content.
+
+#### **Goal 1 Content encourages engagement and action:**
+
+First of all, content drives readers to take action and encourages them to perform the actions necessary to achieve a site's goals. This is influenced both by the content itself (writing) and by the way it is presented (typography and structural elements).
+
+Boring, lifeless, and lengthy writing rarely holds visitors' attention for long enough. Short, fluent, and engaging content captures them and makes them click through to other pages. Even if your pages need a lot of content (which they often do), properly "breaking it up" into short paragraphs supported by visuals can help create a light and engaging feel.
+
+#### **Goal 2 Search Engine Optimization**:
+
+Content also increases a site's visibility in the eyes of search engines. The practice of creating and developing content to achieve a good ranking in search results is called search engine optimization or SEO.
+
+Identifying your keywords and key phrases correctly is very important for the success of any website.
+
+### 5\) Visual Elements
+
+
+
+Style Tile: a free style tile / moodboard template built by Mat Vogels.
+
+It is time to create the **visual style** of the site. This part of the design process is usually shaped by **existing brand elements, color choices**, and **logos** specified by the client. However, it is also the stage of the web design process where a **good web designer can truly shine**.
+
+**Visuals play a more important** **role** in web design than ever before. High quality visuals not only give a website a professional look and feel, but also convey a message, are mobile friendly, and help build trust.
+
+**Visual design is a way of communicating** with the web site users to make the site as **appealing to them** as possible. When done right, it can determine the site’s being one of the major successes amongst competitors. On the other hand, any mistake might put it in risk of becoming just another ordinary web site.
+
+**Tools for visual elements**:
+
+* (Sketch, Illustrator, Photoshop, Figma, vb.)
+* Visual Style Guides.
+
+
+
+### 6\) Development & Platforms
+
+**Front-End Development**: The parts that users interact with (HTML, CSS, JavaScript).
+
+**Back-End Developmen**t: Database and server-side processes (PHP, Python, Node.js).
+
+**No-Code Platforms**: Publishing on platforms like Webflow, Bubble, Adalo, Glide.
+
+### 7\) Testing
+
+When your site has all the visuals and content, you are ready to test.
+Once the **first iteration** of your website/web app is ready, it’s time for some **testing** to make sure it **runs smoothly**.
+
+A website should undergo a detailed testing process before going live.
+Items to check during the testing process:
+
+* Mobile Compatibility.
+* Functionality across different browsers.
+* Functionality of forms and buttons.
+
+Alongside these steps, setting up website uptime monitoring is essential to ensure the site remains functional after launch, providing immediate alerts if any downtime occurs. Ultimately, while testing is an important part of the web design process, it’s not worth losing sleep over. **Done is always better than perfect** and when in doubt, keep this quote in mind.
+
+*“If you are not embarrassed by the first version of your product, you've launched too late.” \- Reid Hoffman, founder of LinkedIn*
+
+### 8\) Website Launch
+
+Now it’s time for everyone’s favorite part of the website design process: When everything has been thoroughly tested and you’re happy with the site, you can start.
+
+Don’t expect this to go perfectly. There may still be some elements that need fixing. Web design is a fluid and ongoing process that requires constant maintenance.
+
+Web design and design in general is about finding the right balance between form and function. You need to use the right fonts, colors, and design motifs. But the way users navigate and experience your site is just as important.
+
+## Conclusion
+
+Previously, when we wanted to turn our designs into reality, the barrier of learning and using a programming language tool stood in our way. This barrier has now been removed thanks to **No-Code tools**. With these tools, even without coding knowledge, there is now a way to bring your designs to life.
+
+## Resources
+
+* Bulut, B. (2025, July 20). *Kod yazmayı bilmeden yazılımcı olmak nasıl mümkün oldu?* Webtekno. [https://www.webtekno.com/kod-bilmeden-yazilimci-olmak-nasil-mumkun-oldu-h159799.html](https://www.webtekno.com/kod-bilmeden-yazilimci-olmak-nasil-mumkun-oldu-h159799.html)
+
+* Ectasarim. (2024, Kasım 10). *Web tasarım ilkeleri nelerdir? Önemli hususlar*. [https://www.ectasarim.com/web-tasarim-ilkeleri/](https://www.ectasarim.com/web-tasarim-ilkeleri/?utm_source=chatgpt.com)
+
+* Meazey, M. (2020, February 12). *The web design process in 7 simple steps*. *Webflow Blog*. [https://webflow.com/blog/the-web-design-process-in-7-simple-steps](https://webflow.com/blog/the-web-design-process-in-7-simple-steps)
+
+* University of California Office of the President. (2016). *How to write SMART goals: A how-to guide.* University of California. [https://www.ucop.edu/local-human-resources/\_files/performance-appraisal/How+to+write+SMART+Goals+v2.pdf](https://www.ucop.edu/local-human-resources/_files/performance-appraisal/How+to+write+SMART+Goals+v2.pdf)
diff --git a/docs/en/Community-Articles/2025-09-11-aws-secrets-manager-in-abp-framework/article.md b/docs/en/Community-Articles/2025-09-11-aws-secrets-manager-in-abp-framework/article.md
new file mode 100644
index 0000000000..bcd96834b8
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-11-aws-secrets-manager-in-abp-framework/article.md
@@ -0,0 +1,803 @@
+# Step-by-Step AWS Secrets Manager Integration in ABP Framework Projects
+
+## Introduction
+In this article, we are going to discuss how to secure sensitive data in ABP Framework projects using AWS Secrets Manager and explain various aspects and concepts of _secret_ data management. We will explain step-by-step AWS Secrets Manager integration.
+
+
+## What is the Problem?
+Modern applications must store sensitive data such as API keys, database connection strings, OAuth client credentials, and other similar sensitive data. These are at the center of functionality but if stored in the wrong place can be massive security issues.
+
+At build time, the first place that comes to mind is usually **appsettings.json**. This is a configuration file; it is not a secure place to store secret information, especially in production.
+
+### Common Security Risks:
+- **Plain text storage**: Plain text storage of passwords
+- **Exposure to version control**: Secrets are rendered encrypted in Git repositories
+- **No access control**: Anyone who has file access can see the secrets
+- **No rotation**: We must change them manually
+- **No audit trail**: Who accessed which secret when is not known
+
+## .NET User Secrets Tool vs AWS Secrets Manager
+
+**User Secrets (.NET Secret Manager Tools)** is a dev environment only, local file-based solution that keeps sensitive information out of the repository.
+
+**AWS Secrets Manager** is production. It's a centralized, encrypted, and audited secret management service.
+
+| Feature | User Secrets (Dev) | AWS Secrets Manager (Prod) |
+| ---------------------- | ---------------------------- | ------------------------------ |
+| Scope | Local developer machine | All environments (dev/stage/prod) |
+| Storage | JSON in user profile | Managed service (centralized) |
+| Encryption | None (plain text file) | Encrypted with KMS |
+| Access Control | OS file permissions | IAM policies |
+| Rotation | None | Yes (automatic) |
+| Audit / Traceability | None | Yes (CloudTrail) |
+| Typical Usage | Quick dev outside repo | Production secret management |
+
+---
+
+## AWS Secrets Manager
+Especially designed to securely store and handle sensitive and confidential data for our applications. It even supports features such as secret rotation, replication, and many more.
+
+AWS Secrets Manager offers a trial of 30 days. After that, there is a $0.40 USD/month charge per stored secret. There is also a $0.05 USD fee per 10,000 API requests.
+
+### Key Features:
+- **Automatic encryption**: KMS automatic encryption
+- **Automatic rotation**: Scheduled secret rotation
+- **Fine-grained access control**: IAM fine-grained access control
+- **Audit logging**: Full audit logging with CloudTrail
+- **Cross-region replication**: Cross-region replication
+- **API integration**: Programmatic access support
+
+---
+
+## Step 1: AWS Secrets Manager Setup
+
+### 1.1 Creating a Secret in AWS Console
+First, search for the Secrets Manager service in the AWS Management Console.
+
+1. **AWS Console** → **Secrets Manager** → **Store a new secret**
+2. Select **Secret type**:
+ - **Other type of secret** (For custom key-value pairs)
+ - **Credentials for RDS database** (For databases)
+ - **Credentials for DocumentDB database**
+ - **Credentials for Redshift cluster**
+
+
+
+3. Enter **Secret value**:
+```json
+{
+ "ConnectionString": "Server=myserver;Database=mydb;User Id=myuser;Password=mypassword;"
+}
+```
+
+4. Set **Secret name**: `prod/ABPAWSTest/ConnectionString`
+5. Add **Description**: "ABP Framework connection string for production"
+6. Choose **Encryption key** (default KMS key is sufficient)
+7. Configure **Automatic rotation** settings (optional)
+
+### 1.2 IAM Permissions
+Create an IAM policy for secret access:
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "secretsmanager:GetSecretValue",
+ "secretsmanager:DescribeSecret"
+ ],
+ "Resource": "arn:aws:secretsmanager:eu-north-1:588118819172:secret:prod/ABPAWSTest/ConnectionString-*"
+ }
+ ]
+}
+```
+
+---
+
+## Step 2: ABP Framework Project Setup
+
+### 2.1 NuGet Packages
+Add the required AWS packages to your project:
+
+```bash
+dotnet add package AWSSDK.SecretsManager
+dotnet add package AWSSDK.Extensions.NETCore.Setup
+```
+
+### 2.2 Configuration Files
+
+**appsettings.json** (Development):
+```json
+{
+ "AWS": {
+ "Profile": "default",
+ "Region": "eu-north-1",
+ "AccessKey": "YOUR_ACCESS_KEY",
+ "SecretKey": "YOUR_SECRET_KEY"
+ },
+ "SecretsManager": {
+ "SecretName": "prod/ABPAWSTest/ConnectionString",
+ "SecretArn": "arn:aws:secretsmanager:eu-north-1:588118819172:secret:prod/ABPAWSTest/ConnectionString-xtYQxv"
+ }
+}
+```
+
+**appsettings.Production.json** (Production):
+```json
+{
+ "AWS": {
+ "Region": "eu-north-1"
+ // Use environment variables or IAM roles in production
+ },
+ "SecretsManager": {
+ "SecretName": "prod/ABPAWSTest/ConnectionString"
+ }
+}
+```
+
+### 2.3 Environment Variables (Production)
+```bash
+export AWS_ACCESS_KEY_ID=your_access_key
+export AWS_SECRET_ACCESS_KEY=your_secret_key
+export AWS_DEFAULT_REGION=eu-north-1
+```
+
+---
+
+## Step 3: AWS Integration Implementation
+
+### 3.1 Program.cs Configuration
+
+```csharp
+using Amazon;
+using Amazon.SecretsManager;
+
+public class Program
+{
+ public async static Task Main(string[] args)
+ {
+ var builder = WebApplication.CreateBuilder(args);
+
+ // AWS Secrets Manager configuration
+ var awsOptions = builder.Configuration.GetAWSOptions();
+
+ // Read AWS credentials from appsettings
+ var accessKey = builder.Configuration["AWS:AccessKey"];
+ var secretKey = builder.Configuration["AWS:SecretKey"];
+ var region = builder.Configuration["AWS:Region"];
+
+ if (!string.IsNullOrEmpty(accessKey) && !string.IsNullOrEmpty(secretKey))
+ {
+ awsOptions.Credentials = new Amazon.Runtime.BasicAWSCredentials(accessKey, secretKey);
+ }
+
+ if (!string.IsNullOrEmpty(region))
+ {
+ awsOptions.Region = RegionEndpoint.GetBySystemName(region);
+ }
+
+ builder.Services.AddDefaultAWSOptions(awsOptions);
+ builder.Services.AddAWSService();
+
+ // ... ABP configuration
+ await builder.AddApplicationAsync();
+ var app = builder.Build();
+
+ await app.InitializeApplicationAsync();
+ await app.RunAsync();
+ }
+}
+```
+
+### 3.2 Secrets Manager Service
+
+**Interface:**
+```csharp
+public interface ISecretsManagerService
+{
+ Task GetSecretAsync(string secretName);
+ Task GetSecretAsync(string secretName) where T : class;
+ Task GetConnectionStringAsync();
+}
+```
+
+**Implementation:**
+```csharp
+using Amazon.SecretsManager;
+using Amazon.SecretsManager.Model;
+using Volo.Abp.DependencyInjection;
+using System.Text.Json;
+
+public class SecretsManagerService : ISecretsManagerService, IScopedDependency
+{
+ private readonly IAmazonSecretsManager _secretsManager;
+ private readonly IConfiguration _configuration;
+ private readonly ILogger _logger;
+
+ public SecretsManagerService(
+ IAmazonSecretsManager secretsManager,
+ IConfiguration configuration,
+ ILogger logger)
+ {
+ _secretsManager = secretsManager;
+ _configuration = configuration;
+ _logger = logger;
+ }
+
+ public async Task GetSecretAsync(string secretName)
+ {
+ try
+ {
+ var request = new GetSecretValueRequest
+ {
+ SecretId = secretName
+ };
+
+ var response = await _secretsManager.GetSecretValueAsync(request);
+
+ _logger.LogInformation("Successfully retrieved secret: {SecretName}", secretName);
+
+ return response.SecretString;
+ }
+ catch (Exception ex)
+ {
+ _logger.LogError(ex, "Failed to retrieve secret: {SecretName}", secretName);
+ throw;
+ }
+ }
+
+ public async Task GetSecretAsync(string secretName) where T : class
+ {
+ var secretValue = await GetSecretAsync(secretName);
+
+ try
+ {
+ return JsonSerializer.Deserialize(secretValue)
+ ?? throw new InvalidOperationException($"Failed to deserialize secret {secretName}");
+ }
+ catch (JsonException ex)
+ {
+ _logger.LogError(ex, "Failed to deserialize secret {SecretName}", secretName);
+ throw;
+ }
+ }
+
+ public async Task GetConnectionStringAsync()
+ {
+ var secretName = _configuration["SecretsManager:SecretName"]
+ ?? throw new InvalidOperationException("SecretsManager:SecretName configuration is missing");
+
+ return await GetSecretAsync(secretName);
+ }
+}
+```
+
+---
+
+## Step 4: Usage Examples
+
+### 4.1 Using in Application Service
+
+```csharp
+[RemoteService(false)]
+public class DatabaseService : ApplicationService
+{
+ private readonly ISecretsManagerService _secretsManager;
+
+ public DatabaseService(ISecretsManagerService secretsManager)
+ {
+ _secretsManager = secretsManager;
+ }
+
+ public async Task GetDatabaseConnectionAsync()
+ {
+ // Get connection string from AWS Secrets Manager
+ var connectionString = await _secretsManager.GetConnectionStringAsync();
+
+ // Use the connection string
+ return connectionString;
+ }
+
+ public async Task GetApiConfigAsync()
+ {
+ // Deserialize JSON secret
+ var config = await _secretsManager.GetSecretAsync("prod/MyApp/ApiConfig");
+
+ return config;
+ }
+}
+```
+
+### 4.2 DbContext Configuration
+
+```csharp
+public class YourDbContextConfigurer
+{
+ public static void Configure(DbContextOptionsBuilder builder, string connectionString)
+ {
+ builder.UseSqlServer(connectionString);
+ }
+
+ public static void Configure(DbContextOptionsBuilder builder, DbConnection connection)
+ {
+ builder.UseSqlServer(connection);
+ }
+}
+
+// Usage in Module
+public override void ConfigureServices(ServiceConfigurationContext context)
+{
+ var configuration = context.Services.GetConfiguration();
+ var secretsManager = context.Services.GetRequiredService();
+
+ // Get secret at startup and pass to DbContext
+ var connectionString = await secretsManager.GetConnectionStringAsync();
+
+ context.Services.AddAbpDbContext(options =>
+ {
+ options.AddDefaultRepositories(includeAllEntities: true);
+ options.DbContextOptions.UseSqlServer(connectionString);
+ });
+}
+```
+
+---
+
+## Step 5: Best Practices & Security
+
+### 5.1 Security Best Practices
+
+1. **Environment-based Configuration:**
+ - Development: appsettings.json
+ - Production: Environment variables or IAM roles
+
+2. **Principle of Least Privilege:**
+ ```json
+ {
+ "Effect": "Allow",
+ "Action": "secretsmanager:GetSecretValue",
+ "Resource": "arn:aws:secretsmanager:region:account:secret:specific-secret-*"
+ }
+ ```
+
+3. **Secret Rotation:**
+ - Set up automatic rotation
+ - Custom rotation logic with Lambda functions
+
+4. **Caching Strategy:**
+ ```csharp
+ public class CachedSecretsManagerService : ISecretsManagerService
+ {
+ private readonly IMemoryCache _cache;
+ private readonly SecretsManagerService _secretsManager;
+
+ public async Task GetSecretAsync(string secretName)
+ {
+ var cacheKey = $"secret:{secretName}";
+
+ if (_cache.TryGetValue(cacheKey, out string cachedValue))
+ {
+ return cachedValue;
+ }
+
+ var value = await _secretsManager.GetSecretAsync(secretName);
+
+ _cache.Set(cacheKey, value, TimeSpan.FromMinutes(30));
+
+ return value;
+ }
+ }
+ ```
+
+### 5.2 Error Handling
+
+```csharp
+public async Task GetSecretWithRetryAsync(string secretName)
+{
+ const int maxRetries = 3;
+ var delay = TimeSpan.FromSeconds(1);
+
+ for (int i = 0; i < maxRetries; i++)
+ {
+ try
+ {
+ return await GetSecretAsync(secretName);
+ }
+ catch (AmazonSecretsManagerException ex) when (i < maxRetries - 1)
+ {
+ _logger.LogWarning(ex, "Retry {Attempt} for secret {SecretName}", i + 1, secretName);
+ await Task.Delay(delay);
+ delay = TimeSpan.FromMilliseconds(delay.TotalMilliseconds * 2); // Exponential backoff
+ }
+ }
+
+ throw new InvalidOperationException($"Failed to retrieve secret {secretName} after {maxRetries} attempts");
+}
+```
+
+### 5.3 Performance Optimization
+
+```csharp
+public class PerformantSecretsManagerService : ISecretsManagerService
+{
+ private readonly IAmazonSecretsManager _secretsManager;
+ private readonly IMemoryCache _cache;
+ private readonly ILogger _logger;
+ private readonly SemaphoreSlim _semaphore = new(1, 1);
+
+ public async Task GetSecretAsync(string secretName)
+ {
+ var cacheKey = $"secret:{secretName}";
+
+ // Try to get from cache first
+ if (_cache.TryGetValue(cacheKey, out string cachedValue))
+ {
+ return cachedValue;
+ }
+
+ // Use semaphore to prevent multiple concurrent requests for the same secret
+ await _semaphore.WaitAsync();
+ try
+ {
+ // Double-check pattern
+ if (_cache.TryGetValue(cacheKey, out cachedValue))
+ {
+ return cachedValue;
+ }
+
+ // Fetch from AWS
+ var value = await GetSecretFromAwsAsync(secretName);
+
+ // Cache for 30 minutes
+ _cache.Set(cacheKey, value, TimeSpan.FromMinutes(30));
+
+ return value;
+ }
+ finally
+ {
+ _semaphore.Release();
+ }
+ }
+}
+```
+
+---
+
+## Step 6: Testing & Debugging
+
+### 6.1 Unit Testing
+
+```csharp
+public class SecretsManagerServiceTests : AbpIntegratedTest
+{
+ private readonly ISecretsManagerService _secretsManager;
+
+ public SecretsManagerServiceTests()
+ {
+ _secretsManager = GetRequiredService();
+ }
+
+ [Fact]
+ public async Task Should_Get_Connection_String()
+ {
+ // Act
+ var connectionString = await _secretsManager.GetConnectionStringAsync();
+
+ // Assert
+ connectionString.ShouldNotBeNullOrEmpty();
+ connectionString.ShouldContain("Server=");
+ }
+
+ [Fact]
+ public async Task Should_Deserialize_Json_Secret()
+ {
+ // Arrange
+ var secretName = "test/json/config";
+
+ // Act
+ var config = await _secretsManager.GetSecretAsync(secretName);
+
+ // Assert
+ config.ShouldNotBeNull();
+ config.ApiKey.ShouldNotBeNullOrEmpty();
+ }
+}
+```
+
+### 6.2 Mock Implementation for Testing
+
+```csharp
+public class MockSecretsManagerService : ISecretsManagerService, ISingletonDependency
+{
+ private readonly Dictionary _secrets = new()
+ {
+ ["prod/ABPAWSTest/ConnectionString"] = "Server=localhost;Database=TestDb;Trusted_Connection=true;",
+ ["prod/MyApp/ApiKey"] = "test-api-key",
+ ["prod/MyApp/Config"] = """{"ApiUrl": "https://api.test.com", "Timeout": 30}"""
+ };
+
+ public Task GetSecretAsync(string secretName)
+ {
+ if (_secrets.TryGetValue(secretName, out var secret))
+ {
+ return Task.FromResult(secret);
+ }
+
+ throw new ArgumentException($"Unknown secret: {secretName}");
+ }
+
+ public async Task GetSecretAsync(string secretName) where T : class
+ {
+ var json = await GetSecretAsync(secretName);
+ return JsonSerializer.Deserialize(json)
+ ?? throw new InvalidOperationException($"Failed to deserialize {secretName}");
+ }
+
+ public Task GetConnectionStringAsync()
+ {
+ return GetSecretAsync("prod/ABPAWSTest/ConnectionString");
+ }
+}
+```
+
+### 6.3 Integration Testing
+
+```csharp
+public class SecretsManagerIntegrationTests : IClassFixture>
+{
+ private readonly WebApplicationFactory _factory;
+ private readonly HttpClient _client;
+
+ public SecretsManagerIntegrationTests(WebApplicationFactory factory)
+ {
+ _factory = factory;
+ _client = _factory.CreateClient();
+ }
+
+ [Fact]
+ public async Task Should_Connect_To_Database_With_Secret()
+ {
+ // Arrange & Act
+ var response = await _client.GetAsync("/api/health");
+
+ // Assert
+ response.EnsureSuccessStatusCode();
+ }
+}
+```
+
+---
+
+## Step 7: Monitoring & Observability
+
+### 7.1 CloudWatch Metrics
+
+```csharp
+public class MonitoredSecretsManagerService : ISecretsManagerService
+{
+ private readonly ISecretsManagerService _inner;
+ private readonly IMetrics _metrics;
+ private readonly ILogger _logger;
+
+ public async Task GetSecretAsync(string secretName)
+ {
+ using var activity = Activity.StartActivity("SecretsManager.GetSecret");
+ activity?.SetTag("secret.name", secretName);
+
+ var stopwatch = Stopwatch.StartNew();
+
+ try
+ {
+ var result = await _inner.GetSecretAsync(secretName);
+
+ _metrics.Counter("secrets_manager.requests")
+ .WithTag("secret_name", secretName)
+ .WithTag("status", "success")
+ .Increment();
+
+ _metrics.Timer("secrets_manager.duration")
+ .WithTag("secret_name", secretName)
+ .Record(stopwatch.ElapsedMilliseconds);
+
+ return result;
+ }
+ catch (Exception ex)
+ {
+ _metrics.Counter("secrets_manager.requests")
+ .WithTag("secret_name", secretName)
+ .WithTag("status", "error")
+ .WithTag("error_type", ex.GetType().Name)
+ .Increment();
+
+ _logger.LogError(ex, "Failed to retrieve secret {SecretName}", secretName);
+ throw;
+ }
+ }
+}
+```
+
+### 7.2 Health Checks
+
+```csharp
+public class SecretsManagerHealthCheck : IHealthCheck
+{
+ private readonly IAmazonSecretsManager _secretsManager;
+ private readonly ILogger _logger;
+
+ public SecretsManagerHealthCheck(
+ IAmazonSecretsManager secretsManager,
+ ILogger logger)
+ {
+ _secretsManager = secretsManager;
+ _logger = logger;
+ }
+
+ public async Task CheckHealthAsync(
+ HealthCheckContext context,
+ CancellationToken cancellationToken = default)
+ {
+ try
+ {
+ // Try to list secrets to verify connection
+ var request = new ListSecretsRequest { MaxResults = 1 };
+ await _secretsManager.ListSecretsAsync(request, cancellationToken);
+
+ return HealthCheckResult.Healthy("AWS Secrets Manager is accessible");
+ }
+ catch (Exception ex)
+ {
+ _logger.LogError(ex, "AWS Secrets Manager health check failed");
+ return HealthCheckResult.Unhealthy("AWS Secrets Manager is not accessible", ex);
+ }
+ }
+}
+
+// Register in Program.cs
+builder.Services.AddHealthChecks()
+ .AddCheck("secrets-manager");
+```
+
+---
+
+## Step 8: Advanced Scenarios
+
+### 8.1 Dynamic Configuration Reload
+
+```csharp
+public class DynamicSecretsConfigurationProvider : ConfigurationProvider, IDisposable
+{
+ private readonly ISecretsManagerService _secretsManager;
+ private readonly Timer _reloadTimer;
+ private readonly string _secretName;
+
+ public DynamicSecretsConfigurationProvider(
+ ISecretsManagerService secretsManager,
+ string secretName)
+ {
+ _secretsManager = secretsManager;
+ _secretName = secretName;
+
+ // Reload every 5 minutes
+ _reloadTimer = new Timer(ReloadSecrets, null, TimeSpan.Zero, TimeSpan.FromMinutes(5));
+ }
+
+ private async void ReloadSecrets(object state)
+ {
+ try
+ {
+ var secretValue = await _secretsManager.GetSecretAsync(_secretName);
+ var config = JsonSerializer.Deserialize>(secretValue);
+
+ Data.Clear();
+ foreach (var kvp in config)
+ {
+ Data[kvp.Key] = kvp.Value;
+ }
+
+ OnReload();
+ }
+ catch (Exception ex)
+ {
+ // Log error but don't throw to avoid crashing the timer
+ Console.WriteLine($"Failed to reload secrets: {ex.Message}");
+ }
+ }
+
+ public void Dispose()
+ {
+ _reloadTimer?.Dispose();
+ }
+}
+```
+
+### 8.2 Multi-Region Failover
+
+```csharp
+public class MultiRegionSecretsManagerService : ISecretsManagerService
+{
+ private readonly List _clients;
+ private readonly ILogger _logger;
+
+ public MultiRegionSecretsManagerService(
+ IConfiguration configuration,
+ ILogger logger)
+ {
+ _logger = logger;
+ _clients = new List();
+
+ // Create clients for multiple regions
+ var regions = new[] { "us-east-1", "us-west-2", "eu-west-1" };
+ foreach (var region in regions)
+ {
+ var config = new AmazonSecretsManagerConfig
+ {
+ RegionEndpoint = RegionEndpoint.GetBySystemName(region)
+ };
+ _clients.Add(new AmazonSecretsManagerClient(config));
+ }
+ }
+
+ public async Task GetSecretAsync(string secretName)
+ {
+ Exception lastException = null;
+
+ foreach (var client in _clients)
+ {
+ try
+ {
+ var request = new GetSecretValueRequest { SecretId = secretName };
+ var response = await client.GetSecretValueAsync(request);
+
+ _logger.LogInformation("Retrieved secret from region {Region}",
+ client.Config.RegionEndpoint.SystemName);
+
+ return response.SecretString;
+ }
+ catch (Exception ex)
+ {
+ lastException = ex;
+ _logger.LogWarning(ex, "Failed to retrieve secret from region {Region}",
+ client.Config.RegionEndpoint.SystemName);
+ }
+ }
+
+ throw new InvalidOperationException(
+ "Failed to retrieve secret from all regions", lastException);
+ }
+}
+```
+
+---
+
+## Conclusion
+
+AWS Secrets Manager integration with ABP Framework significantly enhances the security of your applications. With this integration:
+
+ **Centralized Secret Management**: All secrets are managed centrally
+ **Better Security**: Encryption through KMS and access control through IAM
+ **Audit Trail**: Complete recording of who accessed which secret when
+ **Automatic Rotation**: Secrets can be rotated automatically
+ **High Availability**: AWS high availability guarantee
+**Easy Integration**: Native integration with ABP Framework
+**Cost Effective**: Pay only for what you use
+**Scalable**: Scales with your application needs
+
+With this post, you can securely utilize AWS Secrets Manager in your ABP Framework applications and bid farewell to secret management concerns in production.
+
+### Key Benefits:
+- **Developer Productivity**: No hardcoded secrets in config files
+- **Operational Excellence**: Automation of rotation and monitoring
+- **Security Compliance**: Meet enterprise security requirements
+- **Peace of Mind**: Professional-grade secret management
+
+---
+
+## Additional Resources
+
+- [AWS Secrets Manager Documentation](https://docs.aws.amazon.com/secretsmanager/)
+- [ABP Framework Documentation](https://docs.abp.io/)
+- [AWS SDK for .NET](https://docs.aws.amazon.com/sdk-for-net/)
+- [AWS Security Best Practices](https://aws.amazon.com/architecture/security-identity-compliance/)
+- [Sample Project Repository](https://github.com/fahrigedik/AWSIntegrationABP)
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-09-11-aws-secrets-manager-in-abp-framework/cover.png b/docs/en/Community-Articles/2025-09-11-aws-secrets-manager-in-abp-framework/cover.png
new file mode 100644
index 0000000000..ac2b5557a5
Binary files /dev/null and b/docs/en/Community-Articles/2025-09-11-aws-secrets-manager-in-abp-framework/cover.png differ
diff --git a/docs/en/Community-Articles/2025-09-12-Demystified-Aggregates-in-DDD-&-.NET/post.md b/docs/en/Community-Articles/2025-09-12-Demystified-Aggregates-in-DDD-&-.NET/post.md
new file mode 100644
index 0000000000..a06eecb3d8
--- /dev/null
+++ b/docs/en/Community-Articles/2025-09-12-Demystified-Aggregates-in-DDD-&-.NET/post.md
@@ -0,0 +1,316 @@
+
+# Demystified Aggregates in DDD & .NET: From Theory to Practice
+
+## Introduction
+
+Domain-Driven Design (DDD) is one of the key foundations of modern software architecture and has taken a strong place in the .NET world. At the center of DDD are Aggregates, which protect the consistency of business rules. While they are one of DDD’s biggest strengths, they’re also one of the most commonly misunderstood ideas. Trying to follow “pure” DDD rules to the letter often clashes with the complexity and performance needs of real-world projects, leaving developers in tough situations. The goal of this article is to take a fresh, practical look at Aggregates and show how they can be applied in a way that works in real life.
+
+----------
+
+### **Chapter 1: Laying the Groundwork: What Is a Classic Aggregate?**
+
+Before jumping into pragmatic shortcuts, let’s make sure we’re all on the same page. To do that, we’ll start with the classic “by the book” definition of an Aggregate and the rules that make it tick.
+
+#### **What Exactly Is an Aggregate?**
+
+At its simplest, an **Aggregate** is a group of related objects (Entities and Value Objects) that are treated as **one unit of change**. And this group has a leader: the **Aggregate Root**.
+
+- **Aggregate Root** → Think of it as the gatekeeper. All outside commands (like “add a product to the order”) must go through the root. You can’t just poke around and change stuff inside.
+
+- **Entity** → Objects within the Aggregate that have their own identity (ID). Example: an `OrderLine` inside an `Order`.
+
+- **Value Object** → Objects without an identity. They’re defined entirely by their values, like an `Address` or `Money`.
+
+
+The Aggregate’s main purpose isn’t just grouping things together—it’s about **protecting business rules (invariants).** For example: _“an order’s total amount can never be negative.”_ The Aggregate Root makes sure rules like this are never broken.
+
+
+#### **The Role of Aggregates: Transaction Boundaries**
+
+The most important job of an Aggregate is defining the **transactional consistency boundary**. In other words:
+
+👉 Any change you make inside an Aggregate either **fully succeeds** or **fully fails**. There’s no half-done state.
+
+From a database perspective, when you call `SaveChanges()` or `Commit()`, everything within one Aggregate gets saved in a single transaction. If you add a product and update the total price, those two actions are atomic—they succeed together. Thanks to Aggregates, you’ll never end up in weird states like _“product was added but total wasn’t updated.”_
+
+
+#### **The Golden Rules of Aggregates**
+
+Classic DDD lays out three golden rules for working with Aggregates:
+
+1. **Talk Only to the Root**
+ You can’t directly update something like an `OrderLine`. You must go through the root: `Order.AddOrderLine(...)` or `Order.RemoveOrderLine(...)`. That way, the root always enforces the rules.
+
+2. **Reference Other Aggregates by ID Only**
+ An `Order` shouldn’t hold a `Customer` object directly. Instead, it should just store `CustomerId`. This keeps Aggregates independent and avoids loading massive object graphs.
+
+3. **Change Only One Aggregate per Transaction**
+ Need to create an order _and_ update loyalty points? Classic DDD says: do it in two steps. First, save the `Order`. Then publish a **domain event** to update the `Customer`. This enables scalability but introduces **eventual consistency**.
+
+
+
+#### **A Classic Example: The Order Aggregate in .NET**
+
+Here’s a simple example showing an `Order` Aggregate that enforces a business rule:
+
+```csharp
+// Aggregate Root: The entry point and rule enforcer
+public class Order
+{
+ public Guid Id { get; private set; }
+ public Guid CustomerId { get; private set; }
+
+ private readonly List _orderLines = new();
+ public IReadOnlyCollection OrderLines => _orderLines.AsReadOnly();
+
+ public decimal TotalPrice { get; private set; }
+
+ public Order(Guid id, Guid customerId)
+ {
+ Id = id;
+ CustomerId = customerId;
+ }
+
+ public void AddOrderLine(Guid productId, int quantity, decimal price)
+ {
+ // Rule 1: Max 10 order lines
+ if (_orderLines.Count >= 10)
+ throw new InvalidOperationException("An order can contain at most 10 products.");
+
+ // Rule 2: No duplicate products
+ var existingLine = _orderLines.FirstOrDefault(ol => ol.ProductId == productId);
+ if (existingLine != null)
+ throw new InvalidOperationException("This product is already in the order.");
+
+ var orderLine = new OrderLine(productId, quantity, price);
+ _orderLines.Add(orderLine);
+
+ RecalculateTotalPrice();
+ }
+
+ private void RecalculateTotalPrice()
+ {
+ TotalPrice = _orderLines.Sum(ol => ol.TotalPrice);
+ }
+}
+
+public class OrderLine
+{
+ public Guid Id { get; private set; }
+ public Guid ProductId { get; private set; }
+ public int Quantity { get; private set; }
+ public decimal UnitPrice { get; private set; }
+ public decimal TotalPrice => Quantity * UnitPrice;
+
+ public OrderLine(Guid productId, int quantity, decimal unitPrice)
+ {
+ Id = Guid.NewGuid();
+ ProductId = productId;
+ Quantity = quantity;
+ UnitPrice = unitPrice;
+ }
+}
+
+```
+
+Here, the `Order` enforces the rule _“an order can have at most 10 items”_ inside its `AddOrderLine` method. Nobody outside the class can bypass this, because `_orderLines` is private.
+
+👉 That’s the real strength of a classic Aggregate: **business rules are always protected at the boundary.**
+
+----------
+
+### **Chapter 2: Theory in Books vs. Reality in Code — Why Classic Aggregates Struggle**
+
+In Chapter 1, we painted the “ideal” world of DDD. Aggregates were like fortresses guarding our business rules…
+But what happens when we try to build that fortress in a real project with tools like Entity Framework Core? That’s when the gap between theory and practice starts to show up.
+
+#### **1. That `.Include()` Chain — Do We Really Need It? The Performance Trap**
+
+DDD books tell us: _“To validate a business rule, you must load the entire aggregate into memory.”_
+Sounds reasonable if consistency is the goal.
+
+But let’s picture a scenario: we have an `Order` aggregate with **500 order lines** inside it. And all we want to do is change its status to `Confirmed`.
+
+```csharp
+// Just to update a single field...
+var order = await _context.Orders
+ .Include(o => o.OrderLines) // <-- 500 rows pulled in!
+ .SingleOrDefaultAsync(o => o.Id == orderId);
+
+order.Confirm(); // Just sets order.Status = "Confirmed";
+
+await _context.SaveChangesAsync();
+
+```
+
+This query pulls **all 500 order lines into memory** just so we can flip a single `Status` field. Even in small projects, this is a silent performance killer. As the system grows, it will drag your app down.
+
+
+#### **2. The Abandoned Fortress — Sliding into Anemic Domain Models**
+
+Now, what’s a developer’s natural reaction to this? Something like:
+
+_“Pulling this much data is expensive. Maybe I should strip down the aggregate into a plain POCO with properties only, and move the logic into an `OrderService` class.”_
+
+This is how we slip straight into the **Anemic Domain Model** trap. Our classes lose their behavior, becoming nothing more than data bags.
+The whole DDD principle of _“keep behavior close to data”_ evaporates. Business logic leaks out of the aggregate and spreads across services. We think we’re doing DDD, but in reality, we’ve fallen back into classic transaction-script style coding.
+
+
+#### **3. One Model Doesn’t Fit All — The Clash of Command and Query**
+
+Aggregates are designed for **commands** — write operations where business rules must be enforced.
+
+But what about **queries**? Imagine a dashboard where we just want to list the last 10 orders. All we need is `OrderId`, `CustomerName`, and `TotalAmount`.
+
+Loading 10 fully-hydrated `Order` aggregates (with all their order lines) just for that list? That’s like using a cannon to hunt a sparrow. Wasteful, slow, and clumsy.
+Aggregates simply aren’t built for reporting or read-heavy scenarios.
+
+
+And there you have it — the three usual suspects that make developers doubt DDD in real life:
+
+- Performance headaches
+
+- The risk of falling into an Anemic Model
+
+- Aggregates being too heavy for read operations
+
+
+So, should we give up on DDD? Absolutely not!
+The key is to stop following the rules blindly and instead focus on their **real intent**. In the next chapter, we’ll explore the pragmatic approach — **Demystified Aggregates** — and how they can actually help us solve these problems.
+
+----------
+
+### **Chapter 3: Enter the Solution — What Exactly Is a "Demystified Aggregate"?**
+
+The issues we listed in the last chapter don’t mean DDD is bad. They just show that blindly applying textbook rules without considering the realities of your project creates friction.
+
+A **Demystified Aggregate** isn’t a library or a framework. It’s a **way of thinking**. Its philosophy is simple: focus on the Aggregate’s real job, and make sure it does that job **as efficiently as possible.**
+
+
+#### **1. Philosophy: Focus on Purpose, Not Rules**
+
+What’s the Aggregate’s most sacred duty?
+**To protect business rules (invariants) during a data change (command).**
+
+Here’s the key: an Aggregate’s job isn’t to always hold all data in memory. Its job is to **ensure consistency while performing an operation**.
+
+Think of it like a security guard at a bank vault. Their job is to make sure transfers are done correctly. They don’t need to memorize the serial number of every single banknote. They just need the critical info for the current operation: the balance and the transfer amount.
+
+The Demystified Aggregate says the same thing: when running a method, you **only load the data that method actually needs**, not the entire Aggregate.
+
+
+#### **2. The Core Idea: What “State” Does a Behavior Actually Need?**
+
+To apply this idea in code, ask yourself:
+_“What data does the `Confirm()` method on my `Order` Aggregate actually need?”_
+
+- Maybe just the order’s current `Status`. (`"Pending"` can become `"Confirmed"`, `"Cancelled"` throws an error.)
+
+- What about `AddItem(product, quantity)`?
+
+ - It needs the `Status` (can’t add items to a cancelled order).
+
+ - And maybe the existing `OrderLines` (to increase quantity if the item already exists).
+
+
+See the pattern? Each behavior needs different data. So why load everything every single time?
+
+
+#### **3. How Do We Do This in .NET & EF Core? Practical Solutions**
+
+Putting this philosophy into code is easier than you might think.
+
+**The Approach: Purpose-Built Repository Methods**
+
+Instead of a generic `GetByIdAsync()`, create methods tailored to the operation at hand. Let’s revisit our classic **Order Confirmation** scenario in a “Before & After” style.
+
+**BEFORE (Classic & Inefficient Approach)**
+
+```csharp
+// Repository Layer
+public async Task GetByIdAsync(Guid id)
+{
+ // LOAD EVERYTHING!
+ return await _context.Orders
+ .Include(o => o.OrderLines)
+ .SingleOrDefaultAsync(o => o.Id == id);
+}
+
+// Application Service Layer
+public async Task ConfirmOrderAsync(Guid orderId)
+{
+ var order = await _orderRepository.GetByIdAsync(orderId);
+ order.Confirm(); // This method might not even care about OrderLines!
+ await _unitOfWork.SaveChangesAsync();
+}
+
+```
+
+**AFTER (Demystified & Focused Approach)**
+
+```csharp
+// Repository Layer
+public async Task GetForConfirmationAsync(Guid id)
+{
+ // LOAD ONLY WHAT WE NEED! (No OrderLines needed)
+ return await _context.Orders
+ .SingleOrDefaultAsync(o => o.Id == id);
+}
+
+// Application Service Layer
+public async Task ConfirmOrderAsync(Guid orderId)
+{
+ // Intent is crystal clear in the code!
+ var order = await _orderRepository.GetForConfirmationAsync(orderId);
+
+ // Aggregate still protects the business rule.
+ // Confirm() checks status, etc.
+ order.Confirm();
+
+ await _unitOfWork.SaveChangesAsync();
+}
+
+```
+
+**What Do We Gain?**
+
+1. **Awesome Performance:** We avoid unnecessary JOINs and data transfer.
+
+2. **Clear Intent:** Anyone reading `GetForConfirmationAsync` immediately knows this operation only cares about the order itself, not its items. Code documents itself.
+
+3. **No Compromise:** Our Aggregate still enforces the business rules via `Confirm()`. DDD’s spirit remains intact.
+
+
+For **read/query operations**, the answer is even simpler: skip Aggregates altogether! Use optimized queries that return DTOs via `Select` projections, or even raw SQL with Dapper.
+
+That’s the essence of a Demystified Aggregate: **using the right tool for the right job.**
+
+In the next chapter, we’ll wrap everything up and tie all the concepts together.
+
+----------
+
+### **Conclusion: Pragmatism Beats Dogmatism in DDD**
+
+We’ve reached the finish line. We started with the “pure” textbook definition of Aggregates in the ideal world of Domain-Driven Design. Then we hit the real-world walls of performance and complexity. Finally, we learned how to break through those walls.
+
+The biggest lesson from the **Demystified Aggregates** approach is simple:
+
+**DDD isn’t a rigid rulebook — it’s a way of thinking.**
+
+Our goal isn’t to implement the “most pure DDD ever written in a book.” It’s to make our domain logic clean, solid, understandable, and performant. In this journey, patterns and rules should serve us, not the other way around.
+
+
+### **Key Takeaways**
+
+1. **Focus on the Core Purpose:**
+ The primary reason an Aggregate exists is to enforce business rules (invariants) and ensure consistency while handling a command. Every design decision should revolve around this purpose.
+
+2. **Load Only What You Need:**
+ You don’t have to load the entire Aggregate to execute a behavior. Use purpose-built repository methods (`GetForX()`) to fetch just the data needed for the operation. This can drastically improve both performance and readability.
+
+3. **Separate Writing from Reading:**
+ Use rich, protected Aggregates for commands (write operations). For queries (read operations), don’t burden your Aggregates. Instead, rely on projections, DTOs, or optimized queries. This is one of the simplest, most practical ways to embrace CQRS principles.
+
+Don’t be afraid to shape your Aggregates based on your project and the realities of your tools (like Entity Framework Core). The power of DDD lies in its **flexibility and pragmatism**.
+
+
diff --git a/docs/en/framework/architecture/domain-driven-design/application-services.md b/docs/en/framework/architecture/domain-driven-design/application-services.md
index 4d32f853dd..968ceb434d 100644
--- a/docs/en/framework/architecture/domain-driven-design/application-services.md
+++ b/docs/en/framework/architecture/domain-driven-design/application-services.md
@@ -134,7 +134,7 @@ The `CreateAsync` method above manually creates a `Book` entity from given `Crea
However, in many cases, it's very practical to use **auto object mapping** to set properties of an object from a similar object. ABP provides an [object to object mapping](../../infrastructure/object-to-object-mapping.md) infrastructure to make this even easier.
-Object to object mapping provides abstractions and it is implemented by the [AutoMapper](https://automapper.org/) library by default.
+Object to object mapping provides abstractions and it is implemented by the [Mapperly](https://mapperly.riok.app/) library by default.
Let's create another method to get a book. First, define the method in the `IBookAppService` interface:
@@ -162,36 +162,32 @@ public class BookDto
}
````
-AutoMapper requires to create a mapping [profile class](https://docs.automapper.org/en/stable/Configuration.html#profile-instances). Example:
+[Mapperly](https://mapperly.riok.app/) requires to create a mapping class that implements the `MapperBase` class with the `[Mapper]` attribute as follows:
-````csharp
-public class MyProfile : Profile
+```csharp
+[Mapper]
+public partial class BookToBookDtoMapper : MapperBase
{
- public MyProfile()
- {
- CreateMap();
- }
+ public override partial BookDto Map(Book source);
+
+ public override partial void Map(Book source, BookDto destination);
}
-````
+```
-You should then register profiles using the `AbpAutoMapperOptions`:
+Then, if your application uses multiple mapping providers, you should add the following configuration to your module's `ConfigureServices` method to decide which mapping provider to use:
````csharp
-[DependsOn(typeof(AbpAutoMapperModule))]
+[DependsOn(typeof(AbpMapperlyModule))]
public class MyModule : AbpModule
{
public override void ConfigureServices(ServiceConfigurationContext context)
{
- Configure(options =>
- {
- //Add all mappings defined in the assembly of the MyModule class
- options.AddMaps();
- });
+ context.Services.AddMapperlyObjectMapper();
}
}
````
-`AddMaps` registers all profile classes defined in the assembly of the given class, typically your module class. It also registers for the [attribute mapping](https://docs.automapper.org/en/stable/Attribute-mapping.html).
+With this configuration, your module will use [Mapperly](https://mapperly.riok.app/) as the default mapping provider and you don't need to register mapping classes manually.
Then you can implement the `GetAsync` method as shown below:
@@ -291,16 +287,21 @@ public class CreateUpdateBookDto
}
````
-[Profile](https://docs.automapper.org/en/stable/Configuration.html#profile-instances) class of DTO class.
+Define the mapping classes for [Mapperly](https://mapperly.riok.app/) as follows:
```csharp
-public class MyProfile : Profile
+[Mapper]
+public partial class BookToBookDtoMapper : MapperBase
{
- public MyProfile()
- {
- CreateMap();
- CreateMap();
- }
+ public override partial BookDto Map(Book source);
+ public override partial void Map(Book source, BookDto destination);
+}
+
+[Mapper]
+public partial class CreateUpdateBookDtoToBookMapper : MapperBase
+{
+ public override partial Book Map(CreateUpdateBookDto source);
+ public override partial void Map(CreateUpdateBookDto source, Book destination);
}
```
diff --git a/docs/en/framework/architecture/modularity/installer-projects.md b/docs/en/framework/architecture/modularity/installer-projects.md
new file mode 100644
index 0000000000..81c75ab015
--- /dev/null
+++ b/docs/en/framework/architecture/modularity/installer-projects.md
@@ -0,0 +1,221 @@
+# Module Installer Projects
+
+Each ABP module includes an `.Installer` project (e.g., `Volo.Abp.Account.Installer`) that serves as a **Virtual File System container** for module installation and resource management. These projects are essential for the ABP CLI to understand and install modules properly.
+
+## Purpose of Installer Projects
+
+Installer projects have three main purposes:
+
+1. **Virtual File System Integration**: Register the module's embedded resources with ABP's Virtual File System
+2. **Resource Packaging**: Package module metadata files (`.abpmdl` and `.abppkg`) as embedded resources
+3. **CLI Integration**: Enable the ABP CLI to understand module structure and install modules automatically
+
+## Structure of Installer Projects
+
+### Project Files
+
+- **`{ModuleName}.Installer.csproj`**: References `Volo.Abp.VirtualFileSystem` and embeds module metadata files
+- **`InstallationNotes.md`**: Documentation for the module
+- **`Volo/Abp/{ModuleName}/Abp{ModuleName}InstallerModule.cs`**: The core module class that registers embedded resources
+
+### Example Installer Module
+
+```csharp
+using Volo.Abp.Modularity;
+using Volo.Abp.VirtualFileSystem;
+
+namespace Volo.Abp.Account;
+
+[DependsOn(typeof(AbpVirtualFileSystemModule))]
+public class AbpAccountInstallerModule : AbpModule
+{
+ public override void ConfigureServices(ServiceConfigurationContext context)
+ {
+ Configure(options =>
+ {
+ options.FileSets.AddEmbedded();
+ });
+ }
+}
+```
+
+### Project Configuration
+
+The `.csproj` file embeds module metadata as content:
+
+```xml
+
+
+ net9.0
+ true
+
+
+
+
+
+
+
+
+
+
+ true
+ content\
+
+
+
+
+ true
+ content\
+
+
+
+```
+
+## Module Metadata Files
+
+### `.abpmdl` (Module Definition)
+
+The module definition file describes the module's structure and packages:
+
+```json
+{
+ "folders": {
+ "items": {
+ "src": {},
+ "test": {}
+ }
+ },
+ "packages": {
+ "Volo.Abp.Account.Web": {
+ "path": "src/Volo.Abp.Account.Web/Volo.Abp.Account.Web.abppkg",
+ "folder": "src"
+ },
+ "Volo.Abp.Account.Application": {
+ "path": "src/Volo.Abp.Account.Application/Volo.Abp.Account.Application.abppkg",
+ "folder": "src"
+ }
+ }
+}
+```
+
+### `.abppkg` (Package Definition)
+
+Each package has a definition file that specifies its role:
+
+```json
+{
+ "role": "lib.application"
+}
+```
+
+Common roles:
+- `lib.application`: Application layer package
+- `lib.mvc`: MVC/Web layer package
+- `lib.domain`: Domain layer package
+- `lib.domain-shared`: Shared domain layer package
+- `lib.efcore`: Entity Framework Core package
+
+## How Installer Projects Work
+
+### 1. CLI Installation Process
+
+When you run `abp add-module Volo.Abp.Account`:
+
+1. **Download Installer Package**: CLI downloads `Volo.Abp.Account.Installer` from NuGet
+2. **Read Module Definition**: CLI reads the embedded `.abpmdl` file to understand module structure
+3. **Read Package Definitions**: CLI reads `.abppkg` files to understand package roles
+4. **Install Packages**: CLI installs appropriate packages to correct project types based on roles
+5. **Add Dependencies**: CLI adds module dependencies to project module classes
+
+### 2. Virtual File System Integration
+
+The `InstallerModule` registers itself with the Virtual File System:
+
+```csharp
+options.FileSets.AddEmbedded();
+```
+
+This makes embedded resources available at runtime and enables:
+- Access to module metadata
+- Resource file management
+- Module configuration
+
+## Creating Installer Projects for New Modules
+
+### Required Files
+
+1. **Project File**: `{ModuleName}.Installer.csproj`
+2. **Module Class**: `Abp{ModuleName}InstallerModule.cs`
+3. **Documentation**: `InstallationNotes.md`
+4. **Module Definition**: `{ModuleName}.abpmdl` (in module root)
+5. **Package Definitions**: `{PackageName}.abppkg` (in each package)
+
+### Template Structure
+
+```
+modules/your-module/
+├── src/
+│ ├── Volo.Abp.YourModule.Installer/
+│ │ ├── Volo.Abp.YourModule.Installer.csproj
+│ │ ├── InstallationNotes.md
+│ │ └── Volo/
+│ │ └── Abp/
+│ │ └── YourModule/
+│ │ └── AbpYourModuleInstallerModule.cs
+│ └── [other packages]/
+├── Volo.Abp.YourModule.abpmdl
+└── [other module files]
+```
+
+### Package Definition Examples
+
+For different package types:
+
+```json
+// Application package
+{ "role": "lib.application" }
+
+// MVC package
+{ "role": "lib.mvc" }
+
+// Domain package
+{ "role": "lib.domain" }
+
+// EF Core package
+{ "role": "lib.efcore" }
+```
+
+## Why Installer Projects Appear "Empty"
+
+Installer projects appear minimal because their primary function is infrastructure, not business logic:
+
+- **No Business Logic**: Business logic belongs in the actual module packages
+- **Pure Infrastructure**: They only handle module installation and resource management
+- **CLI Integration**: They enable automated module installation through the ABP CLI
+- **Resource Management**: They package and distribute module metadata
+
+## Best Practices
+
+1. **Follow Naming Convention**: Use `{ModuleName}.Installer` for the project name
+2. **Include Documentation**: Always provide `InstallationNotes.md` with module information
+3. **Proper Dependencies**: Only depend on `Volo.Abp.VirtualFileSystem`
+4. **Embed All Metadata**: Include both `.abpmdl` and `.abppkg` files
+5. **Test Installation**: Verify your installer works with `abp add-module` command
+
+## Troubleshooting
+
+### Common Issues
+
+1. **Missing .abpmdl file**: Ensure the module definition file exists in the module root
+2. **Missing .abppkg files**: Each package needs a definition file
+3. **Incorrect roles**: Use appropriate roles for each package type
+4. **CLI not finding module**: Verify the installer package is published to NuGet
+
+### Verification Steps
+
+1. Build the installer project: `dotnet build`
+2. Check embedded resources: Verify `.abpmdl` and `.abppkg` files are embedded
+3. Test CLI installation: `abp add-module YourModule`
+4. Verify dependencies: Check that module dependencies are added correctly
+
+This installer system enables ABP's sophisticated module architecture, allowing for automated installation with proper dependency resolution and project type matching.
\ No newline at end of file
diff --git a/docs/en/framework/architecture/multi-tenancy/index.md b/docs/en/framework/architecture/multi-tenancy/index.md
index 2340d24103..21bb054b6a 100644
--- a/docs/en/framework/architecture/multi-tenancy/index.md
+++ b/docs/en/framework/architecture/multi-tenancy/index.md
@@ -384,6 +384,19 @@ namespace MultiTenancyDemo.Web
* A tenant resolver should set `context.TenantIdOrName` if it can determine it. If not, just leave it as is to allow the next resolver to determine it.
* `context.ServiceProvider` can be used if you need to additional services to resolve from the [dependency injection](../../fundamentals/dependency-injection.md) system.
+##### The Fallback Tenant
+
+If you want to always fallback to a tenant (in case of no tenant was found by the tenant resolution logic), you can set the `AbpTenantResolveOptions.FallbackTenant` option:
+
+```csharp
+Configure(options =>
+{
+ options.FallbackTenant = "acme";
+});
+```
+
+The `FallbackTenant` value can be a tenant name or tenant's Id. This option can be helpful on development time or some specific scenarios to set a constant tenant for the application. It is a simple and consistent way to ensure that a tenant context is always available when needed. However, when you do that, no way to switch to the host side. It is not something you will need it most of the time, but here if you need such a resolution logic.
+
#### Multi-Tenancy Middleware
Multi-Tenancy middleware is an ASP.NET Core request pipeline [middleware](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/middleware) that determines the current tenant from the HTTP request and sets the `ICurrentTenant` properties.
diff --git a/docs/en/framework/fundamentals/localization.md b/docs/en/framework/fundamentals/localization.md
index 6e8a3f678a..47c4ca564a 100644
--- a/docs/en/framework/fundamentals/localization.md
+++ b/docs/en/framework/fundamentals/localization.md
@@ -91,6 +91,34 @@ A JSON localization file content is shown below:
> ABP will ignore (skip) the JSON file if the `culture` section is missing.
+You can also use nesting or array in localization files, like this:
+
+````json
+{
+ "culture": "en",
+ "texts": {
+ "HelloWorld": "Hello World!",
+ "Hello": {
+ "World": "Hello World!"
+ },
+ "Hi":[
+ "Bye": "Bye World!"
+ "Hello": "Hello World!"
+ ]
+ }
+}
+````
+
+Then you can use it like this:
+
+> The double underscore (`__`) is used to separate the parent key from the child key.
+
+````csharp
+var str = L["Hello__World"]; // Hello World!
+var str2 = L["Hi__0"]; // Bye World!
+var str3 = L["Hi__1"]; // Hello World!
+````
+
### Default Resource
`AbpLocalizationOptions.DefaultResourceType` can be set to a resource type, so it is used when the localization resource was not specified:
diff --git a/docs/en/framework/fundamentals/object-extensions.md b/docs/en/framework/fundamentals/object-extensions.md
index b12be63dc0..87ece27f75 100644
--- a/docs/en/framework/fundamentals/object-extensions.md
+++ b/docs/en/framework/fundamentals/object-extensions.md
@@ -394,6 +394,22 @@ public class MyProfile : Profile
It has the same parameters with the `MapExtraPropertiesTo` method.
+#### Mapperly Integration
+
+If you're using the [Mapperly](https://github.com/riok/mapperly) library, the ABP also provides an extension method to utilize the `MapExtraPropertiesTo` method defined above.
+
+You can use the `MapExtraProperties` attribute to Mapperly class:
+
+````csharp
+[Mapper]
+[MapExtraProperties]
+public partial class IdentityUserToProfileDtoMapper : MapperBase
+{
+ public override partial IdentityUserDto Map(IdentityUser source);
+ public override partial void Map(IdentityUser source, IdentityUserDto destination);
+}
+````
+
## Entity Framework Core Database Mapping
If you're using the EF Core, you can map an extra property to a table field in the database. Example:
diff --git a/docs/en/framework/infrastructure/background-jobs/hangfire.md b/docs/en/framework/infrastructure/background-jobs/hangfire.md
index f5991ee19b..8377f001c0 100644
--- a/docs/en/framework/infrastructure/background-jobs/hangfire.md
+++ b/docs/en/framework/infrastructure/background-jobs/hangfire.md
@@ -159,14 +159,24 @@ app.UseAbpHangfireDashboard("/hangfire", options =>
`AbpHangfireAuthorizationFilter` class has the following fields:
* **`enableTenant` (`bool`, default: `false`):** Enables/disables accessing the Hangfire dashboard on tenant users.
-* **`requiredPermissionName` (`string`, default: `null`):** Hangfire dashboard is accessible only if the current user has the specified permission. In this case, if we specify a permission name, we don't need to set `enableTenant` `true` because the permission system already does it.
+* **`requiredPermissionName` (`string`, default: `null`):** Hangfire dashboard is accessible only if the current user has the specified permission.
+* **`requiredRoleNames` (`string[]`, default: `[]`):** Hangfire dashboard is accessible only if the current user has one of the specified roles.
-If you want to require an additional permission, you can pass it into the constructor as below:
+If you want to require more policies, you can use the `PolicyBuilder` property of the `AbpHangfireAuthorizationFilter` class.
```csharp
app.UseAbpHangfireDashboard("/hangfire", options =>
{
- options.AsyncAuthorization = new[] { new AbpHangfireAuthorizationFilter(requiredPermissionName: "MyHangFireDashboardPermissionName") };
+ var hangfireAuthorizationFilter = new AbpHangfireAuthorizationFilter(requiredPermissionName: "MyHangFireDashboardPermissionName");
+
+ //hangfireAuthorizationFilter.PolicyBuilder.AddRequirements(new PermissionRequirement("YourPermissionName"));
+ //hangfireAuthorizationFilter.PolicyBuilder.RequireRole("YourCustomRole");
+ //hangfireAuthorizationFilter.PolicyBuilder.Requirements.Add(new YourCustomRequirement());
+
+ options.AsyncAuthorization = new[]
+ {
+ hangfireAuthorizationFilter
+ };
});
```
@@ -190,18 +200,20 @@ private void ConfigureAuthentication(ServiceConfigurationContext context, IConfi
options.Authority = configuration["AuthServer:Authority"];
options.RequireHttpsMetadata = configuration.GetValue("AuthServer:RequireHttpsMetadata");
options.Audience = "MyProjectName";
- });
- context.Services.AddAuthentication()
- .AddCookie("Cookies")
- .AddOpenIdConnect("oidc", options =>
+ options.ForwardDefaultSelector = httpContext => httpContext.Request.Path.StartsWithSegments("/hangfire", StringComparison.OrdinalIgnoreCase)
+ ? CookieAuthenticationDefaults.AuthenticationScheme
+ : null;
+ })
+ .AddCookie(CookieAuthenticationDefaults.AuthenticationScheme)
+ .AddAbpOpenIdConnect(OpenIdConnectDefaults.AuthenticationScheme, options =>
{
options.Authority = configuration["AuthServer:Authority"];
- options.RequireHttpsMetadata = configuration.GetValue("AuthServer:RequireHttpsMetadata");
- options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
+ options.RequireHttpsMetadata = Convert.ToBoolean(configuration["AuthServer:RequireHttpsMetadata"]);
+ options.ResponseType = OpenIdConnectResponseType.Code;
- options.ClientId = configuration["AuthServer:ClientId"];
- options.ClientSecret = configuration["AuthServer:ClientSecret"];
+ options.ClientId = configuration["AuthServer:HangfireClientId"];
+ options.ClientSecret = configuration["AuthServer:HangfireClientSecret"];
options.UsePkce = true;
options.SaveTokens = true;
@@ -211,6 +223,8 @@ private void ConfigureAuthentication(ServiceConfigurationContext context, IConfi
options.Scope.Add("email");
options.Scope.Add("phone");
options.Scope.Add("MyProjectName");
+
+ options.SignInScheme = CookieAuthenticationDefaults.AuthenticationScheme;
});
}
```
@@ -218,26 +232,27 @@ private void ConfigureAuthentication(ServiceConfigurationContext context, IConfi
```csharp
app.Use(async (httpContext, next) =>
{
- if (httpContext.Request.Path.StartsWithSegments("/hangfire"))
+ if (httpContext.Request.Path.StartsWithSegments("/hangfire", StringComparison.OrdinalIgnoreCase))
{
- var result = await httpContext.AuthenticateAsync("Cookies");
- if (result.Succeeded)
+ var authenticateResult = await httpContext.AuthenticateAsync(CookieAuthenticationDefaults.AuthenticationScheme);
+ if (!authenticateResult.Succeeded)
{
- httpContext.User = result.Principal;
- await next(httpContext);
+ await httpContext.ChallengeAsync(
+ OpenIdConnectDefaults.AuthenticationScheme,
+ new AuthenticationProperties
+ {
+ RedirectUri = httpContext.Request.Path + httpContext.Request.QueryString
+ });
return;
}
-
- await httpContext.ChallengeAsync("oidc");
- }
- else
- {
- await next(httpContext);
}
+ await next.Invoke();
});
-
app.UseAbpHangfireDashboard("/hangfire", options =>
{
- options.AsyncAuthorization = new[] {new AbpHangfireAuthorizationFilter()};
+ options.AsyncAuthorization = new[]
+ {
+ new AbpHangfireAuthorizationFilter()
+ };
});
```
diff --git a/docs/en/framework/infrastructure/entity-cache.md b/docs/en/framework/infrastructure/entity-cache.md
index 64a03ad4c4..cba0cf8eaa 100644
--- a/docs/en/framework/infrastructure/entity-cache.md
+++ b/docs/en/framework/infrastructure/entity-cache.md
@@ -88,6 +88,17 @@ public class MyMapperProfile : Profile
}
```
+If you are using [Mapperly](https://mapperly.riok.app/), you can create a new mapping class that implements the `MapperBase` class with the `[Mapper]` attribute as follows:
+
+```csharp
+[Mapper]
+public partial class ProductToProductDtoMapper : MapperBase
+{
+ public override partial ProductDto Map(Product source);
+ public override partial void Map(Product source, ProductDto destination);
+}
+```
+
Now, you can inject the `IEntityCache` service wherever you want:
```csharp
diff --git a/docs/en/framework/infrastructure/event-bus/distributed/index.md b/docs/en/framework/infrastructure/event-bus/distributed/index.md
index d56215fa12..f379a44f40 100644
--- a/docs/en/framework/infrastructure/event-bus/distributed/index.md
+++ b/docs/en/framework/infrastructure/event-bus/distributed/index.md
@@ -643,6 +643,11 @@ Configure(options =>
* `InboxWaitingEventMaxCount`: The maximum number of events to query at once from the inbox in the database. Default value is 1000.
* `OutboxWaitingEventMaxCount`: The maximum number of events to query at once from the outbox in the database. Default value is 1000.
* `DistributedLockWaitDuration`: ABP uses [distributed locking](../../distributed-locking.md) to prevent concurrent access to the inbox and outbox messages in the database, when running multiple instance of the same application. If an instance of the application can not obtain the lock, it tries after a duration. This is the configuration of that duration. Default value is 15 seconds (`TimeSpan.FromSeconds(15)`).
+* `InboxProcessorFailurePolicy`: The policy to handle the failure of the inbox processor. Default value is `Retry`. Possible values are:
+ * `Retry`: The current exception and subsequent events will continue to be processed in order in the next cycle.
+ * `RetryLater`: Skip the event that caused the exception and continue with the following events. The failed event will be retried after a delay that doubles with each retry, starting from the configured `InboxProcessorRetryBackoffFactor` (e.g., 10, 20, 40, 80 seconds). The default maximum retry count is 10 (configurable). Discard the event if it still fails after reaching the maximum retry count.
+ * `Discard`: The event that caused the exception will be discarded and will not be retried.
+* `InboxProcessorRetryBackoffFactor`: The initial retry delay factor (double) used when `InboxProcessorFailurePolicy` is `RetryLater`. The retry delay is calculated as: `delay = InboxProcessorRetryBackoffFactor × 2^retryCount`. Default value is `10`.
### Skipping Outbox
diff --git a/docs/en/framework/infrastructure/object-to-object-mapping.md b/docs/en/framework/infrastructure/object-to-object-mapping.md
index 8961d804c7..8c9a0453df 100644
--- a/docs/en/framework/infrastructure/object-to-object-mapping.md
+++ b/docs/en/framework/infrastructure/object-to-object-mapping.md
@@ -84,7 +84,7 @@ public class UserAppService : ApplicationService
}
````
-You should have defined the mappings before to be able to map objects. See the AutoMapper integration section to learn how to define mappings.
+You should have defined the mappings before to be able to map objects. See the AutoMapper/Mapperly integration section to learn how to define mappings.
## AutoMapper Integration
@@ -217,13 +217,298 @@ public class MyProfile : Profile
}
````
+## Mapperly Integration
+
+[Mapperly](https://github.com/riok/mapperly) is a .NET source generator for generating object mappings. [Volo.Abp.Mapperly](https://www.nuget.org/packages/Volo.Abp.Mapperly) package defines the Mapperly integration for the `IObjectMapper`.
+
+Once you define mappings class as below, you can use the `IObjectMapper` interface just like explained before.
+
+### Define Mapping Classes
+
+You can define a mapper class by using the `Mapper` attribute. The class and methods must be `partial` to allow the Mapperly to generate the implementation during the build process:
+
+````csharp
+[Mapper]
+public partial class UserToUserDtoMapper : MapperBase
+{
+ public override partial UserDto Map(User source);
+ public override partial void Map(User source, UserDto destination);
+}
+````
+
+If you also want to map `UserDto` to `User`, you can inherit from the `TwoWayMapperBase` class:
+
+````csharp
+[Mapper]
+public partial class UserToUserDtoMapper : TwoWayMapperBase
+{
+ public override partial UserDto Map(User source);
+ public override partial void Map(User source, UserDto destination);
+
+ public override partial User ReverseMap(UserDto destination);
+ public override partial void ReverseMap(UserDto destination, User source);
+}
+````
+
+### Before and After Mapping Methods
+
+The base class provides `BeforeMap` and `AfterMap` methods that can be overridden to perform actions before and after the mapping:
+
+````csharp
+[Mapper]
+public partial class UserToUserDtoMapper : TwoWayMapperBase
+{
+ public override partial UserDto Map(User source);
+ public override partial void Map(User source, UserDto destination);
+
+ public override partial void BeforeMap(User source)
+ {
+ //TODO: Perform actions before the mapping
+ }
+
+ public override partial void AfterMap(User source, UserDto destination)
+ {
+ //TODO: Perform actions after the mapping
+ }
+
+ public override partial User ReverseMap(UserDto destination);
+ public override partial void ReverseMap(UserDto destination, User source);
+
+ public override partial void BeforeReverseMap(UserDto destination)
+ {
+ //TODO: Perform actions before the reverse mapping
+ }
+
+ public override partial void AfterReverseMap(UserDto destination, User source)
+ {
+ //TODO: Perform actions after the reverse mapping
+ }
+}
+````
+
+### Mapping the Object Extensions
+
+[Object extension system](../fundamentals/object-extensions.md) allows to define extra properties for existing classes. ABP provides a mapping definition extension to properly map extra properties of two objects:
+
+````csharp
+[Mapper]
+[MapExtraProperties]
+public partial class UserToUserDtoMapper : MapperBase
+{
+ public override partial UserDto Map(User source);
+ public override partial void Map(User source, UserDto destination);
+}
+````
+
+It is suggested to use the `MapExtraPropertiesAttribute` attribute if both classes are extensible objects (implement the `IHasExtraProperties` interface). See the [object extension document](../fundamentals/object-extensions.md) for more.
+
+### Property Setter Method
+
+Mapperly requires that properties of both source and destination objects have `setter` methods. Otherwise, the property will be ignored. You can use `protected set` or `private set` to control the visibility of the `setter` method, but each property must have a `setter` method.
+
+### Deep Cloning
+
+By default, Mapperly does not create deep copies of objects to improve performance. If an object can be directly assigned to the target, it will do so (e.g., if the source and target type are both `List`, the list and its entries will not be cloned). To create deep copies, set the `UseDeepCloning` property on the `MapperAttribute` to `true`.
+
+````csharp
+[Mapper(UseDeepCloning = true)]
+public partial class UserToUserDtoMapper : MapperBase
+{
+ public override partial UserDto Map(User source);
+ public override partial void Map(User source, UserDto destination);
+}
+````
+
+### Lists and Arrays Support
+
+ABP Mapperly integration also supports mapping lists and arrays as explained in the [IObjectMapper Interface](#iobjectmappertsource-tdestination-interface) section.
+
+**Example**:
+
+````csharp
+[Mapper]
+public partial class UserToUserDtoMapper : MapperBase
+{
+ public override partial UserDto Map(User source);
+ public override partial void Map(User source, UserDto destination);
+}
+
+var users = await _userRepository.GetListAsync(); // returns List
+var dtos = ObjectMapper.Map, List>(users); // creates List
+````
+
+> When mapping a collection property, if the source value is null Mapperly will keep the destination value as null. This is different from AutoMapper, which will map the destination field to an empty collection.
+
+### Nested Mapping
+
+When working with nested object mapping, there's an important limitation to be aware of. If you have separate mappers for nested types like in the example below, the parent mapper (`SourceTypeToDestinationTypeMapper`) will not automatically use the nested mapper (`SourceNestedTypeToDestinationNestedTypeMapper`) to handle the mapping of nested properties. This means that configurations like the `MapperIgnoreTarget` attribute on the nested mapper will be ignored during the parent mapping operation.
+
+````csharp
+public class SourceNestedType
+{
+ public string Name { get; set; }
+
+ public string Ignored { get; set; }
+}
+
+public class SourceType
+{
+ public string Name { get; set; }
+
+ public SourceNestedType Nested { get; set; }
+}
+
+public class DestinationNestedType
+{
+ public string Name { get; set; }
+
+ public string Ignored { get; set; }
+}
+
+public class DestinationType
+{
+ public string Name { get; set; }
+
+ public DestinationNestedType Nested { get; set; }
+}
+
+[Mapper]
+public partial class SourceTypeToDestinationTypeMapper : MapperBase
+{
+ public override partial DestinationType Map(SourceType source);
+ public override partial void Map(SourceType source, DestinationType destination);
+}
+
+[Mapper]
+public partial class SourceNestedTypeToDestinationNestedTypeMapper : MapperBase
+{
+ [MapperIgnoreTarget(nameof(SourceNestedType.Ignored))]
+ public override partial DestinationNestedType Map(SourceNestedType source);
+
+ [MapperIgnoreTarget(nameof(SourceNestedType.Ignored))]
+ public override partial void Map(SourceNestedType source, DestinationNestedType destination);
+}
+````
+
+There are several ways to solve this nested mapping issue. Choose the approach that best fits your specific requirements:
+
+#### Solution 1: Multi-Interface Implementation
+
+Implement both mapping interfaces (`IAbpMapperlyMapper` and `IAbpMapperlyMapper`) in a single mapper class. This approach consolidates all related mapping logic into one class.
+
+**Important:** Remember to implement `ITransientDependency` to register the mapper class with the dependency injection container.
+
+````csharp
+[Mapper]
+public partial class SourceTypeToDestinationTypeMapper : IAbpMapperlyMapper, IAbpMapperlyMapper, ITransientDependency
+{
+ public partial DestinationType Map(SourceType source);
+ public partial void Map(SourceType source, DestinationType destination);
+ public void BeforeMap(SourceType source)
+ {
+ }
+
+ public void AfterMap(SourceType source, DestinationType destination)
+ {
+ }
+
+ [MapperIgnoreTarget(nameof(SourceNestedType.Ignored))]
+ public partial DestinationNestedType Map(SourceNestedType source);
+
+ [MapperIgnoreTarget(nameof(SourceNestedType.Ignored))]
+ public partial void Map(SourceNestedType source, DestinationNestedType destination);
+
+ public void BeforeMap(SourceNestedType source)
+ {
+ }
+
+ public void AfterMap(SourceNestedType source, DestinationNestedType destination)
+ {
+ }
+}
+````
+
+#### Solution 2: Consolidate Mapping Methods
+
+Copy the nested mapping methods from `SourceNestedTypeToDestinationNestedTypeMapper` to the parent `SourceTypeToDestinationTypeMapper` class. This ensures all mapping logic is contained within a single mapper.
+
+Example:
+
+````csharp
+[Mapper]
+public partial class SourceTypeToDestinationTypeMapper : MapperBase
+{
+ public override partial DestinationType Map(SourceType source);
+ public override partial void Map(SourceType source, DestinationType destination);
+
+ [MapperIgnoreTarget(nameof(SourceNestedType.Ignored))]
+ public override partial DestinationNestedType Map(SourceNestedType source);
+ [MapperIgnoreTarget(nameof(SourceNestedType.Ignored))]
+ public override partial void Map(SourceNestedType source, DestinationNestedType destination);
+}
+
+[Mapper]
+public partial class SourceNestedTypeToDestinationNestedTypeMapper : MapperBase
+{
+ [MapperIgnoreTarget(nameof(SourceNestedType.Ignored))]
+ public override partial DestinationNestedType Map(SourceNestedType source);
+
+ [MapperIgnoreTarget(nameof(SourceNestedType.Ignored))]
+ public override partial void Map(SourceNestedType source, DestinationNestedType destination);
+}
+````
+
+#### Solution 3: Dependency Injection Approach
+
+Inject the nested mapper as a dependency into the parent mapper and use it in the `AfterMap` method to handle nested object mapping manually.
+
+Example:
+
+````csharp
+[Mapper]
+public partial class SourceTypeToDestinationTypeMapper : MapperBase
+{
+ private readonly SourceNestedTypeToDestinationNestedTypeMapper _sourceNestedTypeToDestinationNestedTypeMapper;
+
+ public SourceTypeToDestinationTypeMapper(SourceNestedTypeToDestinationNestedTypeMapper sourceNestedTypeToDestinationNestedTypeMapper)
+ {
+ _sourceNestedTypeToDestinationNestedTypeMapper = sourceNestedTypeToDestinationNestedTypeMapper;
+ }
+
+ public override partial DestinationType Map(SourceType source);
+ public override partial void Map(SourceType source, DestinationType destination);
+
+ public override void AfterMap(SourceType source, DestinationType destination)
+ {
+ if (source.Nested != null)
+ {
+ destination.Nested = _sourceNestedTypeToDestinationNestedTypeMapper.Map(source.Nested);
+ }
+ }
+}
+````
+
+#### Choosing the Right Solution
+
+Each solution has its own advantages:
+
+- **Solution 1** consolidates all mapping logic in one place and works well when mappings are tightly related.
+- **Solution 2** is simple but can lead to code duplication if you need the nested mapper elsewhere.
+- **Solution 3** maintains separation of concerns and reusability but requires manual mapping in the `AfterMap` method.
+
+Choose the approach that best aligns with your application's architecture and maintainability requirements.
+
+### More Mapperly Features
+
+Most of Mapperly's features such as `Ignore` can be configured through its attributes. See the [Mapperly documentation](https://mapperly.riok.app/docs/intro/) for more details.
+
## Advanced Topics
### IObjectMapper Interface
-Assume that you have created a **reusable module** which defines AutoMapper profiles and uses `IObjectMapper` when it needs to map objects. Your module then can be used in different applications, by nature of the [modularity](../architecture/modularity/basics.md).
+Assume that you have created a **reusable module** which defines AutoMapper/Mapperly profiles and uses `IObjectMapper` when it needs to map objects. Your module then can be used in different applications, by nature of the [modularity](../architecture/modularity/basics.md).
-`IObjectMapper` is an abstraction and can be replaced by the final application to use another mapping library. The problem here that your reusable module is designed to use the AutoMapper library, because it only defines mappings for it. In such a case, you will want to guarantee that your module always uses AutoMapper even if the final application uses another default object mapping library.
+`IObjectMapper` is an abstraction and can be replaced by the final application to use another mapping library. The problem here that your reusable module is designed to use the AutoMapper/Mapperly library, because it only defines mappings for it. In such a case, you will want to guarantee that your module always uses AutoMapper/Mapperly even if the final application uses another default object mapping library.
`IObjectMapper` is used to contextualize the object mapper, so you can use different libraries for different modules/contexts.
@@ -281,6 +566,8 @@ public class UserAppService : ApplicationService
While using the contextualized object mapper is same as the normal object mapper, you should register the contextualized mapper in your module's `ConfigureServices` method:
+When using AutoMapper:
+
````csharp
[DependsOn(typeof(AbpAutoMapperModule))]
public class MyModule : AbpModule
@@ -298,6 +585,20 @@ public class MyModule : AbpModule
}
````
+When using Mapperly:
+
+````csharp
+[DependsOn(typeof(AbpMapperlyModule))]
+public class MyModule : AbpModule
+{
+ public override void ConfigureServices(ServiceConfigurationContext context)
+ {
+ //Use Mapperly for MyModule
+ context.Services.AddMapperlyObjectMapper();
+ }
+}
+````
+
`IObjectMapper` is an essential feature for a reusable module where it can be used in multiple applications each may use a different library for object to object mapping. All pre-built ABP modules are using it. But, for the final application, you can ignore this interface and always use the default `IObjectMapper` interface.
### IObjectMapper Interface
diff --git a/docs/en/framework/ui/angular/form-validation.md b/docs/en/framework/ui/angular/form-validation.md
index 6a67018124..6e36945c96 100644
--- a/docs/en/framework/ui/angular/form-validation.md
+++ b/docs/en/framework/ui/angular/form-validation.md
@@ -170,3 +170,211 @@ export const appConfig: ApplicationConfig = {
The error message will be bold and italic now:
+
+## How to Validate Nested Form Groups
+
+There are multiple ways to validate nested form groups in ABP Angular UI. Below is the first and most common approach, using automatic validation and error messages with nested reactive forms. (A second method will be described in the next section.)
+
+### 1st Way: Automatic Validation and Error Message Using Nested Reactive Forms
+
+ABP Angular UI leverages Angular's reactive forms and the [ngx-validate](https://www.npmjs.com/package/@ngx-validate/core) library to provide a robust, flexible, and user-friendly form validation experience. Whether you build your forms manually or use ABP’s dynamic form generation features, validation and error messages are handled automatically.
+
+#### Key Features
+
+- **Automatic Validation:**
+ All validation rules defined in your DTOs (such as `[Required]`, `[StringLength]`, `[EmailAddress]`, etc.) are automatically reflected in the Angular form. Error messages are shown under each field without any extra markup.
+
+- **Nested Form Groups and Dynamic Fields:**
+ For complex data structures, you can group fields or manage dynamic lists using nested `FormGroup` and `FormArray` structures. Validation and error display work seamlessly for both parent and child controls.
+
+- **Dynamic and Extensible Forms:**
+ With ABP’s extensibility system, you can generate forms dynamically using helpers like `generateFormFromProps` and display them with the `abp-extensible-form` component. This ensures all entity properties (including extension properties) are included in the form and their validation rules are applied.
+
+- **No Extra Boilerplate:**
+ You do not need to add custom error components or directives for validation. The system works out of the box, including for nested and dynamically generated controls.
+
+#### Real-World Example: Nested Form Groups in the Users Form
+
+Below is a real example from the Users management form in ABP Angular UI, showing how nested form structures and validation are implemented. This example includes both dynamically generated fields (with `abp-extensible-form`) and a dynamic list of roles using `FormArray` and `FormGroup`.
+
+**TypeScript: Building the Form**
+
+```ts
+buildForm() {
+ const data = new FormPropData(this.injector, this.selected);
+ this.form = generateFormFromProps(data); // Automatically creates form controls from entity and extension properties
+
+ this.service.getAssignableRoles().subscribe(({ items }) => {
+ this.roles = items;
+ if (this.roles) {
+ // Dynamic roles list: nested FormArray and FormGroup
+ this.form.addControl(
+ 'roleNames',
+ this.fb.array(
+ this.roles.map(role =>
+ this.fb.group({
+ [role.name as string]: [
+ this.selected?.id
+ ? !!this.selectedUserRoles?.find(userRole => userRole.id === role.id)
+ : role.isDefault,
+ ],
+ }),
+ ),
+ ),
+ );
+ }
+ });
+}
+```
+
+**HTML: Displaying the Form**
+
+```html
+
+
+ {{ (selected?.id ? 'AbpIdentity::Edit' : 'AbpIdentity::NewUser') | abpLocalization }}
+
+
+
+ @if (form) {
+
+ } @else {
+
+ }
+
+
+```
+
+**Explanation:**
+- `abp-extensible-form` automatically generates and displays all entity fields and their validation.
+- In the Roles tab, each role is represented by a checkbox, and these checkboxes are managed in a `FormArray`, with each as a `FormGroup`. This is a real-world example of a nested form structure.
+- All validation and error messages are shown automatically for both the main form and nested groups.
+
+
+### 2nd Way: Manual Nested Reactive Forms Without abp-extensible-form
+
+You can also build and validate nested form groups manually, without using `abp-extensible-form` or dynamic helpers. This approach gives you full control over the form structure and is useful for custom or non-entity-based forms.
+
+#### Example: Simple Manual Nested FormGroup
+
+Below is a simple, generic example of a nested reactive form. This form includes a nested `FormGroup` for profile information and demonstrates how to apply validation rules.
+
+**TypeScript: Building the Form**
+
+```ts
+import { Component, OnInit, inject } from '@angular/core';
+import { FormBuilder, FormGroup, Validators } from '@angular/forms';
+import { NgxValidateCoreModule } from '@ngx-validate/core';
+
+@Component({
+ selector: 'app-nested-form',
+ templateUrl: './nested-form.component.html',
+ standalone: true,
+ imports: [NgxValidateCoreModule],
+})
+export class NestedFormComponent implements OnInit {
+ form: FormGroup;
+
+ private fb = inject(FormBuilder);
+
+ ngOnInit() {
+ this.buildForm();
+ }
+
+ buildForm() {
+ this.form = this.fb.group({
+ userName: ['', Validators.required],
+ email: ['', [Validators.required, Validators.email]],
+ profile: this.fb.group({
+ firstName: ['', Validators.required],
+ lastName: ['', Validators.required],
+ }),
+ });
+ }
+
+ submit() {
+ if (this.form.invalid) {
+ return;
+ }
+ // handle submit
+ }
+}
+```
+
+**HTML: Displaying the Form**
+
+```html
+
+```
+
+**How it works:**
+- The form contains main fields (`userName`, `email`) and a nested `FormGroup` (`profile`).
+- The `profile` group includes `firstName` and `lastName` fields, each with their own validation rules.
+- Validation rules are defined directly in the form builder.
+- Error messages and validation feedback are handled automatically by ngx-validate and ABP Angular UI, just like with dynamic forms.
+- This structure ensures that validation works automatically for both the main form and nested groups.
+
+> **Note:** This approach is ideal for custom forms or when you want full control over the form structure. It provides a user experience and validation behavior similar to ABP's dynamic forms, but with manual control over the form layout and logic.
+
+---
\ No newline at end of file
diff --git a/docs/en/framework/ui/angular/modifying-the-menu.md b/docs/en/framework/ui/angular/modifying-the-menu.md
index ee3997b9d7..44b2bb0bfd 100644
--- a/docs/en/framework/ui/angular/modifying-the-menu.md
+++ b/docs/en/framework/ui/angular/modifying-the-menu.md
@@ -269,7 +269,12 @@ this.routes.remove(['Your navigation']);
// or
this.routes.removeByParam({ name: 'Your navigation' });
```
+**Method Parameters:**
+- `remove(routeNames: string[])`: Takes an array of route names to remove.
+- `removeByParam(routeProperty: Partial)`: Takes any route property (name, path, parentName, etc.) to match and remove routes.
+
+**Results of the operations above:**
- Moved the _Home_ navigation under the _Administration_ dropdown based on given `parentName`.
- Added an icon to _Home_.
- Specified the order and made _Home_ the first item in list.
diff --git a/docs/en/modules/docs.md b/docs/en/modules/docs.md
index b564980ba3..b9c3209e3f 100644
--- a/docs/en/modules/docs.md
+++ b/docs/en/modules/docs.md
@@ -148,11 +148,6 @@ An ABP module must declare `[DependsOn]` attribute if it has a dependency upon a
{
options.DefinitionProviders.Add();
});
-
- Configure(options =>
- {
- options.AddProfile();
- });
}
}
```
diff --git a/docs/en/others/why-abp-platform.md b/docs/en/others/why-abp-platform.md
index c13631546b..61756d2654 100644
--- a/docs/en/others/why-abp-platform.md
+++ b/docs/en/others/why-abp-platform.md
@@ -169,7 +169,7 @@ The learning curve is much lower than not using the ABP. That may sound surprisi
ABP creates a full stack, production-ready, working solution for you in seconds. Many of the real-life problems are already solved and many fine tune configurations are already applied for the ASP.NET Core and the other used libraries. If you start from scratch, you will experience and learn all these details yourself to truly implement your solution.
-ABP uses the industry standard frameworks, libraries and systems you already know (or need to learn to build a real-world product) like Angular, Blazor, MAUI, EF Core, AutoMapper, OpenIddict, Bootstrap, Redis, SignalR... etc. So, all your knowledge is directly re-usable with the ABP. ABP even simplifies using these libraries and systems and solves the integration problems. If you don't know these tools now, learning them will be easier within the ABP.
+ABP uses the industry standard frameworks, libraries and systems you already know (or need to learn to build a real-world product) like Angular, Blazor, MAUI, EF Core, AutoMapper (switched to Mapperly due to licensing concerns), OpenIddict, Bootstrap, Redis, SignalR... etc. So, all your knowledge is directly re-usable with the ABP. ABP even simplifies using these libraries and systems and solves the integration problems. If you don't know these tools now, learning them will be easier within the ABP.
ABP provides an excellent infrastructure to apply DDD principles and other best practices. It provides a lot of sweet abstractions and automation to reduce the repeating code. However, it doesn't force you to use or apply all these. A common mistake is to see that ABP has a lot of features, and it is hard to learn all of them. Having a lot of features is an advantage when you come to the point that you need them. However, you don't need to know a feature until you need it, and you can continue with the development approach you are used to. You can still write code as you are used to as if ABP doesn't provide all these benefits. Learning the ABP infrastructure is progressive. You will love it whenever you learn a new feature but can continue developing without knowing its existence.
diff --git a/docs/en/release-info/migration-guides/AutoMapper-To-Mapperly.md b/docs/en/release-info/migration-guides/AutoMapper-To-Mapperly.md
new file mode 100644
index 0000000000..7356a6930b
--- /dev/null
+++ b/docs/en/release-info/migration-guides/AutoMapper-To-Mapperly.md
@@ -0,0 +1,376 @@
+# Migrating from AutoMapper to Mapperly
+
+## Introduction
+
+The AutoMapper library is **no longer free for commercial use**. For more details, you can refer to [this announcement post](https://www.jimmybogard.com/automapper-and-mediatr-going-commercial/).
+
+ABP Framework provides both AutoMapper and Mapperly integrations. If your project currently uses AutoMapper and you don't have a commercial license, you can switch to Mapperly by following the steps outlined below.
+
+## Migration Steps
+
+Please open your project in an IDE(`Visual Studio`, `VS Code` or `JetBrains Rider`), then perform the following global search and replace operations:
+
+1. Replace `Volo.Abp.AutoMapper` with `Volo.Abp.Mapperly` in all `*.csproj` files.
+2. Replace `using Volo.Abp.AutoMapper;` with `using Volo.Abp.Mapperly;` in all `*.cs` files.
+3. Replace `AbpAutoMapperModule` with `AbpMapperlyModule` in all `*.cs` files.
+4. Replace `AddAutoMapperObjectMapper` with `AddMapperlyObjectMapper` in all `*.cs` files.
+5. Remove any code sections that configure `Configure`.
+6. Review any existing AutoMapper `Profile` classes and ensure all newly created Mapperly mapping classes are registered appropriately. (You can refer to the example below for guidance)
+
+**Example:**
+
+Here is an AutoMapper's `Profile` class:
+
+```csharp
+public class ExampleAutoMapper : Profile
+{
+ public AbpIdentityApplicationModuleAutoMapperProfile()
+ {
+ CreateMap()
+ .MapExtraProperties()
+ .Ignore(x => x.IsLockedOut)
+ .Ignore(x => x.SupportTwoFactor)
+ .Ignore(x => x.RoleNames);
+
+ CreateMap();
+
+ CreateMap()
+ .MapExtraProperties();
+
+ CreateMap()
+ .ReverseMap();
+
+ CreateMap()
+ .ForMember(dest => dest.RoleId, src => src.MapFrom(r => r.Id));
+
+ CreateMap()
+ .ForMember(dest => dest.Active, src => src.MapFrom(r => r.IsActive ? "Yes" : "No"))
+ .ForMember(dest => dest.EmailConfirmed, src => src.MapFrom(r => r.EmailConfirmed ? "Yes" : "No"))
+ .ForMember(dest => dest.TwoFactorEnabled, src => src.MapFrom(r => r.TwoFactorEnabled ? "Yes" : "No"))
+ .ForMember(dest => dest.AccountLookout, src => src.MapFrom(r => r.LockoutEnd != null && r.LockoutEnd > DateTime.UtcNow ? "Yes" : "No"))
+ .Ignore(x => x.Roles);
+ }
+}
+```
+
+And the Mapperly mapping class:
+
+```csharp
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+[MapExtraProperties]
+public partial class IdentityUserToIdentityUserDtoMapper : MapperBase
+{
+ [MapperIgnoreTarget(nameof(IdentityUserDto.IsLockedOut))]
+ [MapperIgnoreTarget(nameof(IdentityUserDto.SupportTwoFactor))]
+ [MapperIgnoreTarget(nameof(IdentityUserDto.RoleNames))]
+ public override partial IdentityUserDto Map(IdentityUser source);
+
+ [MapperIgnoreTarget(nameof(IdentityUserDto.IsLockedOut))]
+ [MapperIgnoreTarget(nameof(IdentityUserDto.SupportTwoFactor))]
+ [MapperIgnoreTarget(nameof(IdentityUserDto.RoleNames))]
+ public override partial void Map(IdentityUser source, IdentityUserDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class IdentityUserClaimToIdentityUserClaimDtoMapper : MapperBase
+{
+ public override partial IdentityUserClaimDto Map(IdentityUserClaim source);
+
+ public override partial void Map(IdentityUserClaim source, IdentityUserClaimDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+[MapExtraProperties]
+public partial class OrganizationUnitToOrganizationUnitDtoMapper : MapperBase
+{
+ public override partial OrganizationUnitDto Map(OrganizationUnit source);
+ public override partial void Map(OrganizationUnit source, OrganizationUnitDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class OrganizationUnitRoleToOrganizationUnitRoleDtoMapper : TwoWayMapperBase
+{
+ public override partial OrganizationUnitRoleDto Map(OrganizationUnitRole source);
+ public override partial void Map(OrganizationUnitRole source, OrganizationUnitRoleDto destination);
+
+ public override partial OrganizationUnitRole ReverseMap(OrganizationUnitRoleDto destination);
+ public override partial void ReverseMap(OrganizationUnitRoleDto destination, OrganizationUnitRole source);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+[MapExtraProperties]
+public partial class OrganizationUnitToOrganizationUnitWithDetailsDtoMapper : MapperBase
+{
+ [MapperIgnoreTarget(nameof(OrganizationUnitWithDetailsDto.Roles))]
+ [MapperIgnoreTarget(nameof(OrganizationUnitWithDetailsDto.UserCount))]
+ public override partial OrganizationUnitWithDetailsDto Map(OrganizationUnit source);
+
+ [MapperIgnoreTarget(nameof(OrganizationUnitWithDetailsDto.Roles))]
+ [MapperIgnoreTarget(nameof(OrganizationUnitWithDetailsDto.UserCount))]
+ public override partial void Map(OrganizationUnit source, OrganizationUnitWithDetailsDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class IdentityRoleToOrganizationUnitRoleDtoMapper : MapperBase
+{
+ [MapProperty(nameof(IdentityRole.Id), nameof(OrganizationUnitRoleDto.RoleId))]
+ public override partial OrganizationUnitRoleDto Map(IdentityRole source);
+
+ [MapProperty(nameof(IdentityRole.Id), nameof(OrganizationUnitRoleDto.RoleId))]
+ public override partial void Map(IdentityRole source, OrganizationUnitRoleDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class IdentityUserToIdentityUserExportDtoMapper : MapperBase
+{
+ [MapperIgnoreTarget(nameof(IdentityUserExportDto.Roles))]
+ public override partial IdentityUserExportDto Map(IdentityUser source);
+
+ [MapperIgnoreTarget(nameof(IdentityUserExportDto.Roles))]
+ public override partial void Map(IdentityUser source, IdentityUserExportDto destination);
+
+ public override void AfterMap(IdentityUser source, IdentityUserExportDto destination)
+ {
+ destination.Active = source.IsActive ? "Yes" : "No";
+ destination.EmailConfirmed = source.EmailConfirmed ? "Yes" : "No";
+ destination.TwoFactorEnabled = source.TwoFactorEnabled ? "Yes" : "No";
+ destination.AccountLookout = source.LockoutEnd != null && source.LockoutEnd > DateTime.UtcNow ? "Yes" : "No";
+ }
+}
+```
+
+## Mapperly Mapping Class
+
+To use Mapperly, you'll need to create a dedicated mapping class for each source and destination types.
+
+* Use the `[Mapper]` attribute to designate the class as a Mapperly mapper. The `RequiredMappingStrategy` is set to `Target` by default.
+* Replace AutoMapper's `Ignore()` method with the `[MapperIgnoreTarget]` attribute.
+* Replace the `MapExtraProperties()` method with the `[MapExtraProperties]` attribute.
+* Use the `TwoWayMapperBase` class as an alternative to AutoMapper’s `ReverseMap()` functionality.
+* Implement the `AfterMap()` method to execute logic after the mapping is completed.
+
+### Dependency Injection in Mapper Class
+
+All Mapperly mapping classes automatically registered in the [dependency injection (DI)](../../framework/fundamentals/dependency-injection.md) container. To use a service within a Mapper class, simply add it to the constructor; Mapperly will inject it automatically.
+
+**Example:**
+
+```csharp
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class IdentityUserToIdentityUserDtoMapper : MapperBase
+{
+ public IdentityUserToIdentityUserDtoMapper(MyService myService)
+ {
+ _myService = myService;
+ }
+
+ public override partial IdentityUserDto Map(IdentityUser source);
+ public override partial void Map(IdentityUser source, IdentityUserDto destination);
+
+ public override void AfterMap(IdentityUser source, IdentityUserDto destination)
+ {
+ destination.MyProperty = _myService.GetMyProperty(source.MyProperty);
+ }
+}
+```
+
+## AI Prompt for Migrating AutoMapper to Mapperly
+
+If you have AI tools like Cursor, you can use the following prompt to migrate your AutoMapper mappings to Mapperly automatically:
+
+> AI may generate some code that is not correct. Please check the code carefully.
+
+```
+Please help me migrate AutoMapper Profile classes to Mapperly. I have AutoMapper Profile files in my current workspace/context that need to be converted.
+
+**Conversion Requirements:**
+
+1. **Convert AutoMapper Profile to Mapperly Mappers**: Transform each `CreateMap` into a separate Mapperly mapper class
+2. **Rename the file**: Change from `XXXAutoMapperProfile.cs` to `XXXMappers.cs`
+3. **Use proper Mapperly attributes**:
+ - `[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]` for each mapper class
+ - `[MapExtraProperties]` for classes that need extra properties mapping
+ - `[MapperIgnoreTarget]` for ignored properties
+ - `[MapProperty]` for custom property mappings
+4. **Inherit from appropriate base classes**:
+ - `MapperBase` for one-way mapping
+ - `TwoWayMapperBase` for reverse mapping
+5. **Handle complex mappings**: Use `AfterMap` method for complex transformations
+
+**Note:** The code below contains two parts - both are reference examples for you to understand the conversion pattern:
+1. **AutoMapper Profile example** - shows the original AutoMapper code structure
+2. **Mapperly Mappers example** - shows the expected converted Mapperly code structure
+
+Please convert the actual AutoMapper Profile files that exist in your current context/workspace, following the same conversion pattern as shown in these examples.
+
+**Reference Examples:**
+
+**1. AutoMapper Profile (original code):**
+
+using System;
+using AutoMapper;
+using System.Linq;
+using Volo.Abp.AutoMapper;
+
+namespace Volo.Abp.Identity;
+
+public class ExampleAutoMapperProfile : Profile
+{
+ public ExampleAutoMapperProfile()
+ {
+ CreateMap()
+ .MapExtraProperties()
+ .Ignore(x => x.IsLockedOut)
+ .Ignore(x => x.SupportTwoFactor)
+ .Ignore(x => x.RoleNames);
+
+ CreateMap();
+
+ CreateMap()
+ .MapExtraProperties();
+
+ CreateMap()
+ .ReverseMap();
+
+ CreateMap()
+ .ForMember(dest => dest.RoleId, src => src.MapFrom(r => r.Id));
+
+ CreateMap()
+ .ForMember(dest => dest.Active, src => src.MapFrom(r => r.IsActive ? "Yes" : "No"))
+ .ForMember(dest => dest.EmailConfirmed, src => src.MapFrom(r => r.EmailConfirmed ? "Yes" : "No"))
+ .ForMember(dest => dest.TwoFactorEnabled, src => src.MapFrom(r => r.TwoFactorEnabled ? "Yes" : "No"))
+ .ForMember(dest => dest.AccountLookout, src => src.MapFrom(r => r.LockoutEnd != null && r.LockoutEnd > DateTime.UtcNow ? "Yes" : "No"))
+ .Ignore(x => x.Roles);
+ }
+}
+
+---
+
+**2. Mapperly Mappers (converted code):**
+
+using System;
+using System.Linq;
+using Riok.Mapperly.Abstractions;
+using Volo.Abp.Mapperly;
+
+namespace Volo.Abp.Identity;
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+[MapExtraProperties]
+public partial class IdentityUserToIdentityUserDtoMapper : MapperBase
+{
+ [MapperIgnoreTarget(nameof(IdentityUserDto.IsLockedOut))]
+ [MapperIgnoreTarget(nameof(IdentityUserDto.SupportTwoFactor))]
+ [MapperIgnoreTarget(nameof(IdentityUserDto.RoleNames))]
+ public override partial IdentityUserDto Map(IdentityUser source);
+
+ [MapperIgnoreTarget(nameof(IdentityUserDto.IsLockedOut))]
+ [MapperIgnoreTarget(nameof(IdentityUserDto.SupportTwoFactor))]
+ [MapperIgnoreTarget(nameof(IdentityUserDto.RoleNames))]
+ public override partial void Map(IdentityUser source, IdentityUserDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class IdentityUserClaimToIdentityUserClaimDtoMapper : MapperBase
+{
+ public override partial IdentityUserClaimDto Map(IdentityUserClaim source);
+
+ public override partial void Map(IdentityUserClaim source, IdentityUserClaimDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+[MapExtraProperties]
+public partial class OrganizationUnitToOrganizationUnitDtoMapper : MapperBase
+{
+ public override partial OrganizationUnitDto Map(OrganizationUnit source);
+ public override partial void Map(OrganizationUnit source, OrganizationUnitDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class OrganizationUnitRoleToOrganizationUnitRoleDtoMapper : TwoWayMapperBase
+{
+ public override partial OrganizationUnitRoleDto Map(OrganizationUnitRole source);
+ public override partial void Map(OrganizationUnitRole source, OrganizationUnitRoleDto destination);
+
+ public override partial OrganizationUnitRole ReverseMap(OrganizationUnitRoleDto destination);
+ public override partial void ReverseMap(OrganizationUnitRoleDto destination, OrganizationUnitRole source);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+[MapExtraProperties]
+public partial class OrganizationUnitToOrganizationUnitWithDetailsDtoMapper : MapperBase
+{
+ [MapperIgnoreTarget(nameof(OrganizationUnitWithDetailsDto.Roles))]
+ [MapperIgnoreTarget(nameof(OrganizationUnitWithDetailsDto.UserCount))]
+ public override partial OrganizationUnitWithDetailsDto Map(OrganizationUnit source);
+
+ [MapperIgnoreTarget(nameof(OrganizationUnitWithDetailsDto.Roles))]
+ [MapperIgnoreTarget(nameof(OrganizationUnitWithDetailsDto.UserCount))]
+ public override partial void Map(OrganizationUnit source, OrganizationUnitWithDetailsDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class IdentityRoleToOrganizationUnitRoleDtoMapper : MapperBase
+{
+ [MapProperty(nameof(IdentityRole.Id), nameof(OrganizationUnitRoleDto.RoleId))]
+ public override partial OrganizationUnitRoleDto Map(IdentityRole source);
+
+ [MapProperty(nameof(IdentityRole.Id), nameof(OrganizationUnitRoleDto.RoleId))]
+ public override partial void Map(IdentityRole source, OrganizationUnitRoleDto destination);
+}
+
+[Mapper(RequiredMappingStrategy = RequiredMappingStrategy.Target)]
+public partial class IdentityUserToIdentityUserExportDtoMapper : MapperBase
+{
+ [MapperIgnoreTarget(nameof(IdentityUserExportDto.Roles))]
+ public override partial IdentityUserExportDto Map(IdentityUser source);
+
+ [MapperIgnoreTarget(nameof(IdentityUserExportDto.Roles))]
+ public override partial void Map(IdentityUser source, IdentityUserExportDto destination);
+
+ public override void AfterMap(IdentityUser source, IdentityUserExportDto destination)
+ {
+ destination.Active = source.IsActive ? "Yes" : "No";
+ destination.EmailConfirmed = source.EmailConfirmed ? "Yes" : "No";
+ destination.TwoFactorEnabled = source.TwoFactorEnabled ? "Yes" : "No";
+ destination.AccountLookout = source.LockoutEnd != null && source.LockoutEnd > DateTime.UtcNow ? "Yes" : "No";
+ }
+}
+```
+
+## Mapperly Documentation
+
+Please refer to the [Mapperly documentation](https://mapperly.riok.app/docs/intro/) for more details.
+
+**Key points:**
+
+- [Mapperly Configuration](https://mapperly.riok.app/docs/configuration/mapper/)
+- [Mapperly Enums](https://mapperly.riok.app/docs/configuration/enum/)
+- [Mapperly Flattening and unflattening](https://mapperly.riok.app/docs/configuration/flattening/)
+
+
+## Set Default Mapping Provider
+
+When your project contains modules using both AutoMapper and Mapperly, you may need to explicitly set the default `IAutoObjectMappingProvider` to ensure consistent behavior across your application.
+
+If your application uses `AutoMapper`:
+
+```csharp
+public override void ConfigureServices(ServiceConfigurationContext context)
+{
+ context.Services.AddAutoMapperObjectMapper();
+}
+```
+
+If your application uses `Mapperly`:
+
+```csharp
+public override void ConfigureServices(ServiceConfigurationContext context)
+{
+ context.Services.AddMapperlyObjectMapper();
+}
+```
+
+### Why Set Default Mapping Provider?
+
+When your project contains modules using both AutoMapper and Mapperly, both `AbpAutoMapperModule` and `AbpMapperlyModule` will be loaded. Their dependency order may vary based on your project's module structure, and the last loaded module will override the `IAutoObjectMappingProvider` implementation. This could lead to unexpected behavior. Setting an explicit default ensures predictable mapping behavior throughout your application.
diff --git a/docs/en/release-info/migration-guides/pro/openiddict-microservice.md b/docs/en/release-info/migration-guides/pro/openiddict-microservice.md
index 818a8c368a..33c319111b 100644
--- a/docs/en/release-info/migration-guides/pro/openiddict-microservice.md
+++ b/docs/en/release-info/migration-guides/pro/openiddict-microservice.md
@@ -472,17 +472,12 @@ In `appsettings.json` replace **IdentityServer** section with **OpenIddict** and
typeof(AbpOpenIddictProWebModule),
```
-- In **IdentityServiceWebModule.cs** add object mapping configurations:
+- In **IdentityServiceWebModule.cs** add object mapping configurations for [Mapperly](https://mapperly.riok.app/) (if you are using an another mapping providers, see the [Object to Object Mapping](../../../framework/infrastructure/object-to-object-mapping.md) documentation):
```csharp
- context.Services.AddAutoMapperObjectMapper();
- Configure(options =>
- {
- options.AddMaps(validate: true);
- });
+ context.Services.AddMapperlyObjectMapper();
```
-
### Shared Hosting Module
- In **MyApplicationSharedHostingModule** replace the **database configuration**:
diff --git a/docs/en/solution-templates/guide.md b/docs/en/solution-templates/guide.md
index cb14f57ef3..ded0c49f20 100644
--- a/docs/en/solution-templates/guide.md
+++ b/docs/en/solution-templates/guide.md
@@ -27,7 +27,7 @@ Besides the overall solution structure, the internals of each project in a solut
### Library Integrations & Configurations
-When you use ABP startup solution templates to create a new solution, some **fundamental library installations** ([Serilog](https://serilog.net/), [Autofac](https://autofac.org/), [AutoMapper](https://automapper.org/), [Swagger](https://swagger.io/), [HealthCheck](https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks) and others..) and their fine-tuned configurations are already prepared for you. Also, required **[ABP packages](https://abp.io/packages)** are just installed based on your preferences and configured for **development and production environments**.
+When you use ABP startup solution templates to create a new solution, some **fundamental library installations** ([Serilog](https://serilog.net/), [Autofac](https://autofac.org/), [Mapperly](https://mapperly.riok.app/), [Swagger](https://swagger.io/), [HealthCheck](https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks) and others..) and their fine-tuned configurations are already prepared for you. Also, required **[ABP packages](https://abp.io/packages)** are just installed based on your preferences and configured for **development and production environments**.
### Development Ready
diff --git a/docs/en/tutorials/book-store/part-01.md b/docs/en/tutorials/book-store/part-01.md
index 6b856d9687..4634a68c67 100644
--- a/docs/en/tutorials/book-store/part-01.md
+++ b/docs/en/tutorials/book-store/part-01.md
@@ -291,22 +291,17 @@ public class BookDto : AuditedEntityDto
* The `BookDto` is used to transfer the book data to the presentation layer in order to show the book information on the UI.
* The `BookDto` is derived from the `AuditedEntityDto` which has audit properties just like the `Book` entity defined above.
-It will be needed to map the `Book` entities to the `BookDto` objects while returning books to the presentation layer. [AutoMapper](https://automapper.org) library can automate this conversion when you define the proper mapping. The startup template comes with AutoMapper pre-configured. So, you can just define the mapping in the `BookStoreApplicationAutoMapperProfile` class in the `Acme.BookStore.Application` project:
+It will be needed to map the `Book` entities to the `BookDto` objects while returning books to the presentation layer. [Mapperly](https://mapperly.riok.app/) library can automate this conversion when you define the proper mapping. The startup template comes with Mapperly pre-configured. So, you can just define the mapping in the `BookStoreApplicationMappers` class in the `Acme.BookStore.Application` project:
-````csharp
-using Acme.BookStore.Books;
-using AutoMapper;
-
-namespace Acme.BookStore;
-
-public class BookStoreApplicationAutoMapperProfile : Profile
+```csharp
+[Mapper]
+public partial class BookToBookDtoMapper : MapperBase
{
- public BookStoreApplicationAutoMapperProfile()
- {
- CreateMap();
- }
+ public override partial BookDto Map(Book source);
+
+ public override partial void Map(Book source, BookDto destination);
}
-````
+```
> See the [object to object mapping](../../framework/infrastructure/object-to-object-mapping.md) document for details.
@@ -343,21 +338,23 @@ public class CreateUpdateBookDto
As done to the `BookDto` above, we should define the mapping from the `CreateUpdateBookDto` object to the `Book` entity. The final class will be as shown below:
-````csharp
-using Acme.BookStore.Books;
-using AutoMapper;
+```csharp
+[Mapper]
+public partial class BookToBookDtoMapper : MapperBase
+{
+ public override partial BookDto Map(Book source);
-namespace Acme.BookStore;
+ public override partial void Map(Book source, BookDto destination);
+}
-public class BookStoreApplicationAutoMapperProfile : Profile
+[Mapper]
+public partial class CreateUpdateBookDtoToBookMapper : MapperBase
{
- public BookStoreApplicationAutoMapperProfile()
- {
- CreateMap();
- CreateMap();
- }
+ public override partial Book Map(CreateUpdateBookDto source);
+
+ public override partial void Map(CreateUpdateBookDto source, Book destination);
}
-````
+```
### IBookAppService
@@ -416,7 +413,7 @@ public class BookAppService :
* `BookAppService` is derived from `CrudAppService<...>` which implements all the CRUD (create, read, update, delete) methods defined by the `ICrudAppService`.
* `BookAppService` injects `IRepository` which is the default repository for the `Book` entity. ABP automatically creates default repositories for each aggregate root (or entity). See the [repository document](../../framework/architecture/domain-driven-design/repositories.md).
-* `BookAppService` uses `IObjectMapper` service ([see](../../framework/infrastructure/object-to-object-mapping.md)) to map the `Book` objects to the `BookDto` objects and `CreateUpdateBookDto` objects to the `Book` objects. The Startup template uses the [AutoMapper](http://automapper.org/) library as the object mapping provider. We have defined the mappings before, so it will work as expected.
+* `BookAppService` uses `IObjectMapper` service ([see](../../framework/infrastructure/object-to-object-mapping.md)) to map the `Book` objects to the `BookDto` objects and `CreateUpdateBookDto` objects to the `Book` objects. The Startup template uses the [Mapperly](https://mapperly.riok.app/) library as the object mapping provider. We have defined the mappings before, so it will work as expected.
## Auto API Controllers
diff --git a/docs/en/tutorials/book-store/part-03.md b/docs/en/tutorials/book-store/part-03.md
index 45444ee76f..e67353b1fa 100644
--- a/docs/en/tutorials/book-store/part-03.md
+++ b/docs/en/tutorials/book-store/part-03.md
@@ -298,23 +298,17 @@ public class EditModalModel : BookStorePageModel
### Mapping from BookDto to CreateUpdateBookDto
-To be able to map the `BookDto` to `CreateUpdateBookDto`, configure a new mapping. To do this, open the `BookStoreWebAutoMapperProfile.cs` file in the `Acme.BookStore.Web` project and change it as shown below:
+To be able to map the `BookDto` to `CreateUpdateBookDto`, configure a new mapping. To do this, open the `BookStoreWebMappers.cs` file in the `Acme.BookStore.Web` project and change it as shown below:
-````csharp
-using AutoMapper;
-
-namespace Acme.BookStore.Web;
-
-public class BookStoreWebAutoMapperProfile : Profile
+```csharp
+[Mapper]
+public partial class BookDtoToCreateUpdateBookDtoMapper : MapperBase
{
- public BookStoreWebAutoMapperProfile()
- {
- CreateMap();
- }
-}
-````
+ public override partial CreateUpdateBookDto Map(BookDto source);
-* We have just added `CreateMap();` to define this mapping.
+ public override partial void Map(BookDto source, CreateUpdateBookDto destination);
+}
+```
> Notice that we do the mapping definition in the web layer as a best practice since it is only needed in this layer.
@@ -1288,28 +1282,26 @@ We can now define a modal to edit the book. Add the following code to the end of
````
-### AutoMapper Configuration
+### Mapperly Configuration
The base `AbpCrudPageBase` uses the [object to object mapping](../../framework/infrastructure/object-to-object-mapping.md) system to convert an incoming `BookDto` object to a `CreateUpdateBookDto` object. So, we need to define the mapping.
-Open the `BookStoreBlazorAutoMapperProfile` inside the {{ if UI == "BlazorServer" }}`Acme.BookStore.Blazor` {{ else if UI == "MAUIBlazor" }}`Acme.BookStore.MauiBlazor` {{ else }}`Acme.BookStore.Blazor.Client`{{ end }} project and change the content as the following:
+Open the `BookStoreBlazorMappers` inside the {{ if UI == "BlazorServer" }}`Acme.BookStore.Blazor` {{ else if UI == "MAUIBlazor" }}`Acme.BookStore.MauiBlazor` {{ else }}`Acme.BookStore.Blazor.Client`{{ end }} project and change the content as the following:
-````csharp
-using Acme.BookStore.Books;
-using AutoMapper;
+```csharp
+using Riok.Mapperly.Abstractions;
+using Volo.Abp.Mapperly;
{{ if UI == "BlazorServer" }}namespace Acme.BookStore.Blazor; {{ else if UI == "MAUIBlazor" }}namespace Acme.BookStore.MauiBlazor; {{ else }}namespace Acme.BookStore.Blazor.Client;{{ end }}
-public class BookStoreBlazorAutoMapperProfile : Profile
+[Mapper]
+public partial class BookDtoToCreateUpdateBookDtoMapper : MapperBase
{
- public BookStoreBlazorAutoMapperProfile()
- {
- CreateMap();
- }
-}
-````
+ public override partial CreateUpdateBookDto Map(BookDto source);
-* We've just added the `CreateMap();` line to define the mapping.
+ public override partial void Map(BookDto source, CreateUpdateBookDto destination);
+}
+```
### Test the Editing Modal
diff --git a/docs/en/tutorials/book-store/part-08.md b/docs/en/tutorials/book-store/part-08.md
index a7d73f0209..ac49c6aee4 100644
--- a/docs/en/tutorials/book-store/part-08.md
+++ b/docs/en/tutorials/book-store/part-08.md
@@ -193,7 +193,7 @@ public async Task GetAsync(Guid id)
}
````
-This method simply gets the `Author` entity by its `Id`, converts to the `AuthorDto` using the [object to object mapper](../../framework/infrastructure/object-to-object-mapping.md). This requires to configure the AutoMapper, which will be explained later.
+This method simply gets the `Author` entity by its `Id`, converts to the `AuthorDto` using the [object to object mapper](../../framework/infrastructure/object-to-object-mapping.md). This requires to configure the Mapperly, which will be explained later.
### GetListAsync
@@ -350,12 +350,18 @@ Finally, add the following entries to the `Localization/BookStore/en.json` insid
## Object to Object Mapping
-`AuthorAppService` is using the `ObjectMapper` to convert the `Author` objects to `AuthorDto` objects. So, we need to define this mapping in the AutoMapper configuration.
+`AuthorAppService` is using the `ObjectMapper` to convert the `Author` objects to `AuthorDto` objects. So, we need to define this mapping in the Mapperly configuration.
-Open the `BookStoreApplicationAutoMapperProfile` class inside the `Acme.BookStore.Application` project and add the following line to the constructor:
+Open the `BookStoreApplicationMappers` class inside the `Acme.BookStore.Application` project and define the following mapping class:
````csharp
-CreateMap();
+[Mapper]
+public partial class AuthorToAuthorDtoMapper : MapperBase
+{
+ public override partial AuthorDto Map(Author source);
+
+ public override partial void Map(Author source, AuthorDto destination);
+}
````
## Data Seeder
diff --git a/docs/en/tutorials/book-store/part-09.md b/docs/en/tutorials/book-store/part-09.md
index 06db5f37d9..18ecd2726d 100644
--- a/docs/en/tutorials/book-store/part-09.md
+++ b/docs/en/tutorials/book-store/part-09.md
@@ -335,27 +335,16 @@ The main reason of this decision was to show you how to use a different model cl
* Added `[DataType(DataType.Date)]` attribute to the `BirthDate` which shows a date picker on the UI for this property.
* Added `[TextArea]` attribute to the `ShortBio` which shows a multi-line text area instead of a standard textbox.
-In this way, you can specialize the view model class based on your UI requirements without touching to the DTO. As a result of this decision, we have used `ObjectMapper` to map `CreateAuthorViewModel` to `CreateAuthorDto`. To be able to do that, you need to add a new mapping code to the `BookStoreWebAutoMapperProfile` constructor:
+In this way, you can specialize the view model class based on your UI requirements without touching to the DTO. As a result of this decision, we have used `ObjectMapper` to map `CreateAuthorViewModel` to `CreateAuthorDto`. To be able to do that, you need to define a new mapping configuration in the `BookStoreWebMappers` class:
-````csharp
-using Acme.BookStore.Authors; // ADDED NAMESPACE IMPORT
-using Acme.BookStore.Books;
-using AutoMapper;
-
-namespace Acme.BookStore.Web;
-
-public class BookStoreWebAutoMapperProfile : Profile
+```csharp
+[Mapper]
+public partial class CreateAuthorViewModelToCreateAuthorDtoMapper : MapperBase
{
- public BookStoreWebAutoMapperProfile()
- {
- CreateMap();
-
- // ADD a NEW MAPPING
- CreateMap();
- }
+ public override partial CreateAuthorDto Map(Pages.Authors.CreateModalModel.CreateAuthorViewModel source);
+ public override partial void Map(Pages.Authors.CreateModalModel.CreateAuthorViewModel source, CreateAuthorDto destination);
}
-````
+```
"New author" button will work as expected and open a new model when you run the application again:
@@ -456,29 +445,22 @@ This class is similar to the `CreateModal.cshtml.cs` while there are some main d
* Uses the `IAuthorAppService.GetAsync(...)` method to get the editing author from the application layer.
* `EditAuthorViewModel` has an additional `Id` property which is marked with the `[HiddenInput]` attribute that creates a hidden input for this property.
-This class requires to add two object mapping declarations to the `BookStoreWebAutoMapperProfile` class:
+This class requires to add two object mapping declarations, so open the `BookStoreWebMappers` class and add the following mappings:
```csharp
-using Acme.BookStore.Authors;
-using Acme.BookStore.Books;
-using AutoMapper;
-
-namespace Acme.BookStore.Web;
-
-public class BookStoreWebAutoMapperProfile : Profile
+[Mapper]
+public partial class AuthorDtoToEditAuthorViewModelMapper : MapperBase
{
- public BookStoreWebAutoMapperProfile()
- {
- CreateMap();
+ public override partial EditAuthorViewModel Map(AuthorDto source);
- CreateMap();
+ public override partial void Map(AuthorDto source, EditAuthorViewModel destination);
+}
- // ADD THESE NEW MAPPINGS
- CreateMap();
- CreateMap();
- }
+[Mapper]
+public partial class EditAuthorViewModelToUpdateAuthorDtoMapper : MapperBase
+{
+ public override partial UpdateAuthorDto Map(Pages.Authors.EditModalModel.EditAuthorViewModel source);
+ public override partial void Map(Pages.Authors.EditModalModel.EditAuthorViewModel source, UpdateAuthorDto destination);
}
```
@@ -1220,13 +1202,23 @@ This class typically defines the properties and methods used by the `Authors.raz
`Authors` class uses the `IObjectMapper` in the `OpenEditAuthorModal` method. So, we need to define this mapping.
-Open the `BookStoreBlazorAutoMapperProfile.cs` in the {{ if UI == "BlazorServer" }}`Acme.BookStore.Blazor`{{ else if UI == "MAUIBlazor" }}`Acme.BookStore.MauiBlazor`{{ else }}`Acme.BookStore.Blazor.Client`{{ end }} project and add the following mapping code in the constructor:
+Open the `BookStoreBlazorMappers.cs` in the {{ if UI == "BlazorServer" }}`Acme.BookStore.Blazor`{{ else if UI == "MAUIBlazor" }}`Acme.BookStore.MauiBlazor`{{ else }}`Acme.BookStore.Blazor.Client`{{ end }} project and add the following mappings in the class:
-````csharp
-CreateMap();
-````
+```csharp
+using Riok.Mapperly.Abstractions;
+using Volo.Abp.Mapperly;
+using Acme.BookStore.Authors;
+
+//...
+
+[Mapper]
+public partial class AuthorDtoToUpdateAuthorDtoMapper : MapperBase
+{
+ public override partial UpdateAuthorDto Map(AuthorDto source);
-You will need to declare a `using Acme.BookStore.Authors;` statement to the beginning of the file.
+ public override partial void Map(AuthorDto source, UpdateAuthorDto destination);
+}
+```
### Add to the Main Menu
diff --git a/docs/en/tutorials/book-store/part-10.md b/docs/en/tutorials/book-store/part-10.md
index d4137e3681..02d1f81aba 100644
--- a/docs/en/tutorials/book-store/part-10.md
+++ b/docs/en/tutorials/book-store/part-10.md
@@ -578,11 +578,17 @@ Let's see the changes we've done:
### Object to Object Mapping Configuration
-Introduced the `AuthorLookupDto` class and used object mapping inside the `GetAuthorLookupAsync` method. So, we need to add a new mapping definition inside the `BookStoreApplicationAutoMapperProfile.cs` file of the `Acme.BookStore.Application` project:
+Introduced the `AuthorLookupDto` class and used object mapping inside the `GetAuthorLookupAsync` method. So, we need to add a new mapping definition inside the `BookStoreApplicationMappers.cs` file of the `Acme.BookStore.Application` project:
-````csharp
-CreateMap();
-````
+```csharp
+[Mapper]
+public partial class AuthorToAuthorLookupDtoMapper : MapperBase
+{
+ public override partial AuthorLookupDto Map(Author source);
+
+ public override partial void Map(Author source, AuthorLookupDto destination);
+}
+```
## Unit Tests
@@ -898,12 +904,37 @@ These changes require a small change in the `EditModal.cshtml`. Remove the `();
-CreateMap();
-CreateMap();
+using Riok.Mapperly.Abstractions;
+using Volo.Abp.Mapperly;
+
+//...
+
+[Mapper]
+public partial class CreateBookViewModelToCreateUpdateBookDtoMapper : MapperBase
+{
+ public override partial CreateUpdateBookDto Map(Pages.Books.CreateModalModel.CreateBookViewModel source);
+
+ public override partial void Map(Pages.Books.CreateModalModel.CreateBookViewModel source, CreateUpdateBookDto destination);
+}
+
+[Mapper]
+public partial class BookDtoToEditBookViewModelMapper : MapperBase
+{
+ public override partial Pages.Books.EditModalModel.EditBookViewModel Map(BookDto source);
+
+ public override partial void Map(BookDto source, Pages.Books.EditModalModel.EditBookViewModel destination);
+}
+
+[Mapper]
+public partial class EditBookViewModelToCreateUpdateBookDtoMapper : MapperBase