Skip to content

Latest commit

Β 

History

History
82 lines (60 loc) Β· 3.45 KB

File metadata and controls

82 lines (60 loc) Β· 3.45 KB

Wisemapping Backend Documentation

This directory contains comprehensive documentation for the Wisemapping backend API and services.

πŸ“ Directory Structure

backend/
β”œβ”€β”€ README.md                    # This file - Backend documentation index
β”œβ”€β”€ rest-api/                    # REST API documentation
β”‚   └── REST Services.md        # Legacy REST services documentation
β”œβ”€β”€ telemetry/                   # Telemetry and metrics documentation
β”‚   └── Telemetry.md            # OpenTelemetry and metrics implementation
└── openapi-specs/              # OpenAPI specifications
    β”œβ”€β”€ openapi.yaml            # Main OpenAPI specification
    β”œβ”€β”€ mindmap-endpoints.yaml  # Mindmap-specific endpoints
    └── collaboration-admin-endpoints.yaml # Admin and collaboration endpoints

πŸ“š Documentation Overview

REST API Documentation

Telemetry & Monitoring

API Specifications

πŸš€ Quick Start

  1. For API Integration: Start with the Main API Documentation
  2. For OpenAPI Tools: Use the OpenAPI Specification
  3. For Monitoring: Check the Telemetry Documentation
  4. For Legacy Integration: Refer to REST Services

πŸ”§ Development

Adding New Documentation

When adding new backend documentation:

  1. API Documentation: Add to the main README.md
  2. OpenAPI Specs: Update the appropriate YAML files in openapi-specs/
  3. Telemetry: Update Telemetry.md for metrics changes
  4. Legacy Docs: Update REST Services.md for legacy endpoints

Documentation Standards

  • Use Markdown format for all documentation
  • Include code examples where applicable
  • Keep OpenAPI specifications up to date
  • Document all new endpoints and changes
  • Include authentication requirements
  • Provide error handling examples

πŸ“– Related Documentation

🀝 Contributing

When contributing to the backend documentation:

  1. Follow the existing structure and format
  2. Update relevant sections when making API changes
  3. Include examples for new endpoints
  4. Test all code examples
  5. Update the OpenAPI specifications

πŸ“ž Support

For questions about the backend API: