Loretta
599f8a6787
- 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. |
||
|---|---|---|
| .. | ||
| LOGGING | ||
| README.md | ||
| SERVICES.md | ||
README.md
Mango.Nop.Services documentation
Topic documentation for the Mango.Nop.Services project (Layer 2, service patterns).
Reference docs (flat)
SERVICES.md— Service pattern usage
Topic folders
LOGGING/— Logger bridge between NopCommerce's logger and AyCode.Core's logger (project-specific variant)
Navigation
Per the AI Agent Core Protocol (folder navigation rule), start from this README when browsing docs/. Single-file reference docs remain flat; project-specific variants of framework topics (like LOGGING) live in named subfolders.
See also
- Base logger (framework):
../../../../../Aycode/Source/AyCode.Core/AyCode.Core/docs/LOGGING/README.md - Remote logger variant:
../../../../../Aycode/Source/AyCode.Core/AyCode.Services/docs/LOGGING/README.md - Server-side logger variant:
../../../../../Aycode/Source/AyCode.Core/AyCode.Core.Server/docs/LOGGING/README.md