Skip to content

Conversation

@willmullinthomas
Copy link
Contributor

Why

Monday.com Ticket

What benefit does this bring to the end user? Or, what benefit does this bring to developers working in the codebase?

This allows developers to use antd components like text and buttons with the automatic styles that are used throughout the application

This PR

Describe the changes required and any implementation choices you made to give context to reviewers.

All of the variables are located within the craco.config.js file. The colors are at the top of the page and they correspond to different greens and greys that exist in the figma designs. Any of these values can be overridden in less files, see the info-card.less file for an example of overriding antd global styles.

Screenshots

Provide screenshots of any new components, styling changes, or pages.

Here is what one of the template page looks like with the new theme. No code or styling was changed on this page, the new colors come from the global style

theme

Verification Steps

What steps did you take to verify your changes work? These should be clear enough for someone to be able to clone the branch and follow the steps themselves.

Checked the styling on all of the current pages, removed instances of p and h from application to ensure styling works everywhere.

Copy link
Member

@florisdobber florisdobber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me, super helpful! Let Jack take a look to see if the React makes sense.

Copy link
Member

@florisdobber florisdobber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect I was looking into doing this but couldn't figure it out

Copy link
Member

@jackblanc jackblanc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love the progress with this. There are a few things we'll want to change to use https://styled-components.com/ in the future, but we have to merge frontend-scaffold first.

Copy link
Member

@jackblanc jackblanc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks pretty good, there's a few places where we want to use styled-components now. Sorry that the directions changed with that. Reach out on Slack with questions!

@willmullinthomas
Copy link
Contributor Author

willmullinthomas commented Nov 22, 2020

Changed some places to use styled components, no longer override antd styles and removed inline magic color constants. Did not change login and signup input containers because I believe that might be a separate ticket that involves reorganizing those components a bit more heavily.

height: 100%;
width: 100%;
background: white;
background: @white;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔥

Copy link
Member

@jackblanc jackblanc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@willmullinthomas willmullinthomas merged commit 9c16572 into master Nov 22, 2020
@chromium-52 chromium-52 deleted the global-style branch December 14, 2022 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants