Design-specific tasks in Sprint

Design-specific Resources

Design Team Figma file

Design Team figjam File

Design Handoff file

Admin Panel Requirements

| Wed, 06/29 | • Janice will see if previous lead designer can provide brief autolayout workshop

• Figure out typecscale/iconography/grid system
• Start with lo-fidelity wireframes (landing page) | https://techfleet-ruminate-design.vowel.com/#/meeting/JVD5KaRGRweKqa54 | | Went over Ideation Sketches by all team members + Create 2 lo-fi Wireframe mock ups in Figma. | Discussed Figma file Ruminate scope https://www.figma.com/file/VcQ4rjNJCVSjB0pGXcyra7/Ruminate-MVP-Scoping-and-Prioritization-Board?node-id=0%3A1

Note: Shipping Tracker is out-of-scope for this phase

Destiny: clarify whether they want this project to go live or just an MVP outline

Ideation Sketches, went over and starred priority features of 2 wireframe mockups

(NOTES: Organizing header categories may be out-of-scope

Pricing page should be on landing page, but also again elsewhere) | Thur, 06/30 | Prep the design presentation for Friday’s demo

1. Selecting an Evaluator page
2. Evaluator’s Profile page (from producer user perspective) | Cannot find recording | | Review mock ups of 2 example web pages | Emphasized mentioning the “Request” button in demo presentation

(NOTES: Ruminate does not want producer/user to be able to select evaluators. Does not want reviews/testimonials either

They do not have a current solution for administration aspect of management either- they hope algorithms to match evaluators—> producers completely) | Fri, 07/01 | - Continue building on design system (typography received) - Have a joint meeting with dev team at 6pm EST, Monday

—— Sprint Demo Week 2 (Amitha)

First official sprint started Week 2** | Note: Design team 30-min review not recorded | | Discussing MVP Scope + Priority Features (high value vs. low effort, etc), and Divided up Lo-Fi Wireframes Pages among team members | Reviewed MVP board with Destiny: sticky note exercise to divvy up high value vs. low value, low effort vs. high effort tasks

Reviewed user flow https://www.figma.com/file/qmqUxKSkaZWb7BQPp0pkYJ/Ruminate-Design?node-id=0%3A1

| Tue, 07/05 | -Ellen is completing user flow for Returning Producers Who Want to Redo the Evaluation on an Evaluated Product (see MVP board file)

-Lo-fi Wireframe Pages divided among team members for this week | https://techfleet-ruminate-design.vowel.com/#/meeting/aHtGT6BvoJyUmMwX | | | | Wed, 07/06 | | | | Discussing Dev Team notes + Continue building Lo-fi Wireframes | Reviewed Dev notes Reviewed all team members lo-fi wireframes Working session on lo-fi wireframes | Thur, 07/07 | Continue building Lo-fi Wireframes | https://techfleet-ruminate-design.vowel.com/#/meeting/8VeKrF1RFkc49J8L | | —- | | Fri, 07/08 | Sprint Demo 3 (Jasmine) | — | | | - Discuss with research team on usability test requirements - Flow for producers and evaluators

• Goal to aim for mid-fi wireframe + usability testing by end of this week
• Looking to test 3 main separate flows:

1. Can producer easily enlist as a producer?
2. Can evaluators easily enlist as an evaluator?
3. Will producer will be able to see the form?

Clarify from Ryan on comments in the CX MAP-TO-BE Once evaluation completed, Ruminate would want to see that data. *Be able to create smaller summaries of what everyone said for those questions- instead of reading each answer, get a snapshot of ex: ppl like the packaging, don’t like green, like iconography

Ryan would like payment up front first to start process immediately, then can refund them if unapproved. More approval > rejected for producers. Rather than having them sign up and wait for approval. (Note: good idea to test this order of steps) -Ellen suggestion: hotel-payment structure, to charge until AFTER approval comes through. -Ryan suggestion: an option for producer to sign up without payment involvement Usually approval is next-day, usually a simple, easy process. Destiny: keep in mind target audience is usually Gen Z (older generation), can easily drop-off Discuss and clarify from Ryan on the low-fi designs

Landing page: video preferably takes up entire hero section

Ryan agrees - need to cut down content. Landing page content generally is good

Ryan envisions log in in header somewhere

Other specific notes found in Comments on Figma file

Producer Dashboard - Ryan prefers tabs, possibly include that on Evaluator Dashboard as well Ryan and team will go over what details needed on Detailed Product page

