I'm just bouncing this around in my head right now, but what does it mean to be small? I'd like the code for neat to remain light weight, maybe even to an extreme. But, it's going to need a few, maybe a lot, of css styles to make it usable for a wider range of projects. Where do we stop?

Do only the css and html files matter?

The typical install process is to use curl to grab neat.css and neat.html. Are these the only files I should care about when thinking about the size of Neat? If so, here are some files I might add.

• Add one or more .html files with examples for things like forms
• Add Screenshots showing the main page and/or additional examples
• Add a LICENSE.md file with the full MIT license (there are several)
• Create scripts to check bytes between versions

There is a gh-pages branch that has the main screenshot in it currently, so it can be published to the web but doesn't neat to live in the master branch. This is a bit of a pain to maintain and is more of a trick to simplify the repo for anyone who's just using this project as a launch pad for a simple site/project. Should it stay this way or should the project host strait out of master?

On the flip side, should I remove the custom.css file which is basically just an empty example file. You only get it if you clone the code or download the release, rather than just grabbing the .html and .css files via curl.

What is small?

When I released Neat it was about 1K of css/html. It's grown to almost 2K in a fairly short period of time and I recognize that most software simply grows until it's bloated. I want it to be tiny and accessable but what does that mean today?

I realize this could be a really loaded question for a discussion topic, especially for the first discussion topic.