[FEATURE] Add docs for the Website

[SaptarshiSarkar12]

Is your feature request related to a problem? Please describe.

The README file currently lacks examples and use cases for both Drifty CLI and GUI. It also does not mention the custom issue labels that the project uses.
Before testing their changes, the contributors need to run some commands. The addition of Dockerfiles to this project via #218 will require some notes and advices, but the README file is already too crowded and lengthy.

Describe the solution you'd like.

I would like to have a docs section for Drifty with sections like - Quickstart, Getting Started, Contributing, FAQ and Troubleshooting.

• Quickstart: A brief introduction to the main features of Drifty, with a simple example to get users up and running in minutes.
• Getting Started: A more detailed guide on how to install, configure, and use Drifty, with explanations of the core components and options.
• Contributing: A section for developers who want to help make Drifty better, with instructions on how to set up a development environment, submit pull requests, and report bugs and new ideas.
• FAQ: A collection of common questions and answers about Drifty, covering topics such as compatibility, performance, security, and customization.
• Troubleshooting: This subsection helps to resolve common issues and errors that users may encounter while using Drifty and suggests possible solutions and workarounds.

The docs should be in markdown files and will be rendered by next js. You can read more about this here.

If you have any suggestions to add more suggestions, please let me know.

Screenshots

The docs page can have a look like this -

You can see the live version of the docs homepage here.

Additional information

Skills you need to solve this issue - NextJS, TailwindCSS, MD / MDX in Nextjs.
Those who wish to work on this issue, please leave a comment below and I will assign you with the task.

[sathvik-ng-07]

Hi SaptarshiSarkar12,

I'm interested in working on this issue. I've reviewed the problem and your proposed solution, and I'd like to contribute to improving the documentation for Drifty as described.

Here's what I plan to do:

• Create separate Markdown files for each documentation section (Quickstart, Getting Started, Contributing, FAQ, and Troubleshooting).
• Populate these files with clear and detailed content, including examples and code snippets where necessary.
• Update the main README file to link to the newly created documentation files.
• Test the changes locally to ensure they work as expected.
• Open a pull request (PR) once the changes are ready for review.

Please let me know if you have any specific requirements, guidelines, or additional information I should be aware of before I start working on this. And also let me know if i can submit PR on the master branch itself or some other branch . I'm excited to contribute to the project and help improve its documentation.

Thank you!
Sathvik N G

[SaptarshiSarkar12]

Thank you @sathvik-ng-07 for your interest in this issue!
Yes, I agree with your plan. Looks good to me. 👍
You need to open the PR to the master branch (the default branch). Please do not open any PR against other branches.
I am assigning you with the task. You can start working on it.