#### Lusan :sunflower: --- #### The idea :bulb: An e-commerce style site which allows intermediate to experienced gardeners to browse and compare seeds from different providers and signposts to providers. --- #### User Research and Findings :spiral_note_pad:  --- * Target audience: beginner or intermediate? * "Don't make me think" design * Make navigation super easy: place a search icon in the navbar --- Make sure the purpose of every page is super clear Before  --- After  --- Positives :thumbsup: * Users and PO liked the clean, simple design * Users were able to complete navigational tasks when directed --- Users favoured the 'Growing Conditions' feature  --- Learnings 🤓 * Refine user flow through the site * Walk through every button click in the user's shoes * "Funnel" users to the desired end-point --- #### User stories Based on usability testing and taking into account the most important features to deliver within an MVP. Our core user stories are...🥁 --- As a user I want to...🪴 * Search for seeds (vegetables, herbs and flowers) * Filter search results by specific parameters (type, climate, water, soil and price) * Compare a seed variety offered by different providers (price, spp, stock) * Add products to my wishlist * View my wishlist * Find out my growing conditions based on my postcode (stretch) --- #### Data and Database - Milly :thinking_face: - We're speaking with Isabelle from Lusan this afternoon to find out about the web scraping they've been doing with data from 6 different UK seed companies :seedling: - To begin with we'll be using dummy data in a js file with help from [Chance](https://www.npmjs.com/package/chance) as a random generator for all of the seed categories, sub categories and climate data :sun_with_face: :rain_cloud: :wind_blowing_face: - PostgresSQL Database - Supabase (Not ElephantSQL) :elephant: --- #### Tech Stack - Milly - Next Js - Front End First Approach with React - Cypress for testing :heavy_check_mark: --- #### Sprint 1 Aims * Create an MVP including CSS features to be able to display to PO. * Decision about using db tbc. Back up plan: chance :thinking_face: * Front end focused. * Core features will include: Creating homepage, Burger menu, Browsing seeds page, Working filters. * Mobile first design. --- #### Sprint 2 Aims - Set up tests and Github Actions to run tests ahead of merging and deployment :+1: - Store wish list in local storage :computer: - Create additional smaller pages and components: - contact page and about us page - static growing conditions page - wishlist heart icon toggle - footer component --- #### Our Roles :drum_with_drumsticks: --- #### Scrum facilitator/Liason with product owner :sparkles: * Daily stand-ups. * Frequently update project board on github to give people a sense of completing tasks and also track velocity. * Assigned group members/labels to issues. * Make sure issues are broken down into smaller tasks. * Time-boxing tasks. --- * Breaks! * End of day feedback to the product owner on discord. * Schedule meetings to discuss the webscraping data. * Debrief at the end of the day. --- #### Project Board Goals :star2: (We estimate Sprint 1: 28 points, Sprint 2: 21 points)  --- #### UX/UI * Set up a design framework to keep consistent design across app :triangular_ruler: * Use Styled Components :nail_care: on components repeated across pages --- #### Devops * Project Setup :computer: * Install Cypress :sweat_smile: (with Miah's help) :pray: * Create a Next Js App - don't clone the repo locally :exclamation: * Configure ESLint and Prettier :white_flower: * Deploy to Vercel :thinking_face: * Keep track of PRs and preview branch deployment on the Vercel logs :face_with_monocle: --- #### Quality Assurance / Documentation 🥸 Sprint 1 * Ask team to run `npm run lint` before commits * Keep repo tidy, clear variable naming Sprint 2 * End to end testing of user's "happy path" * Testing of error handling (invalid user inputs etc.) * Github actions to check for `console.log`s * Lighthouse report for accessibility --- Demo time! :sparkles: