📖 docs: Update README.md (#189)

## Description
Update the readme file

## Related Issues
none

## Type of Change

- [ ] Bug fix (non-breaking change)
- [ ] New feature (non-breaking change)
- [ ] Breaking change (fix or feature that changes existing
functionality)
- [x] Documentation update
- [ ] Other (please describe):

## Checklist

- [x] I have updated relevant documentation
- [x] My code follows the project's coding style
- [x] My changes generate no new warnings/errors

## Notes for Reviewers
none

## Screenshots/Demo
none

## Additional Context
none

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Documentation**
- Major overhaul of documentation structure and content for improved
clarity, modern presentation, and ease of navigation.
- Updated and expanded guides for installation, setup, architecture, and
command-line interfaces.
- Enhanced FAQ and troubleshooting sections with more comprehensive
answers and technical details.
- Added new guides for self-hosting with reverse proxy examples (Caddy,
Traefik) and developer notes.
- Improved theming, styling, and home page layout for the documentation
site.
  - Simplified main README to a minimalistic project header and tagline.
- Added new documentation files for Nestri Relay introduction and
container CLI parameters.
- Removed outdated or redundant documentation files and components to
streamline content.

- **Chores**
- Updated, reorganized, or removed configuration files for dependencies,
linting, and environment setup.
- Switched to a new documentation theme and updated related project
dependencies.
- Removed Renovate configuration and ESLint config specific to docs app.
- Adjusted TypeScript and package configurations for better
compatibility.

- **Style**
- Improved dark mode support and visual consistency across documentation
and components.
- Introduced new Tailwind CSS theming and animation support for the
documentation site.

- **New Features**
- Added example configuration files for deploying Nestri Relay with
Caddy and Traefik reverse proxies.
- Introduced new Tailwind CSS theming and animation support for the
documentation site.
- Added a new logo component supporting light/dark mode and optional
title display.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Victor Pahuus Petersen <49293748+victorpahuus@users.noreply.github.com>
Co-authored-by: Wanjohi <elviswanjohi47@gmail.com>
Co-authored-by: DatCaptainHorse <DatCaptainHorse@users.noreply.github.com>

apps/docs/content/2.nestri-node/2.prerequisite.md

@@ -1,53 +1,27 @@
-# Prerequisite
+---
+title: Prerequisites
+description: Essential system and software requirements for setting up Nestri on your server, including GPU compatibility, OS recommendations, and necessary configurations.
+icon: 'lucide:check-circle'
+---
 
-To run Nestri on your own server, there are several essential preparations required before installing nestri-node. This page outlines the key requirements to get Nestri up and running smoothly.
+To run Nestri on your own server, there are several essential preparations required before installing Nestri Node. This page outlines the key requirements to get Nestri up and running smoothly.
 
-Nestri-node supports AMD, NVIDIA, and Intel graphics cards. For optimal performance, however, we recommend using Intel or NVIDIA GPUs. Our testing has shown that these GPUs provide the best results, while AMD graphics cards may encounter limitations due to partial support for Arch Linux in AMD's AMF drivers. As a workaround, we utilize the VA-API plugin for GStreamer with AMD cards to ensure functionality.
+Nestri Node supports AMD, NVIDIA, and Intel graphics cards.
 
 While it might be tempting to skip this setup, we advise against it. Taking the time to prepare now will help you avoid potential issues and wasted hours later.
 
 ## Recommended host configuration
 
 ::list{type="primary"}
-- **NVIDIA or Intel GPU** (AMD is supported, but not reccomended, due to lack of natively supported API-drivers in CachyOS)
-- **AVX supported CPU** (If your CPU doesent support AVX, you can use our `noavx` image)
-- **Fedora or Arch** based distributions ( [Debian and Ubuntu is **not**  supported](/nestri-node/node-faq#can-i-run-nestri-node-on-debianubuntu) )
+- **AMD, NVIDIA or Intel GPU**
+- **CPU with AVX2 support**
+- **Fedora or Arch** based distribution
 ::
 
 ## Software Requirements
 
 ::list{type="primary"}
-- **Nvidia Drivers**
-- **[NVIDIA Container Toolkit](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html#installing-with-apt)**
-- **[Docker](https://linuxiac.com/how-to-install-docker-on-ubuntu-24-04-lts/)**
+- **GPU Drivers** (if not provided by the kernel)
+- **Podman or Docker** (Podman is recommended for better compatibility)
 
 ::
-
-## Disconnect monitor
-Since Nestri requires access to your GPU, then you need to unplug you screen from it.
-If you want to see the Desktop and have a integrated graphicscard in your CPU, then you can connect your monitor to the motherboard.
-### Change the Default Boot Target to Multi-User (Non-GUI Mode)
-Ubuntu typically starts in graphical mode (using the graphical.target systemd target). You should change to the non-graphical multi-user.target, which will prevent Xorg from starting.
-
-1. Open a terminal or access your system via SSH.
-2. To check your current default target (which should be graphical.target)
-
-```bash
-systemctl get-default
-
-```
-
-3. Change the default target to multi-user.target (which corresponds to text mode, without Xorg):
-```bash
-sudo systemctl set-default multi-user.target
-
-
-```
-
-4. Reboot the system
-
-5. Verify that Xorg is not running
-```bash
-nvidia-smi
-```
-