Merge pull request #21792 from LasseRosenow/doxygen-deprecate-getting-started

doc: deprecate Doxygen `Getting Started` and add CoAP guide

Author: AnnsAnns

dist/tools/code_in_guides_check/check_for_code.sh

@@ -38,10 +38,13 @@ parse_code_block() {
 
     # Check if this code exists in any file in the source directory
     found=0
-    for src_file in "$SOURCE_DIR"/*; do
-        # Skip if not a regular file
-        [ -f "$src_file" ] || continue
-
+    # Exclude `/bin/` folders
+    INPUT_FILES=$(
+        find "$SOURCE_DIR" \
+        -type d -name "bin" -prune\
+        -or -type f -print\
+    )
+    for src_file in $INPUT_FILES;  do
         # Read the file content
         src_content=$(cat "$src_file")
 

doc/doxygen/src/getting-started.md

@@ -1,6 +1,9 @@
-Getting started                                              {#getting-started}
+Getting started (Deprecated)                                             {#getting-started}
 ===============
 
+@deprecated Guides have moved to the [Guide Site](https://guide.riot-os.org/getting-started/installing/).
+This page will be removed after release 2026.04.
+
 [TOC]
 
 @deprecated See [Setup Guide](https://guide.riot-os.org/getting-started/installing/#architecture-specific-requirements) on the RIOT Guide Site for the latest information. This section will be removed after release 2025.11.
@@ -17,28 +20,11 @@ Building and executing an example           {#building-and-executing-an-example}
 
 Configuring an application                         {#configuring-an-application}
 --------------------------
-Many modules in RIOT offer configuration options that will be considered during
-compile-time.They are modeled as macros that can be overridden by the user.
-Currently there are two ways of doing this: using `CFLAGS` or via
-@ref kconfig-in-riot "Kconfig" (the last one is currently only possible for a
-subset of modules).
-
-For instructions on how to configure via `CFLAGS` check the
-@ref config "identified compile-time configurations". To learn how to use
-Kconfig in RIOT, please refer to the
-[User's guide to configure with Kconfig](https://guide.riot-os.org/build-system/kconfig/#configure-using-menuconfig).
+@deprecated See [Configuring an Application](https://guide.riot-os.org/advanced_tutorials/creating_application/#configuring-an-application) on the RIOT Guide Site for the latest information. This section will be removed after release 2026.04.
 
 Default configurations                                 {#default-configurations}
 ----------------------
-When devices have a common access interface, having a default configuration to
-enable them across platforms, without having to explicitly specify which modules
-to include, comes in handy. For this, two pseudomodules are defined:
-
-- `saul_default`: will enable all the drivers of sensors and actuators that are
-present in the target platform.
-
-- `netdev_default`: will enable all the drivers of network devices
-present in the target platform.
+@deprecated See [Default Configurations](https://guide.riot-os.org/advanced_tutorials/creating_application/#default-configurations) on the RIOT Guide Site for the latest information. This section will be removed after release 2026.04.
 
 Use Docker to build RIOT                           {#docker}
 ========================
@@ -48,37 +34,9 @@ Use Docker to build RIOT                           {#docker}
 Generating compile_commands.json e.g. for code completion in IDEs
 =================================================================
 
-See [Setup Guide](https://guide.riot-os.org/getting-started/installing/#using-vs-code-for-development) for a guide on how to set up VS Code for RIOT development using the `compile_commands.json` file.
-
-This target will honor the variables controlling the build process such as `BOARD`, `TOOLCHAIN`,
-`DEVELHELP`, etc. just like the usual build process. This works without actual compilation. By
-default, the `compile_commands.json` is placed in the RIOT base directory. This behavior can be
-overwritten using the `COMPILE_COMMANDS_PATH` variable by specifying the full absolute path
-(including file name) of the `compile_commands.json` instead.
-
-***Note:*** By default, the built-in include search directories of GCC will be explicitly added
-and flags incompatible with `clangd` will be dropped. This will allow using `clangd` as language
-server out of the box. If this is not desired, run `export COMPILE_COMMANDS_FLAGS=""` to turn
-modification of the compile commands off. For a list of available flags, run
-`./dist/tools/compile_commands/compile_commands.py --help` in the RIOT base directory.
+@deprecated See [Generating compile_commands.json](https://guide.riot-os.org/getting-started/installing/#generating-compile_commandsjson-eg-for-code-completion-in-ides) on the RIOT Guide Site for the latest information. This section will be removed after release 2026.04.
 
 Using the native port with networking
 =====================================
 
-If you compile RIOT for the native cpu and include the `netdev_tap` module,
-you can specify a network interface like this: `PORT=tap0 make term`
-
-Setting up a tap network
-------------------------
-
-There is a shell script in `RIOT/dist/tools/tapsetup` called `tapsetup` which
-you can use to create a network of tap interfaces.
-
-*USAGE*
-
-To create a bridge and two (or `count` at your option) tap interfaces:
-~~~~~~~{.sh}
-    sudo ./dist/tools/tapsetup/tapsetup [-c [<count>]]
-~~~~~~~
-
-A detailed example can be found in `examples/networking/gnrc/gnrc_networking`.
+@deprecated See [Networking](https://guide.riot-os.org/c_tutorials/networking/) on the RIOT Guide Site for the latest information. This section will be removed after release 2026.04.

doc/guides/advanced_tutorials/creating_application.md

@@ -95,6 +95,60 @@ USEMODULE += gnrc_udp
 
 Modules typically pull in all required dependencies themselves.
 
+### Configuring an Application
+
+Many modules in RIOT offer configuration options that will be considered during
+compile-time. They are modeled as macros that can be overridden by the user.
+Currently there are three ways of doing this: Using `CFLAGS`, `pseudomodules`
+and [Kconfig](https://guide.riot-os.org/build-system/kconfig) (the last one is
+currently only possible for a subset of modules).
+
+#### CFLAGS
+
+`CFLAGS` can be set in your `Makefile` to configure the values of `defines`.
+Make sure to not override the `CFLAGS` variable and only extend it using
+the `+=` operator.
+
+For example, to increase the stack size of the main thread,
+your Makefile needs to contain this line:
+
+```makefile
+CFLAGS += -DTHREAD_STACKSIZE_MAIN=2048
+```
+
+For a list of all compile time configurations check the
+[API Documentation](https://doc.riot-os.org/group__config.html).
+
+#### Kconfig
+
+To learn how to use [Kconfig](https://guide.riot-os.org/build-system/kconfig)
+in RIOT, please refer to the
+[User Guide to Configure with Kconfig](https://guide.riot-os.org/build-system/kconfig/#user-guide-to-configure-with-kconfig).
+
+#### Pseudomodules
+
+When devices have a common access interface, having a default configuration to
+enable them across platforms, without having to explicitly specify which modules
+to include, comes in handy. For this, `pseudomodules` are defined:
+
+##### SAUL Default
+
+Will enable all the drivers of sensors and actuators that are
+present in the target platform.
+
+```makefile
+USEMODULE += saul_default
+```
+
+##### Netdev Default
+
+Will enable all the drivers of network devices
+present in the target platform.
+
+```makefile
+USEMODULE += netdev_default
+```
+
 ## Including Source Files in Subfolders
 
 By default, all source files in an application's (or any RIOT module's) directory