- 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 | ||
| GLOSSARY.md | ||
| README.md | ||
README.md
Mango.Nop Libraries documentation
Top-level documentation for the Mango.Nop shared libraries (Layer 2 — shared NopCommerce plugin framework).
Reference docs (flat)
ARCHITECTURE.md— Repo architecture overviewCONVENTIONS.md— Coding conventionsGLOSSARY.md— Domain glossary
Sub-projects with docs
Mango.Nop.Core/docs/— Core entity mirrors, DTOs, architectureMango.Nop.Data/docs/— Repository and transaction patternsMango.Nop.Services/docs/— Service patterns, logger bridge
Navigation
Per the AI Agent Core Protocol (folder navigation rule), start from this README when browsing docs/. Single-file reference docs remain flat at this level; multi-file topics live in named subfolders at the sub-project level.
See also
- Base framework:
../../../../Aycode/Source/AyCode.Core/(see each project'sdocs/folder).