docs: remove guides

Author: LukasGentele

docs/pages/configuration/images/image-definition/dockerfile.mdx

@@ -31,7 +31,3 @@ images:
 - The second image is built using the Dockerfile in `./frontend/Dockerfile` and the context path `./frontend/`.
 - Switching the `context` for image `frontend` assures that a statement like `ADD file.txt` or  `COPY file.txt .` in `./frontend/Dockerfile` uses the local file `./frontend/file.txt` instead of `./file.txt`.
 - In this example, it is useful to have a `./.dockerignore` file, which ignores the `frontend/` folder when building the first image called `backend`.
-
-:::note
-See **[Best Practices for Image Building](../../../guides/image-building.mdx)** for details on how to optimize your Dockerfiles and use `.dockerignore` for faster image building.
-:::

docs/pages/getting-started/development.mdx

@@ -71,7 +71,6 @@ You can also start the UI without running `devspace dev` using this command:
 devspace ui
 ```
 
-[Follow this guide to learn more about the functionalities of the DevSpace UI for Kubernetes development.](../guides/localhost-ui.mdx)
 
 <figure class="frame">
   <video controls loop autoplay="true">

docs/pages/getting-started/next-steps.mdx

@@ -17,13 +17,3 @@ devspace login                        # to login to Loft via DevSpace
 devspace create space my-namespace    # for creating namespace on-demand via Loft
 devspace create vcluster my-vcluster  # for creating virtual Kubernetes clusters via Loft
 ```
-
-## Guides
-- [Onboarding Guide](../guides/basics.mdx) to share with the rest of your team
-- [Network & Domains Guide](../guides/networking-domains.mdx)
-- [CI/CD Integration Guide](../guides/ci-cd-integration.mdx)
-
-## Best Practices
-- [Image Building](../guides/image-building.mdx)
-- [Dev vs Staging vs Production](../guides/dev-staging-production.mdx)
-- [Remote Debugging](../guides/remote-debugging.mdx)