Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design System update #1204

Closed
4 tasks
sei1122 opened this issue Apr 23, 2022 · 9 comments
Closed
4 tasks

Design System update #1204

sei1122 opened this issue Apr 23, 2022 · 9 comments
Assignees
Labels
Feature: Design System Standards, documentation and guide of design assets and components Role: Front-end Front End Developer size: 8pt The lift to complete this user story 16-24hrs

Comments

@sei1122
Copy link
Member

sei1122 commented Apr 23, 2022

Overview

We need to update the Design System to design more efficiently. When I’m designing, I refer to the design system color, font, button, and components. Some of the items are not the latest so I need to back and forth website and design system.

Action Items

  • Review the current design system with the team
  • Audit Food Oasis site
  • Update design
  • Approval by team

Resources/Instructions

Currently, there are 2 versions of the design system.

Design System version 1
https://www.figma.com/file/D3oq9QOXl0rFkwrEUJbABs/FOLA-Design-System?node-id=0%3A1

Screen Shot 2022-04-22 at 6 10 58 PM

Design System version 2
https://www.figma.com/file/D3oq9QOXl0rFkwrEUJbABs/FOLA-Design-System?node-id=0%3A1
Screen Shot 2022-04-22 at 6 11 31 PM

Material UI (React library) is used Food Oasis site. This is helpful when we design.
Material UI
https://www.figma.com/community/file/912837788133317724

@sei1122 sei1122 added the Feature: Design System Standards, documentation and guide of design assets and components label Apr 23, 2022
@fancyham
Copy link
Collaborator

fancyham commented May 6, 2022

From our meeting with @entrotech

  • Programmers are using color palettes from figma
  • Anything more involved than that, even when designers create CSS, that CSS usually only works on one device and at once size…
  • but actually programmers have to make it work on all devices and browsers which requires tweaking and things like that.

Often Figma specs or figma font sizes don't translate to the web smoothly, perhaps due to CSS issues.

Is there a way for designers to work in a way that developers can easily use and recreate designs?

John:

  • Not that unhappy with the current process. Good practice for developers, too, since this is very real-world problem.
  • Not sure we can do much better than where we are now
  • Perhaps we can design to three different responsive breakpoints?

Bryan:

  • Is there a design/dev environment that previews CSS well that can be used by programmers?

@fancyham fancyham added the Role: Front-end Front End Developer label May 6, 2022
@ExperimentsInHonesty ExperimentsInHonesty added the Missing: Size The effort estimate for this issue is missing label Jul 29, 2022
@staceyrebekahscott staceyrebekahscott added this to the Project Organization milestone Aug 8, 2022
@staceyrebekahscott staceyrebekahscott added size: 2pt The lift to complete this user story 3-4hrs and removed Missing: Size The effort estimate for this issue is missing labels Aug 8, 2022
@staceyrebekahscott

This comment was marked as resolved.

@sei1122

This comment was marked as resolved.

@staceyrebekahscott

This comment was marked as resolved.

@fancyham
Copy link
Collaborator

fancyham commented Sep 7, 2022

In the Figma, we have two 'style guides' listed which is definitely confusing. From my understanding:

The first one is a style guide of colors, fonts, etc. from 2020

The other "Style guide v2" is from from 2021, and was, I think, intended to be defining new proposed styles, but due to time constraints morphed into an audit of styles currently in-use on the site in May 2021, and showing those vs proposed changes.

To make this more clear, I renamed the two Figma pages to:
2020: Style guide
2021: Audit of styles in-use and V2 proposal

@staceyrebekahscott
Copy link
Member

@sei1122 Will completing issue #991 also resolve this issue? Please explain how they are related and if they can/ should be combined.

@sei1122
Copy link
Member Author

sei1122 commented Sep 8, 2022

I work on #991 to focus on Typography, Color, and Logo consistency with the Dev team.
After completing #991, we can move on to this issue. Either I or another designer can work this.

@staceyrebekahscott staceyrebekahscott modified the milestones: Project Organization, Website Improvements- Impact Sprints 2022 Dec 17, 2022
@staceyrebekahscott staceyrebekahscott added size: 8pt The lift to complete this user story 16-24hrs and removed size: 2pt The lift to complete this user story 3-4hrs labels Dec 17, 2022
@staceyrebekahscott
Copy link
Member

Design System Planning- Google Sheet

@jnaito777 @nkiwan Assigning this issue to you. You can use this as a starting issue or Epic, and link any issues you create to this one. It is in the Prioritized backlog for now, but you can move it to In Progress whenever you are ready to get started on it.

@sei1122
Copy link
Member Author

sei1122 commented May 26, 2023

We break down the design system issue into more small tasks, so I close this issue.

@sei1122 sei1122 closed this as completed May 26, 2023
@sumit-sharma92 sumit-sharma92 modified the milestones: Website Improvements- Impact Sprints 2022, 05. Team Workflow Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Design System Standards, documentation and guide of design assets and components Role: Front-end Front End Developer size: 8pt The lift to complete this user story 16-24hrs
Projects
Archived in project
Development

No branches or pull requests

7 participants