https://github.com/codewithrajdeep/recipe-book
Recipe Book - Everyone is professional chef at their own kitchen
https://github.com/codewithrajdeep/recipe-book
internship recipe-website
Last synced: about 2 months ago
JSON representation
Recipe Book - Everyone is professional chef at their own kitchen
- Host: GitHub
- URL: https://github.com/codewithrajdeep/recipe-book
- Owner: CodewithRajDeep
- Created: 2025-06-07T18:35:53.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-06-22T15:24:28.000Z (10 months ago)
- Last Synced: 2025-08-25T14:18:23.846Z (8 months ago)
- Topics: internship, recipe-website
- Language: HTML
- Homepage: https://recipe-book-swart-seven.vercel.app
- Size: 913 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
### π Recipe Book - Responsive Recipe App

### β οΈ Purpose:
A user-friendly web application to add, view, and manage recipes easily. Perfect for food enthusiasts who want to organize and share their favorite recipes with an intuitive interface.
### π Table of Contents:
1.[π About Recipe Book](#about)
2.[π Features](#features)
3.[πΈ Screenshots](#screenshots)
4.[π Tech Stack](#techstack)
5.[π¦ Installation](#installation)
6.[π§ Usage](#usage)
7.[π€ Contributing](#contribution)
8.[π License](#license)
9.[π¬ Contact](#contact)
## π About Recipe Book
Recipe Book is a lightweight responsive platform that allows users to add new recipes with details like title, ingredients, instructions, and serving info. Users can also view and delete recipes on the same page. The app is designed with clean HTML, CSS, and JavaScript and can be hosted easily on platforms like Vercel.
## π Features
- π Add new recipes with title, prep/cook time, servings, ingredients, and instructions
- π View a list of all added recipes dynamically on the page
- β Delete any recipe from the list
- β
Form validation with success confirmation
- π¨ Clean responsive design with custom CSS
- π Persistent data during the session (using local storage or in-memory storage)
## Dashboard:

## Recipes:

## Add Recipes:

## π¦ Installation
Follow these steps to set up the project locally on your machine.
### *π§ Prerequisites:*
- Modern web browser (Chrome, Firefox, Edge, Safari)
- Git (optional)
- Responsive basic web layout
### β¬ Clone Repository:
```bash
git clone https://github.com/your-username/recipe-book.git
cd recipe-book
```
### π Run Locally : start the live server to view the recipe-book
## π§ Usage
- Fill the Add Recipe form with your recipe details
- Submit to see the recipe appear below the form
- View all added recipes dynamically on the page
- Delete any recipe using the delete button
- Refreshing the page clears all recipes (unless you add persistence)
## π€ Contributing
π¬ Contributions are highly encouraged! If you're a researcher, educator, or developer, feel free to improve MediCare.
```
Fork the repository.
Create a new branch (git checkout -b feature-name).
Commit your changes (git commit -m "Added new feature").
Push to your branch (git push origin feature-name).
Open a Pull Request.
```
## π Contribution Guidelines:
## πReporting Issues:
Search for existing issues: Before creating a new issue, search the issue tracker to see if the problem has already been reported. Provide clear and concise information: When creating a new issue, please include as much detail as possible, such as: Clear description of the problem Steps to reproduce the issue Expected behavior Actual behavior Screenshots or logs (if applicable) Use issue templates: If available, use the provided issue templates to structure your report.
## πSubmitting Pull Requests:
Fork the repository: Create a fork of the project on your GitHub account. Create a new branch: Create a new branch based on the main branch or a feature branch. Make changes: Implement your changes and commit them with clear commit messages. Push changes to your fork: Push your changes to your forked repository. Open a Pull Request: Create a pull request from your branch to the main repository. Provide details: Clearly describe the changes you've made and the benefits they bring. Address code review feedback: Be open to feedback and make necessary changes.
## πTesting:
Write unit tests for any new features or bug fixes. Ensure existing tests pass after your changes.
## π License:
Reminder is licensed under the MIT License β open for research and educational purposes.
π GitHub: CodeWithRajDeep
π Website: https://deepraj-portfolio-red.vercel.app