Checkout page - will confirm what “may we also suggest” will include Ryan and team will confirm how to break down Producer Registration form (sections to make it more digestible like the Evaluator Registration)

Onboarding - Ryan and team will discuss logistics for this step; would be good for Research team to test this

Kelly suggests adding a ‘Save’ button for Producer and Eval Registration | Mon, 07/11 | -Continue collaboration with research team on sitemap

• PENDING: color guide from Ryan | https://techfleet-ruminate-design.vowel.com/#/meeting/4Vf3NezuTP4xg3ER | | Design<> Research Meeting on Sitemap/Card Sorting, + Review over Ryan and Kara comments in lo-fi wireframe figma file, Discussion of Content/Design detail | **Meeting with Research for Sitemap - so that it can tested.

-** use consistent terminology: critique + review —> “feedback”; test this terminology with users

Work on mid-fi designs -Discussed comments from Kara/Ryan in figma file, particularly Detailed Product Page

• “View Evaluation” feature
• clarify with Kara which footer they wanted
• check with dev on the collapse/accordion functionality in Producer Registration
• Amitha concern: -should shipping info be put elsewhere of Producer Registration -redundancy in cheese product form (both Producer Registration + Product Intake Form pages)

**-*Amitha added a page for Dev review in design file -Amitha added Admin view sticky notes in CX-MAP-TO-BE of MVP Scope Figma file https://www.figma.com/file/VcQ4rjNJCVSjB0pGXcyra7/Ruminate-MVP-Scoping-and-Prioritization-Board?node-id=110%3A302

**** | Tue, 07/12 | - Clarify discussed comments from Kara/Ryan with them

• Ask follow-up discussed questions with dev about feasibilities | https://techfleet-ruminate-design.vowel.com/#/g/mf61y62feikfisjr | | Design - User Stories + Reviewing Updated Ruminate forms | 1. Discuss on User stories created by product strategy : https://www.figma.com/file/svVhkWDZs8LoTb1GR0fTlD/Ruminate-User-Story-Mapping?node-id=0%3A1

2. Updated forms from Ruminate

• Product Eval Request Form: https://docs.google.com/document/d/1XCqZ6zvH_CIlNV_dpJScE0thqklx0h9DasPP8gh3gnk/edit#heading=h.5d9krmx8yj18
• Feedback Evaluation Form: https://docs.google.com/document/d/1UEHe_8fbZhoLbEZoupEJjyu1yOD3Eg2MtVfbHbMM7fo/edit#
• Evaluation Registration Form: https://docs.google.com/document/d/1SBxOB-mQiXlR5UF_oDqI-EqaK_9wzNwpsl7sNj9EVXI/edit#heading=h.l6unewfz2f9b
• Producer Registration Form: https://docs.google.com/document/d/1PMYOA7DOt8EmjvkIR4b9JQAdVq7zXRGi2ymLtBCDLV0/edit

3. Usability test tasks. Complete the screens by today EOD so that we can prototype tomorrow https://docs.google.com/document/d/1WrLm2omzfQZEEB9KGBmQXsvgVOmQf8Gb94pQcai384g/edit (Add downloadable button for forms (pdf format))
4. . Evaluation form- added sticky notes to User Story mapping Figma file
5. Admin view | Wed, 07/13 | 1. Jasmine to finish the rest of the questions for Product Intake Form on Figma file
6. Start prototyping in the next couple days
7. Ana or Hayley presenting Friday | https://techfleet-ruminate-design.vowel.com/#/meeting/6kLHoHoMZiBCYsMC | | Reviewing all team members progress wireframes, prep questions to ask Ryan | 1. Review all team members mid-fi wireframes in each section
8. Start with Prototyping
9. Ask Research team to ask question about landing page. And how the user feels about it. Questions to ask Ruminate team?

• Producer Dashboard - do we need to include evaluator address?
• Evaluator Product Page - do we need a button allowing Evaluators to download "Product Intake Form"? Through email link or through platform?
• Ask Ruminate for flavor wheels (for Product Evaluation form)
• If not providing evaluator with information, why is Product Intake form necessary? (is this to be provided as a reference after evaluation?) | Thur, 07/14 | 1. All team members continue to work on their mid-fi wireframes, begin prototyping

