normalize.css
open-props
normalize.css | open-props | |
---|---|---|
53 | 50 | |
51,952 | 4,438 | |
- | - | |
0.0 | 8.4 | |
4 months ago | 10 days ago | |
CSS | HTML | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
normalize.css
-
What is cross-browser compatibility, and why should you care?
You can also consider using stylesheets like Normalize.css, Eric Mayer's CSS reset rules to establish a baseline layout across browsers.
-
An Introduction to the Vision Board Project
==> Click here to get the code from necolas.github.io!
-
How to Debug CSS
4. Understanding the box model A thorough understanding of the box model is essential for effective CSS debugging. The box model, encompassing margin, border, and padding, plays a fundamental role in CSS styling. By familiarizing yourself with the box model, you can better identify and resolve many styling issues. Browser issues. Different browsers render our styling differently. This is because browsers have their own default stylesheets called user-agent styles. To override these inconsistencies you should consider resetting your CSS to provide cross-browser consistency. A good resource I use when writing vanilla CSS is Normalize CSS. For example, it resets the margin, padding to zero, and the box-sizing property to border-box.
-
Responsiveness issue
In addition to the answers below about flex, grid and media queries, you can also additionally take a look to the "clearfix hack" (https://www.w3schools.com/howto/howto_css_clearfix.asp) which is a common issue when you position elements and also use something like Normalize.css (see https://github.com/necolas/normalize.css) to avoid some weird bugs in your front end.
-
Why is the font rendered differently on Firefox and Chrome? How can I make it the same?
is this github what you used? Seems like it hasn't been updated in a while
- Basic_Design_System: An extremely basic design system that I’ve created. Meant to be used as a boilerplate for creating more advanced design systems, while also looking good if used out-of-the-box with zero altering.
-
How do you implement CSS for different browsers in the same stylesheet?
You can just download the normalize.css file from their Github, and then include it on your page(s) as the first stylesheet link. It will basically override the "default" styles of the various browsers so that you have a common starting point. That should handle various things like margins and paddings.
-
Should I Be Using -webkit-appearance?
I want to use a CSS normalizer for the first time on a new project I'm doing, and in the code there is a couple -webkit-appearance properties that VSCode is telling me are not standard. However, when I search up if this is really a problem or not, I don't find anything saying yes or no. So... Is it actually a problem to use this property?
-
How to build a docs site with Next.js and Contentlayer
reset.css — download here
-
What working with Tailwind CSS every day for 2 years looks like
This might be helpful.
https://necolas.github.io/normalize.css/
Design decisions, though, are ultimately up to your taste and judgement.
open-props
-
Eurovision Gradients
Now, for the red/blue-version, I took one of the nice linear() timing-functions from Adam Argyle's Open Props:
-
Learn CSS Layout the Pedantic Way
There's still some boilerplate, but I'm a big fan of Open Props[0] because it takes a hybrid approach. CSS isn't necessarily reinventing the wheel, but allowing for easier / more powerful approaches to difficult layouts or things that would otherwise require JS. Bootstrap is fine but troubleshooting advanced layout issues involves a lot of inspecting elements to see what styles are actually being applied (at least in my experience, YMMV) so I'd personally always bet on CSS.
[0] https://open-props.style/
-
Why Tailwind Isn't for Me
I don't quite get the hate for having CSS in another file. Do you also put all your react stuff in one single file ? That same logic and argument can be applied against all modularization.
And really 20-50 tailwind classes in a single element is VERY hard to read and keep in mind. No - it does not make things clear or understandable. One tends to need to re-read and scan over from the beginning and eyes glaze over. Esp if some elements only vary with a few classes missing. I guess it works for people with very high attention to detail and high amount of working memory. I only find it personally frustrating.
Maybe tailwind css works for some bright people. I did try it for a couple of projects and only felt pain.
However, the "atomic css" philosophy behind tailwind is great. I find framewroks like https://open-props.style/ far better to use.
- Htmx and Web Components: A Perfect Match
-
Styling React 2023 edition
Open Props adds to the set by providing extra custom properties for things like easing functions or animations.
-
The Future of CSS: Easy Light-Dark Mode Color Switching with Light-Dark()
> If you wanted to actually solve theming, what you should work for is not a constrained helper function like light-dark(), but instead a shared token schema. Today nearly every company has their own token schema and different ways of naming things in the semantic token layer. If we had a shard language here, not only would it be trivial to add light/dark theming (just redefine a few variables that are already provided for you), code could be shared between sites and inherit the theming/branding.
Isn't that the idea behind https://open-props.style/ (and https://theme-ui.com/ in JS land)?
I think it's a great idea, but hampered by the lack of adoption incentives for the very people that need to adopt it for it to become successful (design system/component library authors). It introduces constraints, but the promised interoperability is not really beneficial to the people who need to work within those constraints.
-
Tailwind CSS and the death of web craftsmanship
I do think that the real value of Tailwind comes from the utility classes, rather than css-in-html paradigm. You could achieve the same, for example, with Pollen.css [0] or Open Props [1].
[0] https://github.com/heybokeh/pollen
[1] https://github.com/argyleink/open-props
-
What is the best styling strategy for a Svelte project?
If you choose to style with plain CSS you can add design tokens as CSS variables with Open Props: https://open-props.style.
-
Released tw-variables: 400 useful Tailwind utilities as ready-to-import CSS variables
Some time ago I discovered Open Props which provides a lot of design tokens as CSS variables and started using it in some of my projects.
-
[Showcase] Searching for Friendly-User for Scrum-Tool Miyagi
CSS: Open Props (https://open-props.style/)
What are some alternatives?
modern-normalize - 🐒 Normalize browsers' default style
carbon-components-svelte - Svelte implementation of the Carbon Design System
postcss-preset-env - Convert modern CSS into something browsers understand
svelte-headlessui - Unofficial Svelte port of the Headless UI component library
Materialize - Materialize, a CSS Framework based on Material Design
pollen - The CSS variables build system
bounce.js - Create beautiful CSS3 powered animations in no time.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
cssnano - A modular minifier, built on top of the PostCSS ecosystem.
humane-js - A simple, modern, browser notification system
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript