<a href="https://www.canva.com/design/DAFlzVM_kfs/FJmsajDd_Kv2PgN0VF5UzQ/edit?utm_content=DAFlzVM_kfs&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton">Link to new Logo </a>

<img style="height: 50px; width: 50px" src="./public/NewLogo.png"/>

To get started with Grabtern Frontend, you'll need to install Node.js and npm on your machine. Then, you can clone this repository and install the dependencies:

• Fork The Repo

you can do this by clicking on the green coloured fork button

• Clone your forked repo

$ git clone https://github.com/your-username/grabtern-frontend.git

• Go to directory

cd grabtern-frontend

• Install Dependencies

npm install

• Start LocalHost Server

npm run dev

This will start the development server on http:https://localhost:3000/.

• And if server stop then

npm run build

npm start

This will start server

<img src="https://img.shields.io/badge/next.js-000000?style=for-the-badge&logo=nextdotjs&logoColor=white"> <img src="https://img.shields.io/badge/MongoDB-4EA94B?style=for-the-badge&logo=mongodb&logoColor=white"> <img src="https://img.shields.io/badge/Docker-2CA5E0?style=for-the-badge&logo=docker&logoColor=white"> <img src="https://img.shields.io/badge/Node.js-339933?style=for-the-badge&logo=nodedotjs&logoColor=white"> <img src="https://img.shields.io/badge/GitHub%20CI/CD-222222?style=for-the-badge&logo=GitHub%20Pages&logoColor=white">

Our platform's email service is seamlessly integrated into various sections, enhancing communication and user interaction.

While the backend remains concealed for security, accessing emails is easy with specific credentials.

You can create an account, verify it, and also act as a mentor with verification.

This way, contributors can fully experience our platform by registering as both mentors and users.

Login to ethereal mail.com with these credentials:

"user": "[email protected]",
"password": "MjMfuHFxfjeXttjH8v"

Prettier is a code formatter that helps maintain consistent code style and formatting in your projects. It automatically analyzes your code and applies predefined formatting rules to ensure a standardized appearance.

Linting is the process of analyzing code for potential errors, bugs, and code style violations. It helps identify and highlight problematic code patterns, potential bugs, and adherence to coding standards.

<b>"Prettier lint test" </b> refers to running a linter (such as ESLint) with the Prettier plugin or rules enabled. It means checking your code for both linting errors and code formatting inconsistencies according to Prettier's rules.

To enable automatic code formatting upon saving in Visual Studio Code, you can install the Prettier extension. This extension ensures that your code is consistently formatted and adheres to the defined style guidelines. Once installed, Prettier will format your code automatically whenever you save a file.

In case you prefer not to install the Prettier extension, there are two helpful commands you can use:

1. npx prettier --check ..: This command checks your codebase for any formatting issues without making any changes. It identifies areas where the formatting may not align with the defined rules.
2. npx prettier --write . .: This command automatically fixes the formatting issues in your codebase. It applies the appropriate formatting changes to ensure consistency and adherence to the defined style guidelines. By utilizing these commands, you can easily verify the formatting of your codebase and address any inconsistencies or style violations, even without having the Prettier extension installed.

If you'd like to contribute to Grabtern Frontend:-

• If you have suggestions for adding or removing projects, feel free to open an issue to discuss it, or directly create a pull request after you edit the README.md file with necessary changes.
• Please make sure you check your spelling and grammar.
• Create individual PR for each suggestion.
• Please also read through the Code Of Conduct before posting your first idea as well.

1. Fork the Project
2. Create your Feature Branch (git checkout -b <new_branch_name>)
3. Save your changes (git add .)
4. Commit your Changes (git commit -m 'Added some AmazingFeature')
5. Push to the Branch (git push origin <branch_name>)
6. Open a Pull Request

This project is licensed under the MIT License - see the LICENSE file for details. MIT

Anmol Agrawal