2. Spring Demo prep Friday by Ana this week
3. Monday review with client Ryan | | | — | —- | Fri, 07/15 | Sprint Demo Week 4 (Ana) | Spring Demo 4 Recording (20 min) https://techfleet.vowel.com/#/meeting/gQNywW1XyA9JVGoF | | Connected all separate prototypes into one main flow, discussed details of design choices + color palettes and cards sorting from Research Team | 1. Reviewed colors from Ryan

2. Reviewed and connected all Prototypes into one major flow - Question: How do we know at what point “Current eval vs. Previous eval” status?

Ideas --> Ask Dev which is feasible. Ask Research team terminology of what determines - “Current vs Previous”-- WORDING?

• “To be Viewed” status text Like Gmail - bold vs. faded card/text Another column for “Review” “Previous” section becomes “Completed” section
• For UX copywriting, check out https://www.copy.ai/

Ellen - change Loading Icon for “Waiting for Results” (Detailed page v4_Analysis complete) a cow-related cute image (?) Back arrow vs. Breadcrumb - Think about which works better

3. Walked through card sorting results with Kelly from research team.

4. New section on Client Review page- Add your designs (everyone in design team) | Mon, 07/18 | - Ana to create 4 color palettes (2 different primary colors)

• Amitha to connect with research team and walk through prototype
• Add updated designs to Client Review for Ruminate to see | https://techfleet-ruminate-design.vowel.com/#/meeting/HkXHNVRDi4dei66o | | Touch base with Janice/research team on user testing results, discuss Ruminate concern, set up next steps/assigned UI components | Checked the prototype (the flows look fine)

Concern from Ruminate team on dividing the registration from. They think that “It’s our opinion that it would be best for it to be 1 because no one would be signing up if they weren’t looking for full approval. Given that, if we break the process into 2 parts, we are opening up the possibility for attrition. Users will feel a sense of “completion” after the first form and would then be less likely to fill out the 2nd.”

1. UI components - - Buttons: Primary and Secondary, to upload

• Checkboxes / Radio buttons / (Toggles & Sliders?)
• Cards
• Progress bar (in the form and on the detailed product page)
• Form fields one side by side and one below the other
• Dropdown menus
• Effects (rounded corners, shadows) - we decide once we have the components
• Tables - for final evaluation, once we design the page we can add
• Navigation - Once the card sort tests are done we will have something
• Tabs - for producer dashboard
• Banners & messaging (e.g. success/error) - pop ups

2. Colors preference tests - decide on the background color for the app

Context blurb to testers: “Please chose which color you prefer. This website is used for Ruminate which is a nonprofit innovation lab that leverages behavioral science, artistic mediums, and the collective wisdom of the food community to break down complex food system issues and find digestible, evidence-based solutions.” | Tue, 07/19 | - Design for Admin View - Amitha

• User profile - Hayley
• Header, footer - Jasmine
• Evaluation Results page for producers - Ellen
• Screen for error msgs - Ana
• Pop-up msgs for errors - Ana
• Evaluator dashboard (no evaluations - empty state) - Ana
• Jasmine - update the prototype with the new form.
• User flows are based on user stories created by the strategy team - (Strategy team to action this instead of Design team)
• Add text size 24px - Ellen | https://techfleet-ruminate-design.vowel.com/#/meeting/2pXSvGoRcPV6iK4F | | Ideation Sketches for additional pages, review client comments, set up color preference tests | 1. Reviewed additional pages (Ideation Sketches) assigned yesterday
• User Profile
• Header/Footer
• Evaluator Dashboard/Error Messages
• Admin View (Aim for next phase)*
• Evaluation Results
• Flavor wheel (pie chart may be out-of-scope for dev team*)

2. Go over clients comments: - Landing Page (Smaller header for each section: MAYBE can apply to Testimonial + Pricing Section, but the rest no, so as not to mess with hierarchy)

• Dashboard: (Clarify what “tutorial” means- for using platform itself, or in terms of marketing?)
• Ask Research Team to test the Shipping Status/Track Shipping portion 3. Set up preference tests for colors

| Wed, 07/20 | Test these two sets of colors: https://app.usabilityhub.com/do/c86b18abb958/7812

https://app.usabilityhub.com/do/e2b679a47490/b64d

Review usability test (card sorting + interview results from research team)

Continue on lo-fi —> mid-fi wireframes for additional pages assigned | https://techfleet-ruminate-design.vowel.com/#/meeting/D4N2YaME1f4JgRjq | | Dev team specific constraint discussions for new pages (flavor wheel, etc), prep demo deck, fix and update some design details for consistency | 1. Discussed with Dev team (Christa)

