-
-
Notifications
You must be signed in to change notification settings - Fork 1
Agenda for week of August 16th 2021 #53
Comments
DEV UPDATEWhat we did last week
What we are doing this week
|
@ahoang94 to continue working on Issue hackforla/admin#33 once that is completed we can present to Bonnie. Please do a mid check in with PM. Research team have shared the Google Document hackforla/product-management#52 with the wider team to add their assumptions - @nasimbiglari will mention the team members in the comment section. Please give them a deadline of when you want their responses. Research will also be working on hackforla/product-management#55. @irisxie to share the document with the wider team on Slack. On Wednesday the UX/UI team will discuss the Issues that @daniellex0 has created. Developers - see above. Hana and Danielle to work through the Guides team questions above and look at the second draft - hackforla/product-management#58 PM to create new Issues and address Issues in the 'Review' column |
@ExperimentsInHonesty please see below the responses from Danielle and I. I messaged you on Slack to put in a weekly meeting last week but assume you missed it. Do you have availability on Monday?
At this stage we are not covering this in our guide however will note that there is a separate guide on how to set up your Figma file effectively. Potentially this Figma Effective Practices guide can link out to our Design Systems Figma file as an example of how a Design System can look.
Our Design Systems guide can replace this issue, unless the purpose of this issue is to tell all PM’s to ensure their projects have Design Systems. Please let us know if it is the latter.
This guide does not relate to what we are currently working on.
This guide does not relate to what we are currently working on.
There are a few typography guidelines in the Design Systems guide, but it would be good to have a dedicated typography guide with more details. Whoever is working on this guide can reference the typography section of our guide.
This guide does not relate to what we are currently working on.
There are accessibility guidelines in the Design Systems guide, but it would be good to have a dedicated accessibility guide with even more details. Whoever is working on this guide can reference the accessibility section of our guide. Ciara Salmon is our dedicated Accessibility advisor, and is already attached to this Issue. Please discuss with her.
This guide does not relate to what we are currently working on.
This guide does not relate to what we are currently working on.
This guide does not relate to what we are currently working on. |
Answers to the above
Answer Please show me what you are creating at our next meeting.
Answer: This is where whoever is working on the project who is collecting links to all the existing figmas for all projects, should put the links and notes about which examples are best to use. Then this issue could referenced when needed both by your project and by product manager and UI/UX people who don't yet have access to your design system guidance. It was originally intended to be the way we developed new figmas, but I can revise it to just be a inventory of figmas with notes saying people should reach out to the design systems team if they need help with new project design system setup.
ok |
|
agenda for design team meeting on the 18th Date Attendance Meeting Notes Review typography examples from other organizations (Design + content) Inclusion of Design Tokens: Possible feature in future MVP (version hackforla/product-management#3?) Horizontal vs. Vertical layout Typography guidelines Actions For Other Teams Resources |
Overview
During the last week the three teams (Research, UX/UI, Development) have been focusing on Issues as well as how the individual teams will be working. This weekly meeting will be discussing Issues and the development team will be showing their process.
Action Items
Resources
Design System Team Agenda overview
The text was updated successfully, but these errors were encountered: