3b8019f37a
* fix(docs): bypass VitePress router interception in DynamicNav links VitePress installs a global click interceptor that catches same-origin <a> clicks and routes them through Vue Router. Cross-version links (e.g. /v1.17/en/ from /main/en/) share the origin but are separate deployments, so Vue Router fails to resolve them and navigation is silently swallowed. Fix by calling window.location.href directly with @click.prevent on all nav links. Signed-off-by: Hamish Willee <hamishwillee@gmail.com> * refactor(docs): use VitePress internal nav components in DynamicNav Replace the hand-rolled dropdown/link rendering with VitePress's own VPNavBarMenuLink, VPNavBarMenuGroup, VPNavScreenMenuLink, and VPNavScreenMenuGroup. This removes ~140 lines of custom CSS and all manual click/flyout handling; VitePress styles and VPFlyout behaviour are inherited for free. The navigation bug (same-origin links swallowed by Vue Router) is also fixed by this approach: VPLink classifies any https:// href as external and renders a plain <a> tag, bypassing the router interceptor entirely. Remote URL and localStorage key are now read from themeConfig (dynamicNavUrl, dynamicNavCacheKey) so the component can be dropped into any VitePress repo with just a config change. Signed-off-by: Hamish Willee <hamishwillee@gmail.com> * refactor(docs): derive DynamicNav cache key from URL by default Use the remote URL as the localStorage key when dynamicNavCacheKey is not set. This avoids the need to declare a key in config, keeps the key unique per data source automatically, and means all deployed versions of a site (same origin, different base paths) naturally share one cache entry — which is the desired behaviour. Signed-off-by: Hamish Willee <hamishwillee@gmail.com> * chore(docs): remove redundant nav:[] from themeConfig VitePress renders no menu items when nav is omitted, so the explicit empty array adds no value now that all items come from DynamicNav. Signed-off-by: Hamish Willee <hamishwillee@gmail.com> * fix(docs): restore display:flex on DynamicNav bar wrapper Removing the scoped styles during the VitePress-internal-components refactor also removed the flex layout on the wrapper div, causing nav items to stack vertically instead of in a row. Signed-off-by: Hamish Willee <hamishwillee@gmail.com> * refactor(docs): replace local DynamicNav with vp-dynamic-nav npm package Removes the in-tree DynamicNav.vue and wires up the published vp-dynamic-nav package instead. navbar.json is imported in config.mjs and passed as dynamicNavInitial so it remains the single source of truth for both the initial render and the remote fetch target. Signed-off-by: Hamish Willee <hamishwillee@gmail.com> --------- Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
The autopilot stack the industry builds on.
About
PX4 is an open-source autopilot stack for drones and unmanned vehicles. It supports multirotors, fixed-wing, VTOL, rovers, and many more experimental platforms from racing quads to industrial survey aircraft. It runs on NuttX, Linux, and macOS. Licensed under BSD 3-Clause.
Why PX4
Modular architecture. PX4 is built around uORB, a DDS-compatible publish/subscribe middleware. Modules are fully parallelized and thread safe. You can build custom configurations and trim what you don't need.
Wide hardware support. PX4 runs on a wide range of autopilot boards and supports an extensive set of sensors, telemetry radios, and actuators through the Pixhawk ecosystem.
Developer friendly. First-class support for MAVLink and DDS / ROS 2 integration. Comprehensive SITL simulation, hardware-in-the-loop testing, and log analysis tools. An active developer community on Discord and the weekly dev call.
Vendor neutral governance. PX4 is hosted under the Dronecode Foundation, part of the Linux Foundation. Business-friendly BSD-3 license. No single vendor controls the roadmap.
Supported Vehicles
 Multicopter |
 Fixed Wing |
 VTOL |
 Rover |
…and many more: helicopters, autogyros, airships, submarines, boats, and other experimental platforms. These frames have basic support but are not part of the regular flight-test program. See the full airframe reference.
Try PX4
Run PX4 in simulation with a single command. No build tools, no dependencies beyond Docker:
docker run --rm -it -p 14550:14550/udp px4io/px4-sitl:latest
Open QGroundControl and fly. See PX4 Simulation Quickstart for more options.
Build from Source
git clone https://github.com/PX4/PX4-Autopilot.git --recursive
cd PX4-Autopilot
make px4_sitl
Note
See the Development Guide for toolchain setup and build options.
Documentation & Resources
| Resource | Description |
|---|---|
| User Guide | Build, configure, and fly with PX4 |
| Developer Guide | Modify the flight stack, add peripherals, port to new hardware |
| Airframe Reference | Full list of supported frames |
| Autopilot Hardware | Compatible flight controllers |
| Release Notes | What's new in each release |
| Contribution Guide | How to contribute to PX4 |
Community
- Weekly Dev Call — open to all developers (Dronecode calendar)
- Discord — Join the Dronecode server
- Discussion Forum — PX4 Discuss
- Maintainers — see
MAINTAINERS.md - Contributor Stats — LFX Insights
Contributing
We welcome contributions of all kinds — bug reports, documentation, new features, and code reviews. Please read the Contribution Guide to get started.
Citation
If you use PX4 in academic work, please cite it. BibTeX:
@software{px4_autopilot,
author = {Meier, Lorenz and {The PX4 Contributors}},
title = {{PX4 Autopilot}},
publisher = {Zenodo},
doi = {10.5281/zenodo.595432},
url = {https://px4.io}
}
The DOI above is a Zenodo concept DOI that always resolves to the latest release. For a version-pinned citation, see the Zenodo record or our CITATION.cff.
Governance
The PX4 Autopilot project is hosted by the Dronecode Foundation, a Linux Foundation Collaborative Project. Dronecode holds all PX4 trademarks and serves as the project's legal guardian, ensuring vendor-neutral stewardship — no single company owns the name or controls the roadmap. The source code is licensed under the BSD 3-Clause license, so you are free to use, modify, and distribute it in your own projects.