• Grids specifications (fine)
• Final evaluation page
• Flavor wheel (Wouldn’t be interactive, but can provide possible star-rating system)
• Statistics (if any) from forms
• Evaluator dashboard Status “To be Viewed vs. Viewed” (maybe possible via boolean system)
• Producer dashboard -on how the products under review will move to past evaluations)
• Status “To be Viewed vs. Viewed” (maybe possible via boolean system) 2. Action items for Amitha:
• Create Lo/Mid- fi Admin page
• Demo decks for tomorrow
• Make changes to forms in the prototype based on the documents edited Note: If new designs available move them to client review. I will msg Ryan 3. Go over Color Preference Testing results (Blue and Purple palettes are winners)** 4. Reviewed new comments from Ryan

| Thur, 07/21 | - Review insights from usability testing

• Continue working on Colors (second set of color preference test and decide on the palette )
• Begin building UI Components (Hayley)
• Continue working on Mid -Hi fi designs
• Align form layouts/details like checkbox, radio buttons, header sizes, etc. (Amitha and Jasmine) | https://techfleet-ruminate-design.vowel.com/#/meeting/sFrUkVov2wpAqqwg | | — | — | Fri, 07/22 | Sprint Demo Week 5 (Ellen) | | | Meeting with Ruminate (Ryan + Kara) to review Figma comments and feedback | 1. Reviewed with Ruminate (Comments from from Figma pages: Client Reviews & Comments, + Page for Testing Signup Process
  • Discussed and clarified usability testing from Research team

Tutorials

• FAQ written format (what Ellen has currently), further down the line we can consider adding more things like videos, a walk-through step-by-step in next phases)

Dashboard Potential re-do of card sorting (?) Log in icon will remain in header of all pages in website*, but clarify what exactly is included in the Dashboard/Account hierarchy

Flavor wheel Ruminate: they prefer a drag-on-a-bar/scale 1-5 (rather than star rating)

Color Preference test comment: Blue palette: certain sections could have some of red color mixed in | Mon, 07/25 | TBD | https://techfleet-ruminate-design.vowel.com/#/meeting/4rtcjYbWcn6vs97r | | Build on color palette post-feedback from Ruminate, tweak website flow details, continue building out pages | 1. Review usability testing results with Research Team (Yu-Chen)

• Usability testing R1 affinity map https://www.figma.com/file/UyEiMd8pbHS4H00IPdvYJs/Ruminate-UXR-Affinity-Mapping-Exercise?node-id=0%3A1
• Potential confusion on what "Pricing" means / Morgan suggested a separate tab for Pricing, but conflict with what Ruminate prefers. Add preference test for this in next usability test
• Landing page: would be nice to see what Ruminate is about, rather than just direct to Sign-up (this confusion might be addressed once actual video is included in the future)* (see airbnb example in Colors page (figma))

2. Color Palette

• Play around with incorporating salmon color into blue palette (buttons?)
• Create options for sign up and play around with color palette - Ana Discuss detailed design updates to finalize (see Next Steps)
• Add a section (pie chart) image for completion of the profile- Amitha on dashboard

| Tue, 07/26 | 1. Send out final designs to Dev for review and feasibility by end of next week

• Research is planning for next round of usability testing for mid next week. Aim to finalize of designs by then and have all pages ready.
• Talk with team on the status of the new screens and any blockers

2. Design Team

• Finalize on navigation and finish the header and footer section and gather feedback - Header (once logged in) - My Products, About, account

• Add updated check box and radio button UI to forms -Jasmine

• Finalize on the evaluation results page Note: Star rating- change to 1 2 3 4 5 scale (not slider bar) - Amitha*

• Reach out to Ryan to cut/condense text in Pricing section - Amitha

• Color Updates- Ana

• User Profile- waiting for feedback from Ruminate team -Dropdown-manage payment, profile section - Hayley Color icons - Hayley

• Review affinity map / usability test results | https://techfleet-ruminate-design.vowel.com/#/meeting/nW7ouNTa1q7GXgfD | | Reviewed Usability test Phase 2 Questions, discussed landing page ‘How It Works’ layout | 1. Review Usability Test Phase 2 Questions with Research Team (Yu-Chen)

  • Changed wording; “Create Profile” to “Complete Profile” Q#2
  • Perhaps add a question on Product Intake Form re: producer area/location

2. Reviewed Design Details:

