docs: add “Why Rugpi?” page

www/docusaurus.config.ts

@@ -72,6 +72,11 @@ const config: Config = {
           label: "Supported Devices",
           position: "left",
         },
+        {
+          to: "/why",
+          label: "Why Rugpi?",
+          position: "left",
+        },
         {
           type: "doc",
           docId: "getting-started",

www/src/pages/why.mdx

@@ -0,0 +1,19 @@
+# Why Rugpi?
+
+While many excellent tools are already available for building images, updating systems, and managing state, integrating them into a robust setup can be challenging.
+Rugpi strives to simplify this process by bundling all essential functionalities into a cohesive package, allowing you to focus on what matters most to you and your users.
+We believe that building innovative devices shouldn't be as complicated as it often is today.
+Although Rugpi may offer less flexibility and configurability than standalone solutions, it excels at delivering a robust base for your device right out of the box.
+
+In case Rugpi does not suit your needs, here are a few standalone solutions that you may want to consider:
+
+**Building Images:**
+- [Debos](https://github.com/go-debos/debos): Build images based on different binary distributions.
+- [edi](https://www.get-edi.io): Build images based on Ubuntu and Debian.
+- [Yocto Project](https://www.yoctoproject.org): Build images from source.
+- [Buildroot](https://www.buildroot.org): Build images from source.
+
+**Update Solutions:**
+- [RAUC](https://rauc.io): Safe and secure OTA updates for embedded Linux.
+- [Mender](https://mender.io): Over-the-air software updates for IoT devices.
+- [SWUpdate](https://sbabic.github.io/swupdate/swupdate.html): Software updates for embedded systems.