chore: update readme

[DaRiaN0Dev]

Summary by Sourcery

Revise and expand the README to better describe the project and improve structure and formatting.

Documentation:

• Reorganize and rewrite the README with clearer sections for features, tech stack, setup, environment notes, testing, contributing, and licensing.
• Enhance README formatting with centered branding, headings, and improved descriptions for project capabilities and usage.

[sourcery-ai]

Reviewer's Guide

README.md is rewritten to improve structure, formatting, and clarity: centralized branding header, reorganized sections with clearer headings, refined feature and tech stack descriptions, more explicit setup and environment instructions, and polished contributing and license text.

File-Level Changes

Change	Details	Files
Reworked project introduction and feature list for clearer branding and readability.	Added centered logo and project title header using HTML for alignment and styling. Rephrased and reformatted the introductory description into a concise tagline and description block. Converted the feature list from simple bullets to a structured list with consistent wording and icons, emphasizing capabilities and tests coverage.	README.md
Restructured setup, environment, and testing sections into clearer, step-based documentation.	Renamed and reformatted the getting started section into numbered, titled steps for cloning, installing dependencies, configuring .env, and running the dev server. Clarified environment-related notes for Swagger, Postman collection, and Docker usage, including explicit paths and a note about editing env vars in docker-compose.yaml. Refined the tests section description and simplified the test command example formatting.	README.md
Polished contributing and license sections for consistency and tone.	Condensed contributing guidance into a short, actionable list (fork, issues, PRs) with a motivational closing sentence. Reformatted the license section with emphasis on MIT license name and reference to LICENSE file. Removed leftover author-facing commentary text from the previous README version.	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The README now mixes HTML headings (<h1>, <p align="center">) with Markdown syntax; consider using pure Markdown for titles and layout to keep the file simpler and more portable across different renderers.
• In the Environment Notes section, the placeholder host/document is a bit vague; consider clarifying with a concrete example (e.g., http://localhost:3000/document) so users can immediately know where to open Swagger.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The README now mixes HTML headings (`<h1>`, `<p align="center">`) with Markdown syntax; consider using pure Markdown for titles and layout to keep the file simpler and more portable across different renderers.
- In the Environment Notes section, the placeholder `host/document` is a bit vague; consider clarifying with a concrete example (e.g., `http://localhost:3000/document`) so users can immediately know where to open Swagger.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}