### Description Creating a systemized documentation structure. Aim is to keep README short and structured and also having documentation for necessary components. ### Rationale As the project has grown, the README has become responsible for describing many different aspects of the application, including setup, deployment, testing, contribution guidelines, sustainability, and project details. Keeping all of this in one file makes it harder to find relevant information and maintain the documentation. This issue aims to create a systemized documentation structure by keeping the README short and focused on the project overview and quick-start information, while moving detailed topics into separate Markdown files in the docs folder. This will make the documentation easier to navigate, update, and expand as the project develops. The structure will also ensure that important areas such as setup, deployment, testing, sustainability, AI use, API behavior, and database design have clear and dedicated documentation. ### Acceptance criteria - [x] The README is shortened and contains only the project overview, quick-start information, and links to detailed documentation. - [x] Each documentation file has a clear title and consistent structure. - [x] Documentation links work correctly from the README and between documents. - [x] The documentation does not contain contradictory or outdated instructions. - [x] The documentation accurately reflects the current project structure and commands.