- Restructured documentation: added `docs/README.md` to each sub-project, moved LOGGING and SIGNALR docs into dedicated subfolders with their own `README.md`. - Updated all cross-references to use new topic folder paths and canonical AyCode.Core doc locations. - Updated `.csproj` files to auto-include all Markdown docs and project-level `README.md` files. - Removed obsolete single-file docs, replaced with structured content in topic folders. - Enforced AI Agent Protocol: session setup, output prefix, no-re-read, and mandatory `docs-check` skill after code changes. - Added domain-critical reminders and navigation guidance to relevant `README.md` files. |
||
|---|---|---|
| .. | ||
| ARCHITECTURE.md | ||
| CONVENTIONS.md | ||
| DTOS.md | ||
| NOP_DEPENDENCIES.md | ||
| README.md | ||
README.md
Mango.Nop.Core documentation
Topic documentation for the Mango.Nop.Core project (Layer 2 framework — NopCommerce-adjacent base types).
Reference docs (flat)
ARCHITECTURE.md— Project architectureCONVENTIONS.md— Project-specific conventionsDTOS.md— DTO system, mapping strategiesNOP_DEPENDENCIES.md— NopCommerce entity mirror pattern
Navigation
Per the AI Agent Core Protocol (folder navigation rule), start from this README when browsing docs/. All docs at this level are single-file reference; topic folders (e.g., LOGGING/) exist only at sub-projects that host a variant (see ../Mango.Nop.Services/docs/LOGGING/).
See also
- Repo-level conventions:
../../docs/CONVENTIONS.md - Base framework:
../../../../../Aycode/Source/AyCode.Core/docs