• Profile overlay drop-down (Account + Manage) - remove privacy & settings, add FAQ Hayley
• Landing Page- Ana Color Palette - Blue color palette won - move forward with more variations adding red -Add “How It Works” Section (?) (Example from Yu-Chen): https://get.cerebral.com/search/home/?cabt=price:week&utm_source=google&utm_medium=cpc&utm_campaign=Branded_mCPC_2022&utm_term=cerebral&gclid=Cj0KCQjwxIOXBhCrARIsAL1QFCYQ3W37PEmnvNmlcWclAzUof4Sc9PMRop7m1stJnd57NaIXbf_OPikaAsIbEALw_wcB *Notes: 1. Content of the dashboard, expecting an email from Ryan by EOD

2. Msg from Kara regarding Price page Will test out price page in the next phase* | Wed, 07/27 | 1. Have to check with Ruminate clients on the images, videos, and illustrations for Hi-Fi design

3. Continue asynchronously updating components/ building on individual designated pages | https://techfleet-ruminate-design.vowel.com/#/g/mf61y62feikfisjr | | Page-by-page review of Figma design file | 1. Re: Sitemap - clarify with Research team on - “My Product” (what would this look like in the evaluator POV?)

4. Reviewed Header design

5. Discussed breakdown for evaluator vs. producer qualifications/info (Color Page in Figma)

6. Potentially add a textbox overlay, (?) Icon to direct to evaluator qualifications - Ana

7. Footer- keep consistent across all pages, edited to fit within grid layout, add Social Media icons, update Sitemap categories - Jasmine

8. Product Intake Form - update radio button components to the form - *Jasmine

7.* Evaluation Results Summary - add one question design (just a sample design for Client Review)- Ellen

| Thur, 07/28 | **Prep demo deck - Amitha (Hayley to present this week)

Drop sesctions into | https://drive.google.com/drive/folders/1k3EuTAl_YAnbq4YntIxU9VXQ7Npw_low?usp=sharing | | — | — | Fri, 07/29 | Sprint Demo Week 6 (Hayley) | https://techfleet.vowel.com/#/meeting/YFSAKYHhsYc8tpLT | | | 1. Discussed color preference updates

• dark blue --> teal
• color contrast accessibility test- Ana

2. Header w/ colors; perhaps for tomorrow. (Double check spacing/text) -Jasmine
   • Update: Product Intake Form - add Evaluator Region question - Jasmine

-- Design Working Session: 1:25-1:45pm-- | Mon, 08/01 | 1. Amitha/Destiny to reach out to Kara re: updated feedback 2. Once color contrast accessibility is tested, begin updating other pages to hi-fi wireframes 3. Review User Flow via Product Strategy team (to the Design team: feel free to comment) https://www.figma.com/file/PdlEHjtxCAttpG2AaMJewP/Ruminate-Feedback-User-Flow?node-id=0%3A1 | https://techfleet-ruminate-design.vowel.com/#/meeting/3D7GBvtGodTtfZEM | | | 1. Discussed Colors- Ana

• Checked Accessibility for Colors (colors passed)
• Add background color on Color Style (for forms)
• Text colors: dark blue or dark teal

2. Update language from the updated Google doc forms from Ruminate- Jasmine/Amitha

3. Make “About Page” based on the site map and make “Log In” high-fidelity page - Ana

4. Footer: update Sitemap categories, and the About Feedback blurb -Jasmine

5. Update the account page based on the feedback from Ryan - Hayley

6. Create evaluator dashboard with no current evaluations - Ana

7. Update the form to reflect new changes and move it to Hi-fi designs, header so that background is on full screens - Amitha

8. Finalize on the dashboard and final results page - Ellen | Tue, 08/02 | 1. Start applying pages to hi-fidelity for tomorrow’s meeting

9. Check with research on when the usability test for Thursday is scheduled?

10. Review User flows from Product strategy (if we have time) | https://techfleet-ruminate-design.vowel.com/#/meeting/noAorjMAFFWmZDhD | | Finalizing hi-fi pages, prototype tonight. | 1. Begin finalizing hi-fi pages so we can begin prototyping

11. Footer- add facebook logo, content, apply colors - Jasmine

12. Apply progress bar color to Product Intake form/ add the “Other” follow-up question too - Jasmine

13. Make “About” Page*- An*a

14. Apply colors, hi-fi of Detailed Product Page - Ana

15. Evaluation Results Summary update to hi-fi - Amitha

