- Introduction
- Installation
- Technologies
- What, Why
- Project Scope
- Project Plan
- Project Outcomes
- Future Improvements
- Contributors
Bamboo Nest is an app designed to connect parents, creating an easy platform for them to buy and sell second hand items.
You can find the deployed site here
You can find our handover documentation here with a more detailed breakdown of our project
To get started with Bamboo Nest on your own machine follow these installation instructions:
Clone the repository
git clone https://github.com/fac28/Bamboo-Nest.git
cd Bamboo-NestRun a local server
npm install
npm run devopen localhost:3000 in your preferred browser to see the result
You will also need the appropriate environment variables stored in .env.local
You can see an example of what environment variables are expected in .env.local.example
Bamboo Nest is deployed on Vercel. The site is set up to continuously deploy whenever changes happen to our main branch You can find the deployed site here
This project is built using:
- Next.js 14
- React
- Typescript
- Supabase
- Tailwind
- What This project is the MVP for Bamboo Nest. A site allowing parents to buy, sell or rent second hand kids items.
- Why Provides a sustainable and affordable way for parents to buy kids items. As well as letting parents make money from bulky items between kids
Three one week sprints
Each sprint included time for retrospectives in the form of SGCs (Stop, Go, Continue).
- We made a clickable Figma prototype
- We conducted user research based on our Figma prototype
- We tweaked our Figma based on feedback from user research & input from our product owner
- We generated some user stories to help identify key features while keeping in mind how users would interact with our site
- Once we were happy with our design we started planning the schema for our database
You can find our figma here
And a clickable demo of the figma here
- At the beginning of each build week we decided what features to work on. Split each feature in to small issues aiming to ensure everything was at most E3.
- Everyone assigned themselves work ensuring active tickets were marked as such.
- We had regular standups giving everyone a space to bring up issues or features they felt needed to be focussed on.
- At the ened of the week we reflected on how the sprint had gone. Making sure issues had been properly labeled with estimations and actuals.
- Toggle favourite button doesn't work on all pages
- add location features: Filter by distance etc
- add payment processing
- add in app communication
- Improve user feedback i.e. when a user submits a form should show what they've submitted and if it was successful
- Add suspense & error boundries to make the site more performant & robust