Delete the standalone "Token-Based Configuration Magic" and the duplicate "Tenant Resolution Priority Chain" sections from the article. Update the feature index/table to replace the Token Replacement entry with Tenant Resolution, and adjust the numbering/labels for Background Job Queue and Widgets so the list stays consistent. This cleans up duplicated content and fixes the section ordering.
Update article to document ABP auto-generated API controllers and dynamic client proxies, including examples and where the behavior is implemented. Clarify that permission and feature checks are NOT automatic and must be applied explicitly with [Authorize] and [RequiresFeature] (notes about the related interceptor registrars included). Renumber sections, expand explanations for anti-forgery, event handling, UOW, outbox, virtual files, JSON settings, localization, and background jobs, and update the summary table to reflect the new/clarified items (Remote Services, Auto API Controllers, Dynamic Client Proxies, Permissions/Features changes).
Add a new community article with a cover image documenting ABP Framework's default conventions and behaviors. Adds docs/en/Community-Articles/2026-02-19-ABP-Framework-Hidden-Magic/post.md and images/cover.png; the article outlines 30+ automatic features (service registration, validation, UOW, auditing, Mapperly, outbox, event handling, virtual file system, Swagger, tenant resolution, etc.) to help developers understand what 'just works' in ABP and how to customize or disable defaults.
Add an Important note to docs/en/modules/cms-kit-pro/index.md clarifying that CMS Kit Pro requires both the base Volo.CmsKit.* packages and the Volo.CmsKit.Pro.* packages. Notes that the `abp add-module Volo.CmsKit.Pro` command will handle this automatically, but if adding packages manually you must include both sets.
Introduce a set of JSON Schema definitions for the ABP Low Code model. Adds schema files for entities, properties, property types, UI descriptors, form availability, enums, foreign keys, interceptors, command interceptors, validators, and custom HTTP endpoints, plus a top-level model.schema.json that references these definitions to validate model.json configuration files. These schemas enable validation and tooling for lowcode entity/config definitions and custom endpoint JavaScript payloads.