Skip to content

Latest commit

 

History

History
149 lines (102 loc) · 6.07 KB

File metadata and controls

149 lines (102 loc) · 6.07 KB

AdventureWorks Documentation

This directory contains technical documentation for the AdventureWorks e-commerce application, organized by topic.

📁 Documentation Structure

docs/
├── architecture/          # System design and architecture
├── features/             # Feature-specific documentation
│   ├── ai-agent/        # AI agent and MCP implementation
│   ├── authentication/   # Password and authentication flows
│   ├── email/           # Email and receipt generation
│   ├── internationalization/  # Translation and localization
│   ├── monitoring/      # Application Insights and telemetry
│   ├── reviews/         # Product review generation
│   ├── search/          # Semantic search and AI features
│   └── seo/             # SEO implementation
├── testing/             # Testing guides and results
└── data-management/     # Data export and management

🏗️ Architecture

Location: architecture/

✨ Features

AI Agent & MCP

Location: features/ai-agent/

Authentication

Location: features/authentication/

Email & Receipts

Location: features/email/

Internationalization

Location: features/internationalization/

Monitoring & Telemetry

Location: features/monitoring/

Product Reviews

Location: features/reviews/

Search

Location: features/search/

SEO

Location: features/seo/

🧪 Testing

Location: testing/

📊 Data Management

Location: data-management/

🎬 Media

  • adventureworks-demo.gif - Animated demo of the application
  • adventureworks-demo.webm - Video demo

📝 Documentation Guidelines

When adding new documentation:

  1. Choose the right location:

    • architecture/ - System-wide design decisions
    • features/<topic>/ - Feature-specific implementation
    • testing/ - Testing procedures and results
    • data-management/ - Data export/import procedures
  2. Use clear titles and structure:

    • Start with overview/purpose
    • Include prerequisites
    • Provide step-by-step procedures
    • Add troubleshooting section
  3. Keep it up-to-date:

    • Update docs when implementation changes
    • Archive outdated docs with date prefix
    • Link related documents
  4. Cross-reference:

    • Link to related code files
    • Reference other documentation
    • Include working examples

🔗 Quick Links