Evaluation Form: https://docs.google.com/document/d/1XCqZ6zvH_CIlNV_dpJScE0thqklx0h9DasPP8gh3gnk/edit# | Wed, 08/03 | Prototype walkthrough today in the evening (15min). 7pm PST/ 10pm EST- Amitha and whoever is free | https://techfleet-ruminate-design.vowel.com/#/meeting/EiLquqzgskYEfCCb | | Discussed decisions/changes and further details for design implementations from latest Usability Test | 1. Reviewed latest Usability Test from Research Team

• Add ‘Save for Later’ or ‘Save as Draft’ button in Product Intake form
• Keep header locked (when scrolling) on the Landing Page (because we want to emphasize/encourage the “Sign Up), all other pages is “Back to Top” arrow
• Hayley designed icons (via illustrator)
• Change background color of Producer Dashboard from salmon to light blue- DONE - Ana

2. “Start an Evaluation” <-- decide on which format/button we want

---Qs to ask Ruminate---

• Do users fill out the form and then select the pricing option or vice versa?
• Get more clarification through testing | Thur, 08/04 | - Prep demo deck for tomorrow (Friday)
• Review user flow from Product Strategy team (if we have time) | https://techfleet-ruminate-design.vowel.com/#/meeting/Q6JsWSqXTYXKCYkS | | | Comments that stood out during demo:
• one user didn’t think the pink (salmon) color evoked “food”
• user flow seemed quite easy to understand | Fri, 08/05 | Sprint Demo Week 7 (Amitha) | https://techfleet.vowel.com/#/g/8hpjssbujq4jkej4 | | Prepping final week Design Handoff documents | 1. Check with product team if they have any standard hand off document.

2. Start preparing hand off document - Amitha will share a google deck with team- https://docs.google.com/presentation/d/1npJX27mBB3DaQrIzXONdbxnKpQdoIfE5AOLyAYuoKDU/edit?usp=sharing

3. Start working on the admin view - sketches and mid-fi

4. Go over usability testing feedback from research team. - https://www.notion.so/tech-fleet-community-dao/Research-3740bb47aa6546d4919d89403bdd03f4 | Mon, 08/08 | Suggestions for Next Phase:

5. Separate "price" from "Log In"

6. Progress bar so user knows how long checkout will take

7. Add a card under User Profile so that user sees pricing plan --> intake form --> checkout cart- Hayley

8. Change "Address" to "Business Address"

9. Add red asterisk to notify users where the field is missing input on all forms

10. Only one CTA to start an evaluation on Evaluator Dashboard -- Ellen

11. Clarify with Dev team about enabling quick link for "Summary" in "Results by section"

12. Discuss with Ruminate team about time commitment on evaluator sign up form

——————- To do today/tomorrow: Continue adding to hand off document - what you worked on, suggestions/what needs to be done for Phase 2 | https://techfleet-ruminate-design.vowel.com/#/meeting/vTQNMKmVeZEybaMQ | | Update and Review Design Handoff/ Joint meeting with Dev Team + Client | 1. Go over the comments from Ruminate (Ryan)- colors especially

2. Joint meeting with Ruminate + dev team at 1:30pm EST https://meet.google.com/nqw-ywcr-eso | Tue, 08/09 | N/A | https://techfleet-ruminate-design.vowel.com/#/g/mf61y62feikfisjr

Note: (20 min long due to overlap with other joint meeting) | | Review Design Handoff | N/A | Wed, 08/10 | N/A | | | Review Design Handoff | 1. - Producer Dashboard - 1/7 users could not find the Completed Evaluations (Usability Test) - Results Summary - “Question 1 / Response Summary” text <-- check accessibility colors, lime green background with dark blue text - Download button- did not get a chance to double check with Dev Team whether feasible (for Phase 2) | Thur, 08/11 | 1. Add Product Intake Form (before Design System slides) and Grids slides to Design Handoff - Jasmine

2. Copy pages into new design file (final design)

Figma Final Design Handoff File: https://www.figma.com/file/N6adkH27O75gaiSObPfytw/Ruminate-Design---Handoff?node-id=6%3A291 | https://techfleet-ruminate-design.vowel.com/#/meeting/TSwuikrYjKjVqAWH | | | | Fri, 08/12 | Sprint Demo Week 8 (Amitha) FINAL WEEK! | https://techfleet.vowel.com/#/g/8hpjssbujq4jkej4 |