Ecommerce Fullstack Project (DEC2023)

Project Description

This project is an ecommerce fullstack application built using React for the frontend and Node.js for the backend. The application allows users to browse through products, add them to their cart, and proceed to checkout.

Folder Structure

The folder structure of the project is as follows:

DEC2023/
│
├── node_module/            
├── public/            
├── src/            
│   ├── assets/        
│   └── components/            
│   └── pages/           
│   └──            
│   └──            
│
└── .eslintrc.cjs
└── .gitignore
└── index.html
└── package-lock.json
└── package.json
└── README.md
└── vite.config.js

Getting Started

Follow these steps to get the project up and running on your local machine.

Clone the Repository

git clone https://github.com/Final-Project-Dec2023/Dec2023.git
cd Dec2023

Install Dependencies

# Install frontend dependencies
cd < root folder >
npm install


### Run the Development Servers

```bash
# Start the frontend development server
npm start

# Start the backend development server
cd ../server
npm start

Now you can access the application at http://localhost:5173.

Contributing

Follow these guidelines to contribute to the project:

1. Fork the repository.
2. Clone your forked repository to your local machine.
3. Create a new branch for your feature or bug fix.
4. Make your changes and commit them with descriptive commit messages.
5. Push your changes to your branch on your forked repository.
6. Submit a pull request to the main repository.

Branch Naming Convention

When naming your branch, follow this convention:

• feature/<feature-name> for new features e.g blard/navbar
• bugfix/<bug-description> for bug fixes e.g kiki/navbaroverflow

Avoiding Conflicts

To avoid conflicts when pushing changes to your branch, make sure to pull any changes from the main repository's main branch into your local branch before pushing:

git pull origin main

Resolve any conflicts locally and then push your changes.

Code Style

Follow the existing code style and conventions in the project. Use meaningful variable and function names, and ensure your code is properly formatted.

Issues and Feedback

If you encounter any issues or have feedback, please open an issue on the GitHub repository, or reach out to BLARD.

---