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

CSS refactor #151

Merged
merged 13 commits into from
Aug 5, 2024
Merged

CSS refactor #151

merged 13 commits into from
Aug 5, 2024

Conversation

jannis-baum
Copy link
Owner

Close #120

@jannis-baum jannis-baum requested a review from tuurep August 1, 2024 19:05
@jannis-baum
Copy link
Owner Author

jannis-baum commented Aug 1, 2024

Hey @tuurep so I did this now, I think it made the CSS a lot less cluttered and will hopefully make it easier to maintain & extend in the future :)

I concentrated as hard as I could while doing this, I hope I didn't mess anything up ^^ If you want to check this I would recommend looking at each of the two commits whose messages are refactor(#120): extract ... colors individually, this way it should be easiest to figure out if I made any mistakes.

Also let me know if you're happy with this or if you would refactor anything else :) I did a couple of other small things, see commit messages

EDIT I forgot about the (single) Notebook color we have at the moment, added another commit that does that.

@jannis-baum jannis-baum force-pushed the issue/120-consider-css-refactor branch 2 times, most recently from a86678c to dbfab63 Compare August 1, 2024 19:57
@tuurep
Copy link
Collaborator

tuurep commented Aug 2, 2024

Hey, looks great. Even surprises me how few variables we end up needing.

Tested and looks as expected on light theme. I only have naming-related concerns, I'll put a review.

@tuurep
Copy link
Collaborator

tuurep commented Aug 2, 2024

That's all!

Drawback of this is that we will have to come up with new variables and sort of maintain a naming scheme for these, but looks like it's worth it IMO.

@jannis-baum jannis-baum force-pushed the issue/120-consider-css-refactor branch from 5cd73d4 to 924dd99 Compare August 3, 2024 19:13
Copy link
Collaborator

@tuurep tuurep left a comment

Choose a reason for hiding this comment

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

Ok, I would go with the muted for header border (etc) option,

And I think it would be simpler if we rename to

  • border-muted
  • border-regular

Also partly so that one can reuse these colors in custom styles and it's more descriptive this way

So if you're okay with all this, we can merge 😄

Sorry for all the pain and suffering we have been through here.

@jannis-baum jannis-baum changed the title Consider CSS refactor CSS refactor Aug 5, 2024
@jannis-baum
Copy link
Owner Author

Absolutely no reason to apologize! I appreciate your dedication to getting these things right a lot, this is very important to the project. Thank you!

@tuurep
Copy link
Collaborator

tuurep commented Aug 5, 2024

Absolutely no reason to apologize! I appreciate your dedication to getting these things right a lot, this is very important to the project. Thank you!

Ok! Not always sure if I'm being counter-useful, so good to know 😄

@jannis-baum
Copy link
Owner Author

Ok! Not always sure if I'm being counter-useful, so good to know 😄

Haha no, definitely useful, this is a big contribution to the quality!

I fixed the naming, you forgot to rename bold to muted in the Markdown styles :)

Now we're good right?

@tuurep
Copy link
Collaborator

tuurep commented Aug 5, 2024

Oh yeah, I forgot to rename the variables.. 🤦

Lets be sure that they're correct, careful because I changed the order of them (the old regular is not the new regular)

@jannis-baum
Copy link
Owner Author

jannis-baum commented Aug 5, 2024

Lets be sure that they're correct, careful because I changed the order of them (the old regular is not the new regular)

Ohhh okay haha, then they probably aren't correct. Can you look into it?

I'll be out for today, talk tomorrow! :)

@tuurep
Copy link
Collaborator

tuurep commented Aug 5, 2024

Yes, these just had to be flipped

Now it's good!

@tuurep
Copy link
Collaborator

tuurep commented Aug 5, 2024

I'll be out for today, talk tomorrow! :)

Okay, I see no reason not to merge now so I'll just go ahead and do it :D

Thanks

@tuurep tuurep merged commit b257f51 into main Aug 5, 2024
6 checks passed
@tuurep tuurep deleted the issue/120-consider-css-refactor branch August 5, 2024 19:50
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.

Consider CSS refactor
3 participants