Design Systems: Design - 2023 Agenda #464

kangina-tech · 2023-01-12T21:44:02Z

Overview

This issue tracks the agenda for the DS: Design meetings in 2023. This will help us stay focused on the goal and have a place to document meeting notes and action items for the following weeks. Weekly meetings for the Design team occur on Thursdays at 10:30 am PST.

Meeting Links

Zoom Link

Template

### **[1/12/2023] Agenda and Notes**

**- [ROLL CALL](https://docs.google.com/spreadsheets/d/1JtJGxSpVQR3t3wN8P5iHtLZ-QEk-NtewGurNTikw1t0/edit#gid=1199107562) -**
Present: 


**- RECURRING ITEMS -**
- [ ] Review any issues that are in the [new issue approval column](https://github.com/hackforla/design-systems/projects/1#column-15133576)
- [ ] Accountability and support check.
- [ ] Review assignments


**- AGENDA -**
- [ ] New items for meeting discussion


**- MEETING NOTES -**
- Quick notes about meeting for review


**- ACTION ITEMS -**
- [ ] Items to do


**- RESOURCES -**
[Figma file](https://www.figma.com/file/5NacfOm45QlrWgr6wWEg4k/Design-System-Template-for-HfLA?node-id=2%3A54&t=r0qPxeKsx29UQhk6-0)
[HfLA Figma Kit](https://www.figma.com/file/XIy3Dciciej4Q6A1TXGMS1/HfLA-Figma-Kit?node-id=2%3A16&t=SAwrdulQxK1A00A7-0)
[Old Design Systems Research](https://www.figma.com/file/UvUJ0zT2EEIOoDQVdn6ApN/Design-Systems-Team-Figma?node-id=0%3A1&t=iCGOD877P5TUJBSz-0)


**[TOP OF PAGE](https://github.com/hackforla/design-systems/issues/464#issue-1531409944)**

DS: UX/UI Team Meetings (2022) #264

The text was updated successfully, but these errors were encountered:

khanhcao17 · 2023-01-12T23:25:17Z

khanhcao17 · 2023-01-13T23:33:05Z

[1/19/2023] Agenda and Notes

- ROLL CALL -
Present: Yas, Liz, Michael, Khanh, Debbie, Asad

- RECURRING ITEMS - [5-10 minutes]

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- [Liz] Audit published Figma kit
- [Michael] Audit published Figma kit
- [Asad] Audit published Figma kit

- AGENDA -

- MEETING NOTES -

Check research notes on Github
We need content designers! Please let us know if you are interested or know someone who is interested
- Action Item: [Yas] Post content design on open position board
Thoughts on Figma Kit
- Liz
  - Confused initially about goal
  - Action Steps on "Start Here" page is too small and confusing
  - Confused about "Numbered tasks" - Do we want to add numbers onto the headers?
  - Some disconnect on layouts of the page
  - "Standards" and "Action Steps" feel a little redundant.
  - Iconography - Confusing? Is it needed?
- Michael
  - Noted on "Iconography" - Is there a guide for icons? Related icons?
  - Liked Sandboxes on the file
  - Big headers vs. small body text
- Asad
  - "Give your file a cover" - Maybe breakdown the action steps more.
  - Importance of housekeeping
  - Adding more pages
  - Making font larger
Kanban method
- Issues will be created on Github by either Debbie or Khanh
- Designers are free to add themselves onto any of the issues in the "BACKLOG" with "DESIGN" labels and move them into the "IN PROGRESS" section.
- These issues/tickets will be used for documentation.
  - Designer will document any updated designs by adding a date to the initial comment and then add another comment with a date, a screenshots, note any changes, and if it's ready to be sent off to another team.
- Contact Khanh if there are any questions
- *This is also a new method and if there are any improvements that can be made, please let us know!
Working with other teams (Content and Research)
- We are still working on how to collaborate with other teams on the Figma file.
- For Github, if you are ready to pass the project onto another team, please contact the team and then figure out who you'll be working with for your page and add them onto the Github issue/ticket.
Assign projects on Github
- [Asad] General rules
- [Michael] Most recent
- [Liz] Documentation

- ACTION ITEMS -

[Yas] Post content design on open position board
[Asad] Housekeeping - General rules - Research
- [Asad] Need to start issue for onboarding
[Michael] Housekeeping - Most recent - Research
- [Michael] Need to start issue for onboarding
[Liz] Housekeeping - Documentation - Research

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-01-20T00:39:18Z

[1/26/2023] Agenda and Notes

- ROLL CALL -
Present: Liz, Khanh, Yas, Michael, Wataru, Asad

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- [Asad] Housekeeping - General rules - Research
  - [Asad] Need to start issue for onboarding
- [Michael] Housekeeping - Most recent - Research
  - [Michael] Need to start issue for onboarding
- [Liz] Housekeeping - Documentation - Research

- AGENDA -

Recurring items [3 minutes]
Future ideal meetings - 20 minutes of meeting time, 40 minutes of design time [2 minutes]
Content/Design sync page [5 minutes]
Case study/timeline template [5 minutes]
General Housekeeping discussion - helping everyone really define what Housekeeping means[15 minutes]
Specific Housekeeping discussion from what was researched [15 minutes]
General timeline discussion [15 minutes]

- MEETING NOTES -

Future meetings will be trying to focus more on giving updates and actively designing.
[Khanh] is figuring out how to best make a Figma page for DESIGN and CONTENT to put finished works on.
[Debbie] is figuring out how to make a Figma page for us to document our work into "case study" ready segments.
General Housekeeping discussion
- Housekeeping is about keeping files tidy and holding people accountable to that.
- Is housekeeping a subset of the kinds of rules we are trying to provide for designers?
- Ground rules vs. Housekeeping
  - Ground rules - General
    - ex. Don't delete Figma pages.
  - Most recent
  - Documentation
Specific Housekeeping discussion
- General Housekeeping [Asad]
  - Asad's Research
  - Creating a shared vision
  - Sitemap
  - Clean up often!
  - Instead of commenting - create text boxes
  - Emoji feedback
  - Don’t delete other people’s work
  - Keep workspace/pages tidy
  - Name pages.. clearly
  - Follow page naming convention
- Housekeeping - Documentation [Liz]
  - *Research can be found in Figma
  - Each group already has their own Wiki with general information so we don't need to research about overall documentation.
  - We would want to find more information about how designers can communicate their thoughts as their designs progress on Figma. And more about any updates for a design, examples would be writing notes about why and how things were updated.
- Housekeeping - Most Recent [Michael]
  - Setting the stage - “What’s New” page with current stage of process
  - Archive what’s already been developed to highlight newer designs
  - Iteration sections
  - Documentation (?) - Document what’s changed in iteration
  - Having a handoff or in-development section
  - Suggesting if latest iteration should be higher up or chronologically
General Timeline
- Released Figma Kit
  - RESEARCH should be done with their first round of user testing by end of February
  - DESIGN will take the findings and work on revamping the current pages and finalizing the style guide for the Figma Kit.
  - DESIGN will then give RESEARCH the updated design for additional research.
- Housekeeping sections
  - DESIGN plans to finish up low fidelity draft of Housekeeping pages by end of February
  - DESIGN will then handoff lofi draft to RESEARCH for additional research.
- Will try to work on Accessibility, Colors, and Typography pages after Housekeeping pages have been completed with high fidelity for V2 release.
*Check Robert's Sandbox on the Figma file for previous Housekeeping pages.
RESEARCH want to see if they can have members who are working in other projects (Michael and Asad) or just newer members (LIz) do a test run of the user testing sessions on Monday.

- ACTION ITEMS -

~~[Khanh] Work to complete CONTENT/DESIGN Sync page.~~
~~[Debbie] Work to complete Case Study Ready page.~~
[Asad] Create a low fidelity version of Housekeeping General Rules page.
- Make this page more of a working page rather than just a landing page introducing Housekeeping.
- Try to fit everything onto one page, but if it's too long then we can discuss either slashing some content or creating two separate pages.
[Liz] Create a low fidelity version of Housekeeping - Documentation page.
- Consider whether or not we want to figure out one best practice that everyone must follow OR emphasizing on the importance of documentation and suggesting different methods of documentation that other groups can adopt.
[Michael] Create a low fidelity version of Housekeeping - Most Recent page.
- Emphasize on the importance of labeling "Most Recent" and suggesting different methods of that other groups can adopt.

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-01-28T21:45:27Z

[2/2/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Debbie, Yas, Liz, Asad, Rachel

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- ~~[Khanh] Work to complete CONTENT/DESIGN Sync page.~~
- ~~[Debbie] Work to complete Case Study Ready page.~~
- [Asad] Create a low fidelity version of Housekeeping General Rules page
- [Liz] Create a low fidelity version of Housekeeping - Documentation page.
- [Michael] Create a low fidelity version of Housekeeping - Most Recent page.

- AGENDA -

Recurring items [3 minutes]
[Asad] Housekeeping General Rules low fidelity page [15 minutes]
[Liz] Housekeeping - Documentation low fidelity page [15 minutes]
[Michael] Housekeeping - Most Recent low fidelity page [15 minutes]

- MEETING NOTES -

Housekeeping - Documentation
- Liz's current version is a step-by-step guide on how to document one specific way.
- Yas suggested doing only examples on how to document.
- Khanh suggested having certain standards for documentation (ex. date and details) AND showing examples.
Housekeeping - Most Recent
- Michael had posted his iterations but was not present to present his pages.
- Everyone will leave comments after looking over.
Housekeeping - General
- Asad had two versions: everything on one page or everything a little more separated.
- There were some things that can be included in the previous "Start here" pages but it's a good start.

- ACTION ITEMS -

[Everyone] Look at the current Housekeeping pages that have been posted on the whiteboard and comment!
[@TobyShanti ] Housekeeping General Rules low fidelity page
- See comments and work accordingly, feel free to discuss more about any comments that are confusing.
- More research done for more general housekeeping
[@liz-zheng ] Housekeeping - Documentation low fidelity page
- See comments and work accordingly, feel free to discuss more about any comments that are confusing.
- More research to see what other teams are doing for documentation.
- Research more on what are best practices for documentation (ex. Is it important to date changes or what are details that should be noted when documenting or how to document for different team members (devs, designers, PMs))
[@mklmrgn l] Housekeeping - Most Recent low fidelity page
- See comments and work accordingly, feel free to discuss more about any comments that are confusing.
[Rachel] Audit current pages and reach out to CONTENT (Sandra or Robert)

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-02-09T02:34:11Z

[2/9/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Debbie, Wataru, Asad, Michael, Liz, Yas, Josh

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- [Everyone] Look at the current Housekeeping pages that have been posted on the whiteboard and comment!
- [Asad] Housekeeping General Rules low fidelity page
  - Changes based on comments
  - More research
- [Liz] Housekeeping - Documentation low fidelity page
  - Changes based on comments
  - More research - other team documentation and best practices
- [Michael] Housekeeping - Most Recent low fidelity page
  - Changes based on comments
- [Rachel] Audit current pages and reach out to CONTENT (Sandra or Robert)

- AGENDA -

Recent updates - New PM and new project. [5 minutes]
~~[Rachel] Go over her opinion of the current pages and any other opinions. [5 minutes]~~
[Asad] Housekeeping General Rules low fidelity page [10 minutes]
[Liz] Housekeeping - Documentation low fidelity page [10 minutes]
[Michael] Housekeeping - Most Recent low fidelity page [10 minutes]

- MEETING NOTES -

Josh will be joining as our new HfLA Design System PM.
Debbie and Khanh will be working on a Design System template update per Bonnie's request.
Housekeeping - General [Asad]
- Not much update had been done.
- Had a further discussion about vision being in the Housekeeping rules.
  - FINAL DECISION: Vision can be explored more outside of the Housekeeping rules.
- Housekeeping general rules should be more about keeping Figma file "tidy".
Housekeeping - Most Recent [Michael]
- Michael went over his low fidelity design.
- Had a chat about how do documentation and most recent designs intersect.
- Emphasized that DESIGN doesn't have to worry too much about wording because CONTENT will help.
Housekeeping - Documentation [Liz]
- Liz shared additional research and new low fidelity design.
- Liz planning on doing additional research and interviewing a dev.

- ACTION ITEMS -

[Everyone] Please update your GitHub issues!
[@TobyShanti ] Housekeeping General Rules low fidelity page
- More research done for more general housekeeping
[@liz-zheng ] Housekeeping - Documentation low fidelity page
- More research to see what other teams are doing for documentation.
- Research more on what are best practices for documentation (ex. Is it important to date changes or what are details that should be noted when documenting or how to document for different team members (devs, designers, PMs))
[@mklmrgn l] Housekeeping - Most Recent low fidelity page
- Figuring out what to note for Most Recent that doesn't overlap too much with "Documentation"

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-02-14T22:44:31Z

[2/16/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Debbie, Wataru, Sandra, Yas, Liz, Asad, Michael, Rachel

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- [Everyone] Update your GitHub issues
- [Asad] Housekeeping General Rules low fidelity page
- [Liz] Housekeeping - Documentation low fidelity page
- [Michael] Housekeeping - Most Recent low fidelity page

- AGENDA -

[Khanh] General Housekeeping [10 minutes]
- Can we change the names of the files?
  - Design System Template for HfLA -> HfLA DS Team - Figma Kit
  - Design Systems Team Figma -> HfLA Design System Template
- How to update your GitHub issues
- How to document on the Whiteboard page of the Figma file
~~[Rachel] Go over her opinion of the current pages and any other opinions. [5 minutes]~~
[Asad and Rachel] General questions [20 minutes]
- HfLA Figma Kit order - Hot Take - Housekeeping rules first?
  - *Yas's note - We have to find a way to manage the repetitive content. The only definitive feedback I can provide right now is we will not change the Kit overall information architecture to bring Housekeeping first. I understand why you both feel bringing the housekeeping first makes sense. But I believe it is because of the content you choose to put there. Again the Kit is not about how teams should design or how should their design process look but it is about how they should structure their Figma file and build their design systems.
- Kit repetition - Ex. Keeping team members informed vs. Documentation and Most Recent content
  - Housekeeping - General summary with option to learn more - Click into Documentation and Most Recent
- Create user flows
Housekeeping wireframe updates [30 minutes]

- MEETING NOTES -

Will be switching the file names.
- Active Figma Kit work will be done in the figma file "Design Systems Team Figma"
- Design System Template will be named "HfLA Design System Template"
Went over proposed method of documentation for GitHub.

Reviewed over whiteboard documentation method.

Yas had shown information architecture chart to help clear up confusion.
Housekeeping "General Rules" is to be structured more like a general guideline similar to a table of contents and if people are confused or want to learn more about documentation or most recent they would go into those pages.
Goal of Asad doing additional research was to try and not let older members' decisions affect the final page design.
- If more pages are needed to be created based on research information that's fine.
- If there's any overlapping information, then figure out what overlaps and adjust accordingly.
Reevaluated Michael's page to see what more could be done. Determined that maybe more research needs to be found on methods of recording latest update and to see what common patterns could be found.
Wataru also noted that we should look more deeply into how designers and developers work together. As well as looking into how documentation should be done in order to converse with developers (ex. how certain things work in a mockup).
Yas then mentioned about the design system template projects and asked Wataru to meet with Debbie, Khanh, Yas, and Josh in some capacity.

- ACTION ITEMS -

[@liz-zheng] Look more into the relationship between designer and developer to develop our "Documentation" page.
[@mklmrgn and @liz-zheng ] Work together to see how to best divide information so that there's not too much repetition between both pages.
[@mklmrgn] Find common patterns in how people document updates (ex. Do they use colors or positions? Or do they use numbering and words?)
[@TobyShanti] Work to build the general rules page. If there's time, feel free to also look into if we want to build out a "Vision/Purpose" page to add in before housekeeping rules.

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-02-22T23:31:31Z

[2/23/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Debbie, Sandra, Asad, Liz, Michael, Yas

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- [Liz] Look more into the relationship between designer and developer to develop our "Documentation" page.
- [Michael and Liz] Work together to see how to best divide information so that there's not too much repetition between both pages.
- [Michael] Find common patterns in how people document updates
- [Asad] Work to build the general rules page. If there's time, feel free to also look into if we want to build out a "Vision/Purpose" page to add in before housekeeping rules.

- AGENDA -

Renaming Figma files (5 minutes)
Review assignments. (30 minutes)
Design system update - Universal template. (25 minutes)

- MEETING NOTES -

Wanting to name the files better to be less confusing to newcomers
- Tabling for a later discussion
- Everyone should better understand what each Figma file's goals are before we can better name
Asad has updated his page to be more like a table of contents.
Liz has updated to reflect more of what she has researched, added more recommendations.
- We might want to move the "page layout" section to general rules.
Michael and Liz had chatted about removing repetitive information.
We want to see more high level examples of ways to document the latest/most recent designs.
- Instead of telling designers to use a different page for the newest designs are marking off a certain section for newest designs, we recommend that one way they can different newer designs from older designs is separate spaces.
We tried to narrow down the goal of updating the "HfLA Design System Template" by trying to truly understand Bonnie's goals and DS goals. Also we have a 2 month deadline.
- Bonnie's goals
  - Something similar to HfLA Website Design System - wants visual indicators and annotations for developers as well as developers to have their design system on the Figma file as well
  - Wants something easy to copy and paste - like a "Starter Stickersheet" - wants to be able to easily start design systems for new groups
- DS goals
  - A properly researched template for others to utilize - Have a basic "Starter Stickersheet" with links that lead to more detailed research on how to properly utilize their design system
  - Want to make sure that Bonnie's needs are met while also keeping in mind that we are building this for all of HfLA to use easily whether they are designers or developers
- Suggested next steps
  - Create a "Starter Stickersheet" with different sections of the DS with one example each of each needed item.
  - Instead of just copying HfLA Website design system, let's re-evaluate what can be improved and what pain points there are potentially.
    - Example pain point - Designers know how to change buttons and place them in the design system but don't know how to adjust the coding. A developer comes along and they utilize the old code and the designs are not updated.
    - Example solution - Create a method of communication directly on the design system by adding a "date updated" section to both the design side as well as the developer side.

- ACTION ITEMS -

[Everyone] Update the Github issue based on what changes have been made!
[Everyone] Comment on whiteboard for the design system sections.
- I've put the colors and buttons sections of the HfLA Website design system onto our whiteboard. Can everyone look over the two sections and see what works for these sections and what pain points you find?
[@TobyShanti @liz-zheng @mklmrgn] Keep an eye on whatever changes content makes and make sure that what you're trying to say is clear to content.
[Content] Going over current "Housekeeping pages" and make comments on content.

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-02-24T01:00:41Z

[3/2/2023] Agenda and Notes

- ROLL CALL -
Present:
Debbie, Rachel, Michelle, Liz, Asad, Michael

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- @liz-zheng will share the new documentation style shared on the slack for better clarification for all.
- @ryayyychel and @michyeh will walk us through the new insights in regards to how content can be even more effective in curbing confusion among users and how to marry thes things with the currently developing component file.

- AGENDA -

Discuss the start of the component file. (15 mins)
Content insight walk-through. (10 mins)
Look through any new progress in individual projects. (10 mins)
Any other business. (5 mins)

- MEETING NOTES -

(Asad, Michael, Michelle, Liz, Racheal, Debbie) Why does the UI Kit need to be put together with the Software Development stuff when most designers do not feel comfortable with coding? It would be more effective if we conducted proper research on whether this is a feasible thing with all projects. Also, it would be of great benefit if we were invited to a meeting with Bonnie and fully gotten what her idea was as we seem to be at an unknown odds with it. This is also to the benefit of our content and research team. They shouldn't have to re-do design's work constantly. It can be very demotivating.
(Content team) Aside from doing a whole renaming of our kit, they are coming up with a template that can help designers know exactly what is being created and why. This is in regards to the fact that no scope has been established in our working system and as such, it is leading to unfortunate things like axing full pages and giving designers work they needn't do. It is also a template that will be easily adaptable to the other teams for other designers.
Housekeeping has been tabled for the moment. It is something that we had started working on without any defined boundaries or definition and this has led to too much confusion and too many iterations that might unfortunately be removed in favour of something completely different. (The current template comes off as though we have different personas instead of one).
(Debbie) Start with creating a component library worksheet as the timeline is dwindling and we need to have a first draft for the teams to use.

- ACTION ITEMS -

Create issues for Component Library project
Set up a possible meeting with Bonnie to get a proper picture in regards to the Coding space in design kit
~~See if research is at a space to accept new projects as we are lagging a little behind when it comes to usability studies and now the component library~~

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

kangina-tech · 2023-03-02T18:24:40Z

[3/9/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Debbie, Asad, Liz, Michael, Yas

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments

- AGENDA -

Review over stakeholder video and Q&A with Yas [15 minutes]
Share ideas for Universal Design System Template [45 minutes]

- MEETING NOTES -

Everyone watched Stakeholder Clarification Video and asked questions.
- Team goals for updated Design System Template
  - Keep developer section
  - Focus on developing the designer section for now
  - Build out the "Button" component first before building out the other components
Suggested timeline
- Week 1: Create basic template.
- Week 2 + 3: Confirm template, collect all different types of components from other teams.
- Week 4 + 5: Build out different sticker sheets, Stakeholder approval, make it pretty.
- Week 6 + 7: Present to all of HfLA, release and announce V2.
- Post release: User testing research with both developers and designers, work with developer to update.

- ACTION ITEMS -

[Everyone] Based on what was said in the meetings, further refine your template.
[Michael and Asad] Guideline for template looks really good, refine it and present at next meeting.
[Everyone] Look through GitHub issues to see if all the components look good and if we need to think about adding anymore.

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-03-09T20:23:18Z

[3/16/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Debbie, Yas, Josh, Asad, Liz, Michael, Rachel

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments

- AGENDA -

Universal Template

- MEETING NOTES -

Asad shared his design for the guideline which would help to explain the template.
- Khanh shared her new design template which adopted Liz's vertical layout but utilized the headers from her other design as well as adding the link for usage back in for reference.
Need to build out more to have a solid example to show Bonnie.

- ACTION ITEMS -

[Anyone available] Help build out something to show to Bonnie on Monday.

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-03-22T23:36:01Z

[3/23/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Sandra, Josh, Asad, Liz, Michelle, Rachel, Jennifer

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments

- AGENDA -

Updates from the stakeholder meeting on Monday [5 minutes]
Discussion about "HfLA Design System Starter" [25 minures]
Discussion about next steps [25 minutes]
Task assignment [5 minutes]

- MEETING NOTES -

Stakeholder updates
- Rather than a "Universal Design System Template" that can be adapted by all the teams currently under HfLA, Bonnie wanted something more along the lines of a "HfLA Design System Starter"
  - Meaning she wants a whole basic design system that can be copied and pasted and used immediately without any changes with design components and codes
- For the components list, well look at the "Materials UI" to help us decide what to build out
Next Steps
- Work with content team to figure out the correct name for this template
  - My suggestion is “HfLA Design System Starter”
  - Does this name best encompass what we are trying to convey?
  - Is it a starter? A basic kit? A foundation?
  - Building blocks?
- Figure out how we are going to combine the previous project of “HfLA Design System Template” with this new “HfLA Design System Starter”
- Work with content team to create a side-by-side guide for using the starter
  - Asad has started with a basic guideline.
  - Also content can feel free to look over the template and rename the categories as needed if there are better words of description.
- Create a table for color with needed basics
  - Research what colors are important for starting a project (Ex. primary brand color, secondary brand color, basic white, basic black, basic gray, positive reaction color, negative reaction color, etc.).
- Create a table for typography with needed basics
  - Research what sizes and boldnesses are the bare minimum for a website/app to get started with.
- Go through and list out the components that each of this project utilizes and then seeing what components can be combined/are the same to create a full list of components that we’ll have to build out in the next couple of weeks.
- Refine the base component table to build all the other components similarly.

- ACTION ITEMS -

[@liz-zheng] Create a table for color with needed basics.
- Research what colors are important for starting a project (Ex. primary brand color, secondary brand color, basic white, basic black, basic gray, positive reaction color, negative reaction color, etc.).
- Feel free to use Hack for LA colors as the starting point.
[@TobyShanti] Go through and list out components that the different HfLA teams use and prioritize those that are most used.
- Try to go through as many as you can on this Google Sheets.
~~Create a table for typography with needed basics.~~
Refine the base component table to build all the other components similarly.

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-03-24T02:28:53Z

[3/30/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Josh, Asad, Liz, Michael, Rachel

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- [Liz] Create a table for color with needed basics.
- [Asad and Natalie] Go through and list out components that the different HfLA teams use and prioritize those that are most used.

- AGENDA -

Naming/"Design System" placement discussion [10 minutes]
[Khanh] Present updated template and discussion. [15 minutes]
[Liz] Present table for color and discussion. [15 minutes]
[Asad and Natalie] Review over any needs for the components list. [10 minutes]
Discuss remaining assignments and next steps. [10 minutes]
- Update template - Update from discussion.
- Color template - Update from discussion.
- Components list - Next steps and completion date.
- Typography template

- MEETING NOTES -

No clear name for the "Design System" yet.
- Temporarily will refer to it as "Starter Kit" because it explains that it is a starting point that can be adjusted.
Updated template (V4)
- Updated for the base template to be the shaded example in order to offer a slight explanation to what each category is filled in for.
- Added the publish update date - Does it make sense? Does it feel needed?
- Each button column is easy to copy and can be deleted easily as well.

Components list
- Asad will be working on going through all the different files this weekend.
- Asad is planning on meeting with Natalie to go over a few of the files together to really get a hand on seeing all the proper components included in the files.
- Asad will be taking lead for this and will ask for help as needed.
Color template
- Liz did research on three different projects to see what colors they used throughout their websites.
- Liz created a color template for light and dark to be built off of showing primary, secondary, status, and grayscale colors.
- Liz has some explanations that will be written down for Content to help create a guide.

Remaining assignments and next steps
- All work done thus far should be documented onto the GitHub.
- Liz will write out additional notes about how to use color template.
- Asad and Natalie will be working to finish up the components prioritization list.
- Michael will be working on the typography template.

- ACTION ITEMS -

[@khanhcao17] Update base template
- Update documentation in GitHub
- Write out notes about how to use template
- Check about the "published updates"
[@liz-zheng] Update color template
- Update documentation in GitHub
- Write out notes about how to use template
[@TobyShanti and Natalie] Components prioritization list
- Try to get the google sheets completed by next meeting so we can get started on the top priority components
[@mklmrgn] Typography template
- Look at research already done about typography
- Do your own research about typography
- Create a basic starter template with minimum required text for a website/app

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-03-31T00:47:21Z

[4/6/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Yas, Josh, Liz, Michael

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments
- [Khanh] Update base template
- [Liz] Update color template
- [Asad and Natalie] Components prioritization list
- [Michael] Typography template

- AGENDA -

Work with Content to finalize working names for products
Review over typography template
Review over Components list
~~Review remainder of timeline - When is Bonnie expecting the release date of the "starter kit"?~~

- MEETING NOTES -

Everyone please show up to the Monday All-Hands meeting (4/10/2023) to take part in the namestorming session for two two projects.
Asad and Natalie have been working on the component audit list and they're just about done.
- The top components to work on so far are: Menu, Button, Select, Text Field, Icon, and Typography.
Michael presented his typography research and working template.
- Research was done on Civic Tech Jobs, Internship Project, and HfLA Website.
- He narrowed down that there needed to be a grouping for Desktop, a grouping for Tablet, a grouping for Mobile, and a grouping for all screen sizes.
  - It was suggested that a grouping for Tablet wasn't needed for a basic typography template.
- He included font family, weight, size, and line height.
  - It was suggested to add letter spacing and color.
  - Color with the typography was debated about because it would add more to the typography when there's already a color specific template, however it was said that it would be needed for the specific typography code.
    - More research needs to be done on this.

- ACTION ITEMS -

[EVERYONE] You are all needed for the namestorming session on Monday (4/10/2023)!
[@TobyShanti] Complete the component audit.
[@mklmrgn ] Continue on typography template work.
- Do more research to consolidate different types of typography.
- Create two different typography templates.
  - Continue to work on current typography layout.
  - Adopt the typography layout to the component template (Khanh - Component Template 4).
[@liz-zheng ] Work on component template for menu.
[@khanhcao17] Update component template to show example if the button changes sizes from desktop to mobile.

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-04-06T19:16:32Z

khanhcao17 · 2023-04-13T19:47:54Z

khanhcao17 · 2023-04-25T23:16:48Z

[4/27/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Asad, Michael, Natalie, Jiyon, Michelle, Yas, Josh

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments

- AGENDA -

[Khanh] "Button" component template
[Michael] "Typography" template
[Michael] "Cards" template
[Natalie] "Text field" component template
[Asad] "Select" component template

- MEETING NOTES -

Introducing two members of the design team:
- Jiyon - a new face to the team who has experience as a graphic designer
- Faezeh - who has been with us since November on the research team
Asad created different sizes of the select component. He still needs to reformat things.
Michael did thorough research on cards and ended up created horizontal and vertical style cards built with auto layout.
- Suggested added more padding to the margins of the cards.
- Michael is to also create cards that are buttons. What he has is cards that have buttons.
- Michael is also going to write a guide on how to use the auto layout on the cards.
Natalie showed her work with the text fields.
- It was decided that she would make text fields that are outlined.
- Also adding to the shot answer text fields, she's to make text fields with icons (like the search bar) and text fields for long answer text.
- Use Asad's "select" component as a guide to build the text fields.
Khanh updated the buttons template to show all the variations.
- Next steps will be to move the buttons to better work with the color coding.
Overall
- Josh requested adding the "Kit publish date".
- Product is ready for a rough test run with Bonnie and also with Research.
Namestorming results!
- Check Michelle's Sandbox for more details.
- Tentative new name for "Figma Kit":
  - HfLA Figma Compass
- Possible new names for "Design System/Starter Kit":
  - HfLA Component Toolbox
  - HfLA Development & Design Library
  - HfLA UI Basics
  - HfLA UI and Code Library

- ACTION ITEMS -

[Michael] "Cards" template
[Natalie] "Text field" component template
[Asad] "Select" component template
[Faezeh] "Icons" component template
[Jiyon] "Navigation" component template

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-04-27T22:27:00Z

[5/4/2023] Agenda and Notes

- ROLL CALL -
Present: Khanh, Natalie, Jiyon, Liz

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments

- AGENDA -

[Khanh] Updates from PM meeting and for content and research team
~~[Asad] "Select" component template~~
~~[Michael] "Cards" template~~
[Natalie] "Text field" component template
~~[Faezeh] "Icons" component template~~
[Jiyon] "Navigation" component template
[Liz] "Header and Footer" component template

- MEETING NOTES -

During the PM meeting with Bonnie (the stakeholder) on Monday, we shared our updates on the component template project as well as the update on the renaming of the projects.
- Bonnie was pleased with our progress for the component templates.
- She had some questions about the typography component so we'll have to go over that component again.
- She's neutral about the name changes and says she does not have much input but recommended that the team does some user research for the new name of the component template.
I met with the content team to ask them to get started on working on short blurbs for the different component templates so if y'all are reached out to by someone on the content team, please work with them to help figure out how to explain each different component template.
I met with the research team to ask their opinion on whether we should do usability testing on the component templates before release or not.
- Initially, Research recommended that we do research before release but I had commented that it would be quite the large research project because of all the different parts.
- After discussion with Design, we suggested doing user interviews on teams that have tried to utilize the new component template system to help build their own design systems.
  - Perhaps maybe asking Bonnie to encourage a couple of teams to use it and then interview them after a month of use.
Jiyon had a busy week and Liz just got back from vacation so neither of them had any updates.
Natalie had an update on the "text field" component template.
- It was decided that she'd look closer at the different states.
  - Look more about how the text field sits when we doing interact with them and then how it changes when we hover over, press on it, and cause an error.
- Additional text fields to work on:
  - Text fields with icons (ex. Search bar)
  - Password text fields (ex. having the password hidden dots vs. revealing the password vs. creating a new password and having requirements)
  - Big paragraph text field (ex. long answer question text boxes)

- ACTION ITEMS -

[Asad] "Select" component template
[Michael] "Cards" template
[Natalie] "Text field" component template
[Faezeh] "Icons" component template
[Jiyon] "Navigation" component template
[Liz] "Header and Footer" component template

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

khanhcao17 · 2023-05-09T13:24:40Z

[5/11/2023] Agenda and Notes

- ROLL CALL -
Present: Michael, Faezeh, Jiyon, Liz, Joshua, Yasaman, Asad

- RECURRING ITEMS -

Review any issues that are in the new issue approval column
Accountability and support check.
Review assignments

- AGENDA -

[Content] Check design dictionary/blurb if completed and see if it would help make our template make sense to someone seeing it for the first time.
[Asad] "Select" component template
[Michael] "Cards" template
[Natalie] "Text field" component template
[Faezeh] "Icons" component template
[Jiyon] "Navigation" component template
[Liz] "Header and Footer" component template

- MEETING NOTES -

-Asad is continuing work on his select component.

Upon feedback from the group, he is going to change the different sizes of the component to reflect desktop and mobile screens. He is also going to expand on the different states of the components. Target completion date is before our next meeting.

-Micheal shared his progress on the card components. He has been updating the padding and the descriptive details portion.

Micheal will be working on adding elevation to his component.

-Faezeh has recently joined our group and has been conducting research on her icon component

Joshua clarified that there is no need to create the icons from scratch but to rather find a system and include it in our design system.

-Jiyon recently joined our team as well. Jiyon shared findings from research conducted on the assigned component navigation.

-Liz has been conducting research on the assigned component and presented her findings.

-Yasaman will be checking in with the content team in regards to the design dictionary/blurb.

-At the moment designers are at capacity but will choose from the remaining component templates once they have completed their current components.

-Some bigger picture conversations that arose while reviewing everyone's components:

Designers are going to need to start thinking about following the same style for components to ensure uniformity.
We should be defining items such as spacing for components for the same reason of uniformity.
Designers should ensure uniformity in presentation.

- ACTION ITEMS -

Items to do

If anyone completes their component template this week, here are the remaining component templates to be created:

"Button groups" component template
"Checkbox" component template
"Accordion" component template

- RESOURCES -
Figma file
HfLA Figma Kit
Old Design Systems Research

TOP OF PAGE

kangina-tech added feature: agenda meeting notes 👤 Design Role: UX design skill set labels Jan 12, 2023

kangina-tech assigned khanhcao17, kangina-tech, allthatyazz, sandraberjan, rsschacht and liz-zheng Jan 12, 2023

kangina-tech added the 👤 Content Role: Content designers tasks label Jan 12, 2023

khanhcao17 assigned winoue90 and edela0015 Jan 13, 2023

khanhcao17 mentioned this issue Jan 16, 2023

Creating New Agenda for 2023 Design Meetings #462

Closed

10 tasks

allthatyazz mentioned this issue Jan 17, 2023

Creating New Agenda for 2023 Research Meetings #477

Closed

10 tasks

khanhcao17 changed the title ~~Design Systems: UX/UI - 2023 Agenda~~ Design Systems: Design - 2023 Agenda Jan 18, 2023

allthatyazz mentioned this issue Jan 24, 2023

Design Systems: Team- 2023 Agenda #478

Open

khanhcao17 assigned mklmrgn and TobyShanti and unassigned edela0015 Jan 24, 2023

khanhcao17 assigned ryayyychel and michyeh and unassigned rsschacht Mar 24, 2023

allthatyazz mentioned this issue Apr 4, 2023

Re-naming of Design Systems Template #510

Open

9 tasks

khanhcao17 assigned Natalie-Aguilar and unassigned kangina-tech Apr 13, 2023

khanhcao17 assigned fuzjan81 and unassigned winoue90 Apr 25, 2023

khanhcao17 unassigned ryayyychel Apr 27, 2023

allthatyazz added this to the 01. Team Workflow milestone May 10, 2023

ExperimentsInHonesty added B: DS Team Initatives B: Documentation labels Aug 13, 2024

ExperimentsInHonesty added this to DS: Project Board Aug 13, 2024

ExperimentsInHonesty moved this to 🏠 START HERE 🏠 in DS: Project Board Aug 13, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Design Systems: Design - 2023 Agenda #464

Design Systems: Design - 2023 Agenda #464

kangina-tech commented Jan 12, 2023 •

edited by khanhcao17

Loading

khanhcao17 commented Jan 12, 2023 •

edited

Loading

khanhcao17 commented Jan 13, 2023 •

edited

Loading

khanhcao17 commented Jan 20, 2023 •

edited

Loading

khanhcao17 commented Jan 28, 2023 •

edited

Loading

khanhcao17 commented Feb 9, 2023 •

edited

Loading

khanhcao17 commented Feb 14, 2023 •

edited

Loading

khanhcao17 commented Feb 22, 2023 •

edited

Loading

khanhcao17 commented Feb 24, 2023 •

edited

Loading

kangina-tech commented Mar 2, 2023 •

edited by khanhcao17

Loading

khanhcao17 commented Mar 9, 2023 •

edited

Loading

khanhcao17 commented Mar 22, 2023 •

edited

Loading

khanhcao17 commented Mar 24, 2023 •

edited

Loading

khanhcao17 commented Mar 31, 2023 •

edited

Loading

khanhcao17 commented Apr 6, 2023 •

edited

Loading

khanhcao17 commented Apr 13, 2023 •

edited by TobyShanti

Loading

khanhcao17 commented Apr 25, 2023 •

edited

Loading

khanhcao17 commented Apr 27, 2023 •

edited

Loading

khanhcao17 commented May 9, 2023 •

edited by TobyShanti

Loading

Design Systems: Design - 2023 Agenda #464

Design Systems: Design - 2023 Agenda #464

Comments

kangina-tech commented Jan 12, 2023 • edited by khanhcao17 Loading

Overview

Meeting Links

Template

khanhcao17 commented Jan 12, 2023 • edited Loading

[1/12/2023] Agenda and Notes

khanhcao17 commented Jan 13, 2023 • edited Loading

[1/19/2023] Agenda and Notes

khanhcao17 commented Jan 20, 2023 • edited Loading

[1/26/2023] Agenda and Notes

khanhcao17 commented Jan 28, 2023 • edited Loading

[2/2/2023] Agenda and Notes

khanhcao17 commented Feb 9, 2023 • edited Loading

[2/9/2023] Agenda and Notes

khanhcao17 commented Feb 14, 2023 • edited Loading

[2/16/2023] Agenda and Notes

khanhcao17 commented Feb 22, 2023 • edited Loading

[2/23/2023] Agenda and Notes

khanhcao17 commented Feb 24, 2023 • edited Loading

[3/2/2023] Agenda and Notes

kangina-tech commented Mar 2, 2023 • edited by khanhcao17 Loading

[3/9/2023] Agenda and Notes

khanhcao17 commented Mar 9, 2023 • edited Loading

[3/16/2023] Agenda and Notes

khanhcao17 commented Mar 22, 2023 • edited Loading

[3/23/2023] Agenda and Notes

khanhcao17 commented Mar 24, 2023 • edited Loading

[3/30/2023] Agenda and Notes

khanhcao17 commented Mar 31, 2023 • edited Loading

[4/6/2023] Agenda and Notes

khanhcao17 commented Apr 6, 2023 • edited Loading

[4/13/2023] Agenda and Notes

khanhcao17 commented Apr 13, 2023 • edited by TobyShanti Loading

[4/20/2023] Agenda and Notes

khanhcao17 commented Apr 25, 2023 • edited Loading

[4/27/2023] Agenda and Notes

khanhcao17 commented Apr 27, 2023 • edited Loading

[5/4/2023] Agenda and Notes

khanhcao17 commented May 9, 2023 • edited by TobyShanti Loading

[5/11/2023] Agenda and Notes

kangina-tech commented Jan 12, 2023 •

edited by khanhcao17

Loading

khanhcao17 commented Jan 12, 2023 •

edited

Loading

khanhcao17 commented Jan 13, 2023 •

edited

Loading

khanhcao17 commented Jan 20, 2023 •

edited

Loading

khanhcao17 commented Jan 28, 2023 •

edited

Loading

khanhcao17 commented Feb 9, 2023 •

edited

Loading

khanhcao17 commented Feb 14, 2023 •

edited

Loading

khanhcao17 commented Feb 22, 2023 •

edited

Loading

khanhcao17 commented Feb 24, 2023 •

edited

Loading

kangina-tech commented Mar 2, 2023 •

edited by khanhcao17

Loading

khanhcao17 commented Mar 9, 2023 •

edited

Loading

khanhcao17 commented Mar 22, 2023 •

edited

Loading

khanhcao17 commented Mar 24, 2023 •

edited

Loading

khanhcao17 commented Mar 31, 2023 •

edited

Loading

khanhcao17 commented Apr 6, 2023 •

edited

Loading

khanhcao17 commented Apr 13, 2023 •

edited by TobyShanti

Loading

khanhcao17 commented Apr 25, 2023 •

edited

Loading

khanhcao17 commented Apr 27, 2023 •

edited

Loading

khanhcao17 commented May 9, 2023 •

edited by TobyShanti

Loading