Why is normalize.css included in this repository? about sakura

[oxalorg]

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]

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?