Add canonicalURL to all docs

Author: hamishwillee

de/README.md

@@ -1,3 +1,7 @@
+---
+canonicalUrl: https://docs.px4.io/main/de/README
+---
+
 <div style="float:right; padding:10px; margin-right:20px;"><a href="https://px4.io/"><img src="../assets/site/logo_pro_small.png" title="PX4 Logo" width="180px" /></a></div>
 
 # PX4 Autopilot User Guide ({{ $themeConfig.px4_version }})
@@ -6,7 +10,7 @@
 
 PX4 is the _Professional Autopilot_. Developed by world-class developers from industry and academia, and supported by an active world wide community, it powers all kinds of vehicles from racing and cargo drones through to ground vehicles and submersibles.
 
-:::tip
+:::tip
 This guide contains everything you need to assemble, configure, and safely fly a PX4-based vehicle. Interested in contributing? Check out the [Development](development/development.md) section. :::
 
 ## How Do I Get Started?
@@ -100,7 +104,7 @@ The _Dronecode Calendar_ shows important community events for platform users and
 - [Pacific Time – Tijuana](https://calendar.google.com/calendar/embed?src=linuxfoundation.org_g21tvam24m7pm7jhev01bvlqh8%40group.calendar.google.com&ctz=America%2FTijuana)
 - [Australia – Melbourne/Sydney/Hobart](https://calendar.google.com/calendar/embed?src=linuxfoundation.org_g21tvam24m7pm7jhev01bvlqh8%40group.calendar.google.com&ctz=Australia%2FSydney)
 
-:::tip
+:::tip
 The calendar default timezone is Central European Time (CET).
 
 :::

de/SUMMARY.md

@@ -1 +1,5 @@
+---
+canonicalUrl: https://docs.px4.io/main/de/advanced/README
+---
+
 # Advanced Topics

de/advanced/README.md

@@ -1,57 +1,61 @@
-# Computer Vision (Optical Flow, MoCap, VIO, Avoidance)
-
-[Computer vision](https://en.wikipedia.org/wiki/Computer_vision) techniques enable computers to use visual data to make sense of their environment.
-
-PX4 uses computer vision systems (primarily running on [Companion Computers](../companion_computer/README.md)) in order to support the following features:
-
-- [Optical Flow](#optical-flow) provides 2D velocity estimation (using a downward facing camera and a downward facing distance sensor).
-- [Motion Capture](#motion-capture) provides 3D pose estimation using a vision system that is _external_ to the vehicle. It is primarily used for indoor navigation.
-- [Visual Inertial Odometry](#visual-inertial-odometry-vio) provides 3D pose and velocity estimation using an onboard vision system and IMU. It is used for navigation when global position information is absent or unreliable.
-- [Obstacle Avoidance](../computer_vision/obstacle_avoidance.md) provides full navigation around obstacles when flying a planned path (currently missions are supported). This uses [PX4/PX4-Avoidance](https://github.com/PX4/PX4-Avoidance) running on a companion computer.
-- [Collision Prevention](../computer_vision/collision_prevention.md) is used to stop vehicles before they can crash into an obstacle (primarily when flying in manual modes).
-
-:::tip
-The [PX4 Vision Autonomy Development Kit](../complete_vehicles/px4_vision_kit.md) (Holybro) is a robust and inexpensive kit for developers working with computer vision on PX4. It comes with no pre-installed software, but does include an example implementation of obstacle avoidance to demonstrate the capabilities of the platform.
-:::
-
-## Motion Capture
-
-Motion Capture (MoCap) is a technique for estimating the 3D _pose_ (position and orientation) of a vehicle using a positioning mechanism that is _external_ to the vehicle. MoCap systems most commonly detect motion using infrared cameras, but other types of cameras, Lidar, or Ultra Wideband (UWB) may also be used.
-
-:::note
-MoCap is commonly used to navigate a vehicle in situations where GPS is absent (e.g. indoors), and provides position relative to a _local_ coordinate system.
-:::
-
-For information about MoCap see:
-
-- [External Position Estimation](../ros/external_position_estimation.md)
-- [Flying with Motion Capture (VICON, Optitrack)](../tutorials/motion-capture.md)
-- [EKF > External Vision System](../advanced_config/tuning_the_ecl_ekf.md#external-vision-system)
-
-## Visual Inertial Odometry (VIO)
-
-Visual Inertial Odometry (VIO) is used for estimating the 3D _pose_ (position and orientation) and _velocity_ of a moving vehicle relative to a _local_ starting position. It is commonly used to navigate a vehicle in situations where GPS is absent (e.g. indoors) or unreliable (e.g. when flying under a bridge).
-
-VIO uses [Visual Odometry](https://en.wikipedia.org/wiki/Visual_odometry) to estimate vehicle _pose_ from visual information, combined with inertial measurements from an IMU (to correct for errors associated with rapid vehicle movement resulting in poor image capture).
-
-:::note
-One difference between VIO and [MoCap](#motion-capture) is that VIO cameras/IMU are vehicle-based, and additionally provide velocity information.
-:::
-
-For information about configuring VIO on PX4 see:
-
-- [EKF > External Vision System](../advanced_config/tuning_the_ecl_ekf.md#external-vision-system)
-- [T265 Setup guide](../peripherals/camera_t265_vio.md)
-
-## Optical Flow
-
-[Optical Flow](../sensor/optical_flow.md) provides 2D velocity estimation (using a downward facing camera and a downward facing distance sensor).
-
-For information about optical flow see:
-
-- [Optical Flow](../sensor/optical_flow.md)
-- [EKF > Optical Flow](../advanced_config/tuning_the_ecl_ekf.md#optical-flow)
-
-## External Resources
-
-- [XTDrone](https://github.com/robin-shaun/XTDrone/blob/master/README.en.md) - ROS + PX4 simulation environment for computer vision. The [XTDrone Manual](https://www.yuque.com/xtdrone/manual_en) has everything you need to get started!
+---
+canonicalUrl: https://docs.px4.io/main/de/advanced/computer_vision
+---
+
+# Computer Vision (Optical Flow, MoCap, VIO, Avoidance)
+
+[Computer vision](https://en.wikipedia.org/wiki/Computer_vision) techniques enable computers to use visual data to make sense of their environment.
+
+PX4 uses computer vision systems (primarily running on [Companion Computers](../companion_computer/README.md)) in order to support the following features:
+
+- [Optical Flow](#optical-flow) provides 2D velocity estimation (using a downward facing camera and a downward facing distance sensor).
+- [Motion Capture](#motion-capture) provides 3D pose estimation using a vision system that is _external_ to the vehicle. It is primarily used for indoor navigation.
+- [Visual Inertial Odometry](#visual-inertial-odometry-vio) provides 3D pose and velocity estimation using an onboard vision system and IMU. It is used for navigation when global position information is absent or unreliable.
+- [Obstacle Avoidance](../computer_vision/obstacle_avoidance.md) provides full navigation around obstacles when flying a planned path (currently missions are supported). This uses [PX4/PX4-Avoidance](https://github.com/PX4/PX4-Avoidance) running on a companion computer.
+- [Collision Prevention](../computer_vision/collision_prevention.md) is used to stop vehicles before they can crash into an obstacle (primarily when flying in manual modes).
+
+:::tip
+The [PX4 Vision Autonomy Development Kit](../complete_vehicles/px4_vision_kit.md) (Holybro) is a robust and inexpensive kit for developers working with computer vision on PX4. It comes with no pre-installed software, but does include an example implementation of obstacle avoidance to demonstrate the capabilities of the platform.
+:::
+
+## Motion Capture
+
+Motion Capture (MoCap) is a technique for estimating the 3D _pose_ (position and orientation) of a vehicle using a positioning mechanism that is _external_ to the vehicle. MoCap systems most commonly detect motion using infrared cameras, but other types of cameras, Lidar, or Ultra Wideband (UWB) may also be used.
+
+:::note
+MoCap is commonly used to navigate a vehicle in situations where GPS is absent (e.g. indoors), and provides position relative to a _local_ coordinate system.
+:::
+
+For information about MoCap see:
+
+- [External Position Estimation](../ros/external_position_estimation.md)
+- [Flying with Motion Capture (VICON, Optitrack)](../tutorials/motion-capture.md)
+- [EKF > External Vision System](../advanced_config/tuning_the_ecl_ekf.md#external-vision-system)
+
+## Visual Inertial Odometry (VIO)
+
+Visual Inertial Odometry (VIO) is used for estimating the 3D _pose_ (position and orientation) and _velocity_ of a moving vehicle relative to a _local_ starting position. It is commonly used to navigate a vehicle in situations where GPS is absent (e.g. indoors) or unreliable (e.g. when flying under a bridge).
+
+VIO uses [Visual Odometry](https://en.wikipedia.org/wiki/Visual_odometry) to estimate vehicle _pose_ from visual information, combined with inertial measurements from an IMU (to correct for errors associated with rapid vehicle movement resulting in poor image capture).
+
+:::note
+One difference between VIO and [MoCap](#motion-capture) is that VIO cameras/IMU are vehicle-based, and additionally provide velocity information.
+:::
+
+For information about configuring VIO on PX4 see:
+
+- [EKF > External Vision System](../advanced_config/tuning_the_ecl_ekf.md#external-vision-system)
+- [T265 Setup guide](../peripherals/camera_t265_vio.md)
+
+## Optical Flow
+
+[Optical Flow](../sensor/optical_flow.md) provides 2D velocity estimation (using a downward facing camera and a downward facing distance sensor).
+
+For information about optical flow see:
+
+- [Optical Flow](../sensor/optical_flow.md)
+- [EKF > Optical Flow](../advanced_config/tuning_the_ecl_ekf.md#optical-flow)
+
+## External Resources
+
+- [XTDrone](https://github.com/robin-shaun/XTDrone/blob/master/README.en.md) - ROS + PX4 simulation environment for computer vision. The [XTDrone Manual](https://www.yuque.com/xtdrone/manual_en) has everything you need to get started!

de/advanced/computer_vision.md

@@ -1,12 +1,16 @@
-# Unsupported Developer Toolchains
-
-This section contains topics about _unsupported_ development platforms and tools (i.e. tools for which the code dev team are unlikely to be able to provide much advice).
-
-:::tip
-See [Toolchain Installation](../dev_setup/dev_env.md) for information about the environments and tools we do support!
-:::
-
-:::warning
-The environments and tools in this section are rarely tested and may not work.
-You should not use these unless you are and expert with the environment and capable of debugging the environment yourself.
-:::
+---
+canonicalUrl: https://docs.px4.io/main/de/advanced/dev_env_unsupported
+---
+
+# Unsupported Developer Toolchains
+
+This section contains topics about _unsupported_ development platforms and tools (i.e. tools for which the code dev team are unlikely to be able to provide much advice).
+
+:::tip
+See [Toolchain Installation](../dev_setup/dev_env.md) for information about the environments and tools we do support!
+:::
+
+:::warning
+The environments and tools in this section are rarely tested and may not work.
+You should not use these unless you are and expert with the environment and capable of debugging the environment yourself.
+:::