Add streamlined technical documentation for new developers

[Copilot]

This PR adds streamlined technical documentation to help new developers understand the FGCS architecture and development workflow. The documentation provides essential architectural guidance while remaining concise and maintainable.

What's Added

Enhanced README.md

• Parameter Generation: Added instructions for running generate_param_definitions.py to fetch latest ArduPilot parameter definitions
• Streamlined Content: Focused on essential installation and usage information with development details properly separated into dedicated guides
• Documentation Links: Added prominent documentation section linking to technical guides

Technical Documentation (docs/)

Backend Architecture Guide - Core backend system documentation covering:

• Controllers architecture with functional descriptions of all 9 controllers (Parameters, Mission, Arm, Flight Modes, etc.)
• Drone state management and data flow patterns
• Error handling, logging, and security considerations

Frontend Architecture Guide - Essential frontend system documentation:

• Redux Architecture Overview - General patterns and state organization rather than specific slice implementations
• Component separation - Clear patterns for container vs presentation components
• Popout windows - Architectural differences from main window, IPC communication, and creation guide
• Electron integration and component architecture

Development Guide - Complete developer onboarding:

• Step-by-step setup instructions for new developers
• Git workflow, commit conventions, and code style standards
• Comprehensive testing procedures with pytest examples
• Debugging techniques, performance optimization, and deployment processes

Documentation Philosophy

The documentation emphasizes architectural concepts and maintainable content:

• Conceptual Focus: Controllers and systems described by functionality rather than specific implementation details
• High-Level Patterns: Focus on architectural patterns rather than code that changes frequently
• Maintainable Content: Avoids implementation specifics that require frequent updates
• Separation of Concerns: README for basic usage, dedicated guides for detailed development information

Architecture Diagrams

Added visual representations of the system architecture showing the relationship between:

• Frontend (Electron + React + Redux)
• Backend (Flask + Controllers)
• Drone (Flight Controller)

Navigation and Discoverability

• Documentation Index: docs/README.md provides overview and navigation for all documentation
• Streamlined README: Focused on essential information with clear links to detailed guides
• Cross-references: Documents reference each other for related topics
• Quick Start Guides: Tailored guidance for backend, frontend, and full-stack developers

This documentation provides new developers with essential architectural understanding in a concise, maintainable format that avoids the overhead of frequently-changing implementation details.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[1Blademaster]

@copilot remove any references to Playwright tests, they aren't implemented yet. Can you also remove any exact references to code, i.e. the specific controllers' functions and specific endpoints as these will need to be updated too frequently. Anything that needs to be updated very frequently should be removed.

[Copilot]

@copilot remove any references to Playwright tests, they aren't implemented yet. Can you also remove any exact references to code, i.e. the specific controllers' functions and specific endpoints as th...

I've removed all Playwright references and specific code examples from the documentation as requested. Changes made in commit 9db26c9:

Playwright References Removed From:

• README.md: Replaced specific Playwright setup instructions with generic test status
• DEVELOPMENT_GUIDE.md: Removed entire Playwright testing section and examples

Specific Code Examples Removed/Generalized:

• Controller function signatures → Functional descriptions
• API endpoint URLs → Categorical descriptions
• Detailed code implementations → Conceptual explanations
• Specific method examples → Pattern descriptions

The documentation now focuses on architectural concepts and patterns rather than implementation details that need frequent updates, while still providing comprehensive guidance for new developers.

[1Blademaster]

@copilot Can we keep the readme fairly short with only the most important information. The readme currently includes development info but this is already included in the development guide. From the backend architecture section remove the api endpoints and performance considerations, frontend testing, debugging sections. From the frontend architecture section we don't need to include specific redux slices. We just need a general overview of how slices fit into the frontend. We can probably get rid of the mavlink communication document as well.

[Copilot]

@copilot Can we keep the readme fairly short with only the most important information. The readme currently includes development info but this is already included in the development guide. From the ba...

I've simplified the documentation as requested in commit 681219b:

README.md Simplified:

• Removed entire Development Info section (testing, SITL setup, stack details)
• Kept only essential installation and usage information
• Development details now properly contained in Development Guide

Backend Architecture Streamlined:

• Removed API endpoints section
• Removed performance considerations section
• Focused on core controllers and system design

Frontend Architecture Simplified:

• Removed specific Redux slice details
• Replaced with general Redux patterns overview
• Maintained component architecture and popout windows

MAVLink Communication Document:

• Completely removed as requested
• Updated all references in other documents
• Simplified architecture diagrams

The documentation is now much more concise while still providing essential architectural guidance for new developers.

[Copilot]

Pull Request Overview

This PR adds comprehensive technical documentation to improve developer onboarding and provide architectural guidance for the FGCS project.

• Creates structured documentation system with guides for backend architecture, frontend architecture, and development processes
• Streamlines README.md to focus on essential usage information with clear links to detailed technical guides
• Establishes documentation standards that emphasize maintainable, conceptual content over implementation specifics

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
README.md	Streamlined content focusing on installation and usage, added documentation section linking to technical guides
docs/README.md	Created documentation index providing overview and navigation for all technical guides
docs/DEVELOPMENT_GUIDE.md	Comprehensive developer onboarding guide covering setup, testing, coding standards, and deployment
docs/FRONTEND_ARCHITECTURE.md	Frontend system documentation covering React/Redux architecture and project structure
docs/BACKEND_ARCHITECTURE.md	Backend system documentation covering Flask architecture, controllers, and MAVLink communication

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}