Ruminate Design Meeting

Attendance: All of design + PM + John

Date: 11/14/2023

📝Agenda:

  1. John & components:
      1. John went over confusions with components
      2. Buttons:
        1. Understand the difference between the primary buttons
        2. Didn’t understand difference between secondary buttons other than change in shape
        3. Mentioned how the buttons will be manual for now but will have to change it to permanent.
        4. Referred to Komal note about the buttons and how it is in progress, but to focus on the medium and long.
      3. Typography:
        1. Heidi tagged Sally in figma regarding medium weight
      4. Measurements:
        1. Dev. will use ‘dev. mode’ for spacing mainly
        2. Will lock measurements/spacing from here on out
          1. Only do detailed measurements if you want to hi light something
      5. Navigation Bar:
        1. No stick nav. bar
        2. Would like to have a CTA button that is visible at all time for users while completing forms, saying “Back To Top” so users can move to the top quickly if needed.
  2. Components and Style Guide:
    1. Keep style guide with the components in the “Components” Page
    2. Heidi asking for other ways to org. style guide and comp that have worked
    3. No copying and pasting components to dev page with prototype (aka no duplicating components), dev. can go to the parent and look at it in our “Components” page John
    4. Design team: whoever is responsible for a certain components will be responsible for MOVING it in the “Components” page so team can use and reference
      1. Do NOT copy components
      2. once done creating (and approved by komal and heidi)
      3. click component
      4. right click
      5. find “Move to page”
      6. and then select “components” page
    5. Gray scale everything moving forward
    6. Don’t skil heading labels, if you need to make a custom note.
    7. Only user typography styles in figma
  3. Clickable stuff:
    1. Desktop: 24x24 frame, ex. if your frame is 22, make it 24.
  4. Distinguish links on annotations.
    1. Buttons are actionable things
    2. Links take you somewhere
  5. Team review page:
    1. If you need comments on your work, leave it in the “Team Review” page
    2. Once you have fixed/taken in advice, ping Komal and Heidi for lead review
    3. Once Approved right click the work and select move to “Developer Handoff” page (so the comments can follow)
  6. Sally show and tell:
    1. Wahoo!!
    2. Sally will use the two website that Kara and Ryan are like to create pricing page
      1. https://www.squarespace.com/pricing
      2. https://asana.com/pricing
    3. First Sally will place screen shot in “cleint review” page in the CLIENT file and tag them to see what they liked so don’t have to wait on comments for a meeting.

:🏓Tabling:

  1. NA

📆Tentative Schedule:

  1. Lo//mid fi by Friday on assigned pages
  2. Meet up tentatively Wed or Thursday to put things together

✨Takeaways: