doc: replace deprecated urls

Author: LasseRosenow

MAINTAINING.md

@@ -182,7 +182,7 @@ announcement can be skipped and the fix merged once at least two ACKs are
 there.
 
 [list of maintainers]: https://riot-os.org/maintainers.html
-[Best Practices]: https://doc.riot-os.org/dev-best-practices.html
-[Comparing build sizes]: https://doc.riot-os.org/advanced-build-system-tricks.html#comparing-build-sizes
-[Coding Conventions]: CODING_CONVENTIONS.md
-[Code of Conduct]: https://github.com/RIOT-OS/RIOT/blob/master/CODE_OF_CONDUCT.md
+[Best Practices]: https://guide.riot-os.org/misc/dev_best_practices/
+[Comparing build sizes]: https://guide.riot-os.org/build-system/advanced_build_system_tricks/#comparing-build-sizes
+[Coding Conventions]: https://guide.riot-os.org/c_tutorials/coding_conventions/
+[Code of Conduct]: https://guide.riot-os.org/general/code_of_conduct/

Makefile

@@ -62,7 +62,7 @@ define welcome_message
 	@echo "Usually, you should run 'make' in your application's directory instead."
 	@echo ""
 	@echo "Please see our Quick Start Guide at:"
-	@echo "    https://doc.riot-os.org/getting-started.html"
+	@echo "    https://guide.riot-os.org/getting-started/installing/"
 	@echo "You can ask questions or discuss with other users on our forum:"
 	@echo "    https://forum.riot-os.org"
 	@echo ""

cpu/esp32/doc.md

@@ -494,7 +494,7 @@ The easiest way to use the ESP32 toolchain is to use the RIOT Docker build
 image. It is specially prepared for building RIOT applications for various
 platforms and already has all the required tools and packages installed.
 Details on how to setup Docker can be found in section
-[Getting Started](https://doc.riot-os.org/getting-started.html#docker).
+[Build in Docker](https://guide.riot-os.org/build-system/build-in-docker/).
 
 The building process using Docker comprises two steps:
 
@@ -522,7 +522,7 @@ $ BUILD_IN_DOCKER=1 make flash BOARD=...
 ### Prerequisites
 
 In addition to the common tools defined in section
-[Getting Started - Common Tools](https://doc.riot-os.org/getting-started.html#compiling-riot),
+[Getting Started - Setup Development Environment](https://guide.riot-os.org/getting-started/installing/),
 the following tools or packages are required to install and use the ESP32
 toolchain (Debian/Ubuntu package names):
 

dist/tools/usb-serial/README.md

@@ -77,7 +77,7 @@ By adding
 
 to the `Makefile.include` of your board, running `make MOST_RECENT_PORT=1 term`
 will connect to the most recently connected board matching the provided
-filters. Refer to https://api.riot-os.org/flashing.html#multiple-boards-simple
+filters. Refer to https://guide.riot-os.org/build-system/flashing/#handling-multiple-boards-simplest-approach
 for more details.
 
 `list-ttys.sh`

doc/guides/build-system/kconfig.md

@@ -450,7 +450,7 @@ reserved for the cases described below:
 | `CPU_CORE_` | Models a CPU core |
 | `CPU_FAM_` | Models a family of CPUs |
 | `CPU_MODEL_` | Models a particular model of CPU |
-| `USEMODULE_` | Models a [RIOT module](https://doc.riot-os.org/creating-modules.html#creating-modules). Generated from `USEMODULE` variable |
+| `USEMODULE_` | Models a [RIOT module](https://guide.riot-os.org/advanced_tutorials/creating_modules/). Generated from `USEMODULE` variable |
 | `USEPKG_` | Models an [external package](https://doc.riot-os.org/group__pkg.html). Generated from `USEPKG` variable |
 
 ---

doc/guides/general/structure.mdx

@@ -75,7 +75,7 @@ scheme. Examples for this is code shared across architectures (e.g.
 `cortexm_common`, `msp430_comon`) or code shared among vendors (e.g.
 `stm32_common`).
 
-See [CPU](https://doc.riot-os.org/build-system-basics.html#cpu) for more detailed information.
+See [CPU](https://guide.riot-os.org/build-system/build_system_basics/#cpucpu_model) for more detailed information.
 
 drivers
 -------

examples/basic/subfolders/README.md

@@ -41,7 +41,7 @@ i.e., including the modules that are part of RIOT itself.
 
 If not manually specified via `SRC`, all source files which reside
 directly in the module's directory are considered part of the module.
-RIOT modules are also described in greater detail [in the documentation](https://doc.riot-os.org/creating-modules.html).
+RIOT modules are also described in greater detail [in the documentation](https://guide.riot-os.org/advanced_tutorials/creating_modules/).
 
 Two lines need to be added to the application's Makefile in order to compile and use the module:
 
@@ -52,7 +52,7 @@ USEMODULE += module
 
 The path added to `EXTERNAL_MODULE_DIRS` is the parent directory of the external module,
 while the string added to `USEMODULE` has to match the module's directory name.
-External modules are described in greater detail [in the documentation](https://doc.riot-os.org/creating-an-application.html#autotoc_md2308).
+External modules are described in greater detail [in the documentation](https://guide.riot-os.org/advanced_tutorials/creating_application/#external-modules).
 
 
 ### Subfolders

makefiles/cargo-targets.inc.mk

@@ -41,10 +41,10 @@ $(CARGO_COMPILE_COMMANDS): $(BUILDDEPS)
 
 cargo-preflight: FORCE
 	@command -v cargo >/dev/null || ($(COLOR_ECHO) \
-		'$(COLOR_RED)Error: `cargo` command missing to build Rust modules.$(COLOR_RESET) Please install as described on <https://doc.riot-os.org/using-rust.html>.' ;\
+		'$(COLOR_RED)Error: `cargo` command missing to build Rust modules.$(COLOR_RESET) Please install as described on <https://guide.riot-os.org/rust_tutorials/rust_in_riot/>.' ;\
 		exit 1)
 	@command -v $${C2RUST:-c2rust} >/dev/null || ($(COLOR_ECHO) \
-		'$(COLOR_RED)Error: `'$${C2RUST:-c2rust}'` command missing to build Rust modules.$(COLOR_RESET) Please install as described on <https://doc.riot-os.org/using-rust.html>.' ;\
+		'$(COLOR_RED)Error: `'$${C2RUST:-c2rust}'` command missing to build Rust modules.$(COLOR_RESET) Please install as described on <https://guide.riot-os.org/rust_tutorials/rust_in_riot/>.' ;\
 		exit 1)
 	@command -v rustup >/dev/null || ($(COLOR_ECHO) \
 		'$(COLOR_RED)Error: `rustup` command missing.$(COLOR_RESET) While it is not essential for building Rust modules, it is the only known way to install the target core libraries (or nightly for -Zbuild-std) needed to do so. If you do think that building should be possible, please edit this file, and file an issue about building Rust modules with the installation method you are using -- later checks in this file, based on rustup, will need to be adjusted for that.' ;\

tests/net/gnrc_dhcpv6_client/Makefile

@@ -43,7 +43,7 @@ include $(RIOTBASE)/Makefile.include
 
 # export IFACE variable to environment of dhcpv6_server and
 # test-with-config/check-config rules
-# see: https://doc.riot-os.org/build-system-basics.html#variable-declaration-guidelines
+# see: https://guide.riot-os.org/build-system/build_system_basics/#variables-declaration-guidelines
 $(call target-export-variables,dhcpv6_server test-with-config/check-config,IFACE)
 
 dhcpv6_server: