Welcome to PlayItForward, the premier community-driven toy exchange platform designed to make toy sharing accessible and sustainable.
By connecting families and toy enthusiasts, PlayItForward serves as a vibrant marketplace where users can give new life to toys, ensuring they are cherished and enjoyed far beyond their initial purchase.
- Key Features
- Why Choose PlayItForward?
- Getting Started
- Prerequisites
- Installation
- Usage
- Additional Resources
- Acknowledgments
- Author
- Contact
- License
- Feedback
-
Toy Management: Manage your toy listings with features like interactive map view, instant messaging for inquiries, and easy add-to-favorite options for quick access later.
-
API Integration: Synchronize your items across different platforms and devices, ensuring you're always up to date.
-
Responsive UI Design: Enjoy a seamless experience on any device, thanks to our adaptive and user-friendly interface.
PlayItForward stands out as a pioneering solution for parents, guardians, and toy enthusiasts looking to maximize the value and enjoyment of toys. By facilitating easy exchanges and fostering a sense of community, the application not only helps in reducing waste but also ensures that toys continue to bring joy to children's lives for years to come.
To get a local copy up and running follow these steps.
- npm
npm install npm@latest -gIt updates npm to the latest version.
- Clone the repo
SSH:
git clone git@github.com:Code-the-Dream-School/ffprac-team4-front.git
HTTPS:
git clone https://github.com/Code-the-Dream-School/ffprac-team4-front.git- Install NPM packages
npm installTo run the application, execute the following command:
npm run devThe application will open in your default web browser at http://localhost:5173.
This is a Full Stack application. Navigate to Back End repositoy
Special thanks and a shout out to the following individuals and organizations:
- Code the Dream for their exceptional coding school, providing valuable learning resources and support.
- Our beloved project manager Gaetan Siry for his guidence, mentorship and countless hours of dedication for the success of our team.
- Hat tip to anyone whose code was used.
If you have any questions or feedback, feel free to reach out to DevArts.
Distributed under the MIT License. See LICENSE for more information.
Your feedback is invaluable to us! If you have any suggestions or run into issues while using PlayItForward, please open an issue on our GitHub repository. We're committed to making PlayItForward the best it can be, and your input helps us achieve that goal.
Thank you for choosing PlayItForward as your toy exchange companion. Let's make it a seamless and productive part of exploring, posting, and exchanging toys!
This will be the front-end for your team's practicum project.
It is suggested that you run these instructions after you setup the back-end server first. You can go through these steps during your first group meeting in case you need assistance from your mentors.
You will have two folders inside one team folder (one for front-end and one for back-end). Name the parent folder something appropriate (in the below example we title it "Practicum Project"). Then clone directly (do not fork and clone) the front and back repos while inside the parent ("Practicum Project") project folder.
The front-end app (React) will be running on port 3000. The back-end server will be running on port 8000. You will need to run both the front-end app and the back-end server at the same time to test your app.
- Clone this repository to the folder that was already created for both the front-end and back-end repos
- Run
npm installto install dependencies - Pull the latest version of the
mainbranch (when needed) - Run
npm startto start the development server - Open http://localhost:3000 with your browser to see the data received the back-end server.
- Now you have your front-end and back-end running locally!
Note: In the below example, the group's front-end repository was named bb-practicum-team1-front and the back-end repository was named bb-practicum-team-1-back. Your repository will have a different name, but the rest should look the same.



