Release 1.0
Release 1.0 establishes the first structured baseline for the VECROS documentation site.
Summary
This release organizes the docs around VECROS product families and introduces the core reference pages users need when evaluating, setting up, or integrating VECROS hardware.
Added
- Product overview pages for JETCORE, JETCORE FC, MINI CC Board, and Development Drones.
- Hardware reference pages for dimensions, pinouts, and wiring diagrams.
- Setup guides for flashing, CAN setup, and MAVLink bridging where applicable.
- Warranty pages for supported hardware products.
- Community pages for support, documentation contribution, terminology, licenses, and developer calls.
- Company pages for About, Certifications, and VECROS logo assets.
Changed
- The documentation site is organized with autogenerated Docusaurus sidebars.
- Product cards on the homepage link directly to generated product-category pages.
- The release section now provides a central place for tracking documentation and product changes.
Fixed
- Corrected spelling, grammar, and terminology issues across community, warranty, and introductory pages.
- Fixed the site favicon path to use the existing SVG asset.
- Fixed the custom font URL so Docusaurus can serve the bundled font correctly.
- Removed a broken placeholder link from the homepage product cards.
Known Issues
- Some product pages still need deeper release metadata, including hardware revision, firmware version, tested JetPack version, and compatible module details.
- Some advanced setup instructions refer users to Vecros support or repositories instead of providing a complete step-by-step flow.
- The release history before 1.0 is not documented in this site.
Compatibility Notes
Where Jetson-based setup is documented, users should select the JetPack version that matches their Jetson module and project requirements. If a product requires custom firmware, drivers, or board-specific images, confirm the correct package with Vecros support before flashing.
Upgrade Guidance
No migration is required for Release 1.0. Users should treat this as the baseline documentation release and follow the product-specific guides for setup and integration.