Add documentation to cipherguess website.

[BHARGAV-RUE]

cipherguess.vercel.app

[Peeyush3587]

Please Elaborate what type of documentation

[BHARGAV-RUE]

Thanks for showing interest in contributing!

I intentionally left the issue open-ended because I'd like contributors to improve any missing documentation they notice. Feel free to enhance the README, setup guide, project overview, features, API documentation, or contribution guide—whatever you think would provide the most value.

One small note: I'm planning a major architectural refactor (moving from a monolith to microservices) in the coming weeks, so I'd recommend avoiding deep documentation of the current internal architecture since it will likely change. Everything else is welcome.

Also, since the project is expected to evolve significantly over the next month, I completely understand if you'd prefer not to work on this issue to avoid your efforts becoming outdated. No pressure at all. If you'd still like to contribute, I'd be happy to review your PR. Thanks again for your interest!

[EmaniPreethika]

Thanks for showing interest in contributing!

I intentionally left the issue open-ended because I'd like contributors to improve any missing documentation they notice. Feel free to enhance the README, setup guide, project overview, features, API documentation, or contribution guide—whatever you think would provide the most value.

One small note: I'm planning a major architectural refactor (moving from a monolith to microservices) in the coming weeks, so I'd recommend avoiding deep documentation of the current internal architecture since it will likely change. Everything else is welcome.

Also, since the project is expected to evolve significantly over the next month, I completely understand if you'd prefer not to work on this issue to avoid your efforts becoming outdated. No pressure at all. If you'd still like to contribute, I'd be happy to review your PR. Thanks again for your interest!

Since you're closest to the implementation details, a rough first draft of the README/install steps/API doc from you would make it a lot easier for contributors to fill in gaps and improve clarity, rather than guessing at things that might be wrong.

[BHARGAV-RUE]

Thanks for the suggestion! I've added a basic README as a starting point. Feel free to improve and expand it. Some areas you can work on are:

1. README structure and formatting
2. Setup & installation guide
3. Features documentation
4. API documentation
5. Project structure overview
6. Screenshots/GIFs
7. Contribution guidelines
8. Environment variables (if needed)
9. Grammar, readability, and overall documentation quality

Please avoid documenting the current internal architecture in too much detail since I'm planning to migrate the project from a monolith to microservices soon. If anything is unclear, feel free to ask. Thanks!