Added the Getting Started page

[mukilan2815]

Related Issue

This helps users to know how to use the website

Description

Added the geting started page for users to know how to use the software and many other FAQs

Type of PR

• Bug fix
• [ x] Feature enhancement
• Documentation update
• Other (specify): _______________

Checklist:

• [ x] I have performed a self-review of my code
• [ x] I have read and followed the Contribution Guidelines.
• [ x] I have tested the changes thoroughly before submitting this pull request.
• [ x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
• [ x] I have commented my code, particularly in hard-to-understand areas.

Resolves

#129

[vercel]

@mukilan2815 is attempting to deploy a commit to the subhadeep3902's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Welcome to Blox AI! 🎉 Thank you for submitting your pull request. We're excited to review it! 🚀 If you haven't already, be sure to check out our site to learn more about how Blox AI makes crafting flowcharts and diagrams a breeze, and how you can get explanations from the top Google Gemini model about your creations. Start visualizing your ideas today! Visit Blox AI for more information.

[github-actions]

Welcome to Our repository.🎊 Thank you so much for taking the time to point this out.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11013489	Triggered	Generic High Entropy Secret	405d0d6	.env.example	View secret
11013489	Triggered	Generic High Entropy Secret	931642d	.env.example	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[subhadeeproy3902]

@mukilan2815 send screenshot

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
blox-ai	❌ Failed (Inspect)			Jun 15, 2024 1:21am

[subhadeeproy3902]

@mukilan2815 U shouldnt remove .env.example it was already notified. And check for these errors ->

[mukilan2815]

[mukilan2815]

@subhadeeproy3902 check it now