-
Notifications
You must be signed in to change notification settings - Fork 28
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
Lay your own foundation instead of Reset or Normalize #7
Comments
I've read that article, and in general I agree, I liked it. We can possibly change some details if we need to. |
Yea, I like this. I've used |
This is a thing that I was thinking about. We have to take care of this aspect because, as Richard said, each component should work fine as a standalone element. If we look at our previous framework (seed UI), I think many elements were affected by the CSS rules provided by normalize.css. But what if the user downloads the CSS of a single element that does not contain any reset? |
There is the |
We can just remove the things we don't need from |
This is the biggest problem. We need something more stable
I agree with you. What about the need of giving to the users the ability to download single components? How could we do for allowing this? Do you think it's better if the user must download at least two separate CSS files or a single one? In the first case, we could have a base CSS file which contains reset, helpers and so on, and a specific CSS file which contains all the rules for a component instead. In the second case, we need a way for incorporate all the necessary in a single file which is compiled just in time, when the user chooses what component wants to download. |
@cbracco |
Hmm... yea, I'm kind of going back and forth with 'your own foundation' and @GabrieleRomeo With regards to making this as modular as possible.... Right, I think that would be nice to have some kind of build process that fetches all the rests that a particular component is dependent on and incorporates them into the CSS for the component... I just don't know what would do that or setting that up. Perhaps it isn't that difficult to do for some components manually. Again, for now, maybe having the component html, css and js files plus the optional normalize/reset file for users to download is ok. The two css file case, normalize and component file(s) may be modular enough for now to meet the deadline. Richard said it doesn't have to be perfect.
My vote is for |
I think that it is not uncommon to declare |
@Gruximillian No actually what There is a PostCSS plugin that acts as a polyfill for the The idea is that this moves the reset into the local scope of a component, instead of having a bunch of components depend on one global reset. Not sure we want to do this but its a neat idea. |
@cbracco |
Some days ago, on this thread on QA, Blake Wilson posted an interesting link by a senior-developer that talks about not using reset.css or normalize.css in our projects.
Here the link
http://jaydenseric.com/blog/forget-normalize-or-resets-lay-your-own-css-foundation
What do you think if we try to adopt it?
The text was updated successfully, but these errors were encountered: