Open Hanastevenson opened 3 years ago
@Hanastevenson please update this with links to the past and future agendas, so that I have a way to find previous items we have talked about and that I have a place to store new items I want to address.
Please add this to our next agenda (if you need clarification), or just add to your team agenda if you understand This issue https://github.com/hackforla/UI-UX/issues/25, is supposed to be a place where we store resources for designers, that will eventually end up being added to the toolkit portion of the website under external resources. You post items all the time in the chat, and I think it would be good to capture them in this issue so that we can decide what to put on the toolkit page. For example the Videos series about typography.
@ExperimentsInHonesty Past and future agendas are now in the comment section above. Feel free to add more actions to the Issue if you need to. In terms of the resources, we actually had this discussion with the team on Monday, next Monday they will be bringing their thoughts on how as a team they wish to collate the resources for Design Systems.
As a team we are also trying to include our thoughts in the Discussion tab. The idea is that team members bring their thoughts to the meeting and then paste them into the Discussion in case other members miss a meeting. We can discuss this further in our 1-2-1.
@ExperimentsInHonesty I have also been collating the resources here
24th January Agenda and Notes
Monday 7th February Agenda and Notes
Ryan will be closing this ticket since Hana does not have edit rights in the old figma file. https://github.com/hackforla/design-systems/issues/114
14th February Agenda and Notes
3/3/22 Agenda and Notes
[x] Ask for Bonnie's help with setting up the zoom account
[x] Discuss new members (Cherilyn and Tammy)
[x] Discuss the usability testing
[ ] Carry forward the "New Items" that we did not get to look at today
3/7/22 Agenda and Notes
Where can team members find the Vision and Mission of Hack For LA?
3/14/22 Agenda and Notes
3/21/22 Agenda and Notes
Please add to your next agenda
@allthatyazz We are trying to secure some social media accounts for your team. It seems like your team has already setup an Instagram account using the email address designsystems@hackforla.org, but we don't know what it's username is? I don't see any issues with the word Instagram in it. Please reach out to Hana to find out if she knows anything about it.
@allthatyazz We are trying to secure some social media accounts for your team. It seems like your team has already setup an Instagram account using the email address designsystems@hackforla.org, but we don't know what it's username is? I don't see any issues with the word Instagram in it. Please reach out to Hana to find out if she knows anything about it.
@ExperimentsInHonesty Thank you for bringing this to my attention. There is also no email in our inbox indicating that we previously had set up an IG account, however, there is a verification code sent by Instagram on March 22. I will reach out to the previous PM to get more detail.
4/11/22 Agenda and Notes
4/20/22 Agenda and Notes
Quick checks
[x] Drive Privacy
Discuss in detail
There would be no PM/Stakeholder meeting on the 4th week of every month from now on. This is going to be ED time-off in exchange for the weekends she works. During this time, Bonnie would be %100 off. For technical emergencies, there is an admin channel on slack. The only emergency that requires urgent attention would be breaching the code of conduct and in that case, Dean Chuch is the point of contact.
5/2/22 Agenda and Notes
5/9/22 Agenda and Notes
You never signed off on this https://github.com/hackforla/website/issues/2745. Can I confirm that it was completed (by leaving a LGTM comment)? If you have new people to add or remove, please open a new issue for changes
6/6/22 Agenda and Notes
This meeting was cut short because ED was not feeling well. We also changed our meeting times to the First and Third Monday of each month. The calendar invite was set by the PM.
7/18/22 Agenda and Notes
- [ ] Create a Design System Page for your Project
- [ ] Create a Color System section
- [ ] Create a Typography section
We discussed the necessity to push the product out of the door before the end of the year. As a result of this meeting, PM took the following actions.
PM & Stakeholder addressed the FOLA team page limitation problem and the Website team's misplaced Cover page on their Figma file's page menu.
Hack for LA would be closed for the month of December (no general onboarding and no stakeholder or lead meetings...).
The stakeholder approved the plan for release to UX-UI CoP. We walked through the final touch-ups required for the v1.0 release. We also discussed the logistics of the release. After this meeting, PM took the following actions.
feature: agenda
. I have revised your label agenda
to reflect this requirement. I am happy to explain how the guides team will be using this label to help people find the agendas of all projects.
This is the first 1-1 meeting of 2023.
Yas's Items
Bonnie's Items
feature: agenda
. I have revised your label agenda
to reflect this requirement. I am happy to explain how the guides team will be using this label to help people find the agendas of all projects.
Agenda and pre-meeting notes on progress
As the Design Systems team, our goal is to create a White Label version of the HfLA Website team's Design System that can serve as a template for other projects. If we consider our work as a product, let's call the product 'Universal Design Systems Template'. The following requirements have been identified by stakeholders for this template:
It is a well-established fact that the DS of the HfLA website team is the most comprehensive among all of HfLA's projects. Several teams have successfully started their own design systems based on the website team's template, which has proven to be highly effective. As the DS team, our goal is to create a template that is even more advanced and superior to that of the HfLA website team, rather than the other way around. This will help us ensure that our template is the ultimate reference point for other HfLA projects and provides the best-in-class solution for designing and developing user interfaces.
Action Items
"DANIELLE NEDIVI's case study is actually the history of building the website team DS not the history of the DS team's template)" What's the difference between a Design System and a Design System Template? Are there any Design System Template examples out there I can look at to better understand what it is?
(Not pushing back on anything... Just trying to understand if such a template is something that's been done before or if we are creating a custom type of thing for our needs)
@sandraberjan for clarifications on the word "template" let's read the first bullet point from the notes above.
As the Design Systems team, our goal is to create a White Label version of the HfLA Website team's Design System that can serve as a template for other projects. If we consider our work as a product, let's call the product 'Universal Design Systems Template'.
To go back to your question,
What's the difference between a Design System and a Design System Template?
In a practical sense, there is no difference between those two. The DS team would create a design system as if it is meant for a hypothetical product so that other teams at HfLA would use our file as their template in the creation of their very own design system. So it is like we are creating the role model or the mother version of a design system that is somehow general enough and flexible enough that other teams can modify it and make their own child version.
My reflection after reading your comment is maybe we need to drop the word "template" from our product's name. Calling our product "HfLA's Universal Design Systems" for me is clear enough.
Thank you for responding, @allthatyazz ! I'm looking into what "White Label" means and found some examples of a "white label" design system. I think you are probably right about dropping the word "template". I'll research a tiny bit more on what people are calling similar systems like this (will spend less than 20 min on that) and report back on what I find.
@sandraberjan for clarifications on the word "template" let's read the first bullet point from the notes above.
As the Design Systems team, our goal is to create a White Label version of the HfLA Website team's Design System that can serve as a template for other projects. If we consider our work as a product, let's call the product 'Universal Design Systems Template'.
To go back to your question,
What's the difference between a Design System and a Design System Template?
In a practical sense, there is no difference between those two. The DS team would create a design system as if it is meant for a hypothetical product so that other teams at HfLA would use our file as their template in the creation of their very own design system. So it is like we are creating the role model or the mother version of a design system that is somehow general enough and flexible enough that other teams can modify it and make their own child version.
My reflection after reading your comment is maybe we need to drop the word "template" from our product's name. Calling our product "HfLA's Universal Design Systems" for me is clear enough.
@allthatyazz for our next meeting
Khanh’s Update from the meeting with Bonnie
- 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 that she wants a whole design system that can be copied and pasted for any new projects that has components already built out with code that other teams can just tweak
- For the component list, we’ll look at the “Materials UI” to help us decide what to build out
- From “Khanh’s Template Update (3/17/2023)” Bonnie would like us to add:
- “Base published date”
- We need to make the descriptive details component accurate
- Any repetitive details will just live in the same box
Attendees: Stakeholer, PMs @joshfishman @allthatyazz , Design Lead @khanhcao17, Content Lead @michyeh
Overview
This issue tracks the agenda for the stakeholder and PM of design systems meetings.
Template
Weekly Agenda
Week 2021/08/30 Week 2021/09/13 Week 2021/09/20 Week 2021/09/27 Week 2021/10/04 Week 2021/10/11 Week 2021/10/18 Week 2021/11/1
Resources/Instructions
Zoom meeting