turash/docs/README.md
Damir Mukimov 000eab4740
Major repository reorganization and missing backend endpoints implementation
Repository Structure:
- Move files from cluttered root directory into organized structure
- Create archive/ for archived data and scraper results
- Create bugulma/ for the complete application (frontend + backend)
- Create data/ for sample datasets and reference materials
- Create docs/ for comprehensive documentation structure
- Create scripts/ for utility scripts and API tools

Backend Implementation:
- Implement 3 missing backend endpoints identified in gap analysis:
  * GET /api/v1/organizations/{id}/matching/direct - Direct symbiosis matches
  * GET /api/v1/users/me/organizations - User organizations
  * POST /api/v1/proposals/{id}/status - Update proposal status
- Add complete proposal domain model, repository, and service layers
- Create database migration for proposals table
- Fix CLI server command registration issue

API Documentation:
- Add comprehensive proposals.md API documentation
- Update README.md with Users and Proposals API sections
- Document all request/response formats, error codes, and business rules

Code Quality:
- Follow existing Go backend architecture patterns
- Add proper error handling and validation
- Match frontend expected response schemas
- Maintain clean separation of concerns (handler -> service -> repository)
2025-11-25 06:01:16 +01:00

47 lines
2.1 KiB
Markdown

# Documentation
This directory contains all project documentation organized by category.
## Structure
- **[app/](app/)** - **🏗️ Core Application Documentation** (First Priority)
- **[business/](business/)** - Business strategy, branding, funding
- **[implementation/](implementation/)** - Implementation plans and reports
- **[concept/](concept/)** - Strategic concept and research
- **[dev_guides/](dev_guides/)** - Development guides
- **[api/](api/)** - API documentation
## 🚀 Quick Start for Developers
**Start Here**: [Application Documentation](app/) - Core docs for understanding and working with Turash
## 🚨 Critical: Frontend-Backend Gap Analysis
**⚠️ IMPORTANT**: Before deploying, read the **[Gap Analysis Report](gap-analysis-report.md)** - identifies critical missing backend endpoints that break frontend functionality.
## 🚀 Quick Start for Developers
**Start Here**: [Application Documentation](app/) - Core docs for understanding and working with Turash
## 📖 Documentation by Role
### For Application Developers
- **[API Overview](api/overview.md)** - API architecture and design principles
- **[MVP Concept](app/mvp_concept.md)** - Complete application specification
- **[Database Structure](app/database_structure.md)** - Data models and relationships
### For API Integration
- **[Organizations API](api/organizations.md)** - Complete organization management
- **[Resources API](api/resources.md)** - Resource flow management
- **[Matching API](api/matching.md)** - Resource matching and optimization
- **[API Reference](api/README.md)** - All endpoints and examples
- **[Gap Analysis Report](gap-analysis-report.md)** - **🔴 Critical missing endpoints**
### For Business Stakeholders
- [Turash Branding](business/turash_branding.md) - Brand identity and positioning
- [Funding Strategy](business/funding/) - EU and international funding programs
### For Implementation Teams
- [Architecture Refactoring Plan](implementation/ARCHITECTURAL_REFACTORING_PLAN.md) - Backend modernization
- [Implementation Gap Report](implementation/IMPLEMENTATION_GAP_REPORT.md) - Current vs. required features