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

Why is normalize.css included in this repository? #9

Open
zhouzi opened this issue May 4, 2017 · 2 comments
Open

Why is normalize.css included in this repository? #9

zhouzi opened this issue May 4, 2017 · 2 comments

Comments

@zhouzi
Copy link
Contributor

zhouzi commented May 4, 2017

Hey there!

I think this repository shouldn't serve as a normalize.css host. Also, the risk is that it quickly become out of sync with official releases.

That been said, I think that all sakura's css files should include normalize.css by default. Having to include normalize.css as a second stylesheet defeats the idea behind sakura:

Just drop in sakura.css to any webpage and go from ugly looking 1900's website to a pretty modern website in literally 0 seconds.

normalize.css addresses browsers inconsistencies, if you're not using it with sakura then you're sure to face bugs here and there.

Happy to submit a PR if that sounds good.

P.S.: including normalize.css in css files would be easy as adding @import 'node_modules/normalize.css'; to the theming scss files.

@oxalorg
Copy link
Owner

oxalorg commented May 5, 2017

I'm not so sure about that.

I did previously think of bundling normalize inside sakura, but that makes it really complicated for those of us who aren't familiar with css/web technologies.

One of the reasons I think^[1] that sakura resonated so well among people was that it's small, easy to understand, and simply works. There is no wriggling around, and the source is relatively easy to ready and does not overwhelm newbies/people who aren't vested into webdev.

This was my line of reasoning to not include a minifed css as well, it will quickly start overwhelming people. They'd be less inclined to read, change, and customize sakura to fit their own needs. It will become like all the other frameworks they're so scared to touch.

Sure adding in normalize will save one step, but it also makes it implicit, and confuse the users. Which is bad. I'd rather they explicitly include a link to normalize. Perhaps we can add that in the README like so:

<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/normalize/7.0.0/normalize.css" type="text/css">
<link rel="stylesheet" href="https://unpkg.com/sakura.css/css/sakura.css" type="text/css">

.. making it very clear that you should include normalize.css for the recommended results.

What do you think?

[1]: I'm gathering this insight from all the people who've commented on this thread: https://www.reddit.com/r/webdev/comments/68zpdp/sakura_a_minimal_classless_css_theme_just_drop_it/, a couple of PMs, and feedback from friends and their co-workers.

@zhouzi
Copy link
Contributor Author

zhouzi commented May 7, 2017

If the generated files are intended to be read and modified then it makes total sense 👍

Maybe the normalize.css file should just be removed from the repository then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants