These should be represented as two separate steps in the UI

Background-images are how gradients get set, we should parse out the opera and possibly other vendor prefixes to sort out the noise.

CSSLINT gives a nice warning about Internet Explorers limit on rules. We should conditionally show something about that.

If css files are dynamically concatenated from a source url - we would need to keep track of rules per file.

We need a name for this project. Nothing has stuff so far.

Right now we flash loading even if everything is almost instant.

We should make this a little smoother and have it only kick in if the page is loading for more than ~600ms.

Don't know what value x should be.

It would be nice if for each property we list out - we show a comparison of total vs uniques. This will help show disparity / alignment with oocss + single purpose class stuffz.

This looks fairly trivial to include.
https://github.com/twitter/recess

Put website data in url structure and make it load betters

Comparisons are fun and can aid in pattern recognition. We should allow to compare various sites or css files against each other and visualize the difference between the two.

Not currently keeping track of this. Should be though.

performance

Test threshold for larger font sizes. Mediums 700px font size doesn't need a long pargram in there. I think like 1 letter would suffice. 120px might not be the magic number though.

We should store the file size of each css file we scrape from a user inputted url.
Should note if each file is
a) minified
b) gzipped

We should calculate the minified and gzipped file sizes and display them in comparison to the actual values.

Currently sorting values by js default i.e : 1,2,22,3

Wouldn't be dynamically generated - but would be nice to have a json file that had it's contents spit out onto the overview page. Would allow for a few interesting nuggets to be stored.

Since it's more than just @jxnblk and myself - we should make a rad about page that's easy to add to so that we can give proper shout outs to any contributors.

It's weird that the XX Selectors heading links off the site. I think the expected behavior would be a detail view of selectors.

What about doing contextual navigation for each section in the overview, then linking to further reading materials in footnotes or smaller text?

It would be cool to get a whole lot of websites that you could preview.

A quick wishlist

ESPN
Facebook
Disney
BBC
New York Times
Nike
Salesforce
Trulia
Kahn Academy
Code Academy
craigslist

0s are most likely overrides so indicating their count could be useful.

It's really hard to tell what's happening in the app right now – just feels broken half the time.

I love the premise of csslint but I think we can make the messaging a bit more useful and display it in a more digestable manner with a web view.

A first pass at things to check for

• Adjoining classes
• Ids in selectors
• Too many !importants
• More than 16 floats
• More than x font sizes
• Elements in selectors
• If there are more than 4095 selectors in a stylesheet
• If import is used

I think you should have a big, massive url input box to allow people to enter a URL. I would love to be able to easily view all my CSS stats for my site!

It would be especially useful since I'm optimising a couple of sites at the moment!

Reshow data from top sites, and add more data for sites of note.

Link hover states are horrible. Fix them. Design them.

User can save/store results from rprtr on an arbitrary basis and visualize changes to metrics over time as their css changes.

This will help people see how changes they have made or potential refactors could impact performance / file size.

Enough said.

Allow option to not show repeating values.

If a user inputs a url to a site i.e

http://www.cartoonnetwork.com/tv_shows/adventuretime/

We run telemetry tests on the url and show the results in a graph.

See: http://topcoat.io/posts/benchmarks/

Ideally a user could input a url, the source could be scraped for paths to css files - those css files could be concatenated into one file - then translated into an AST to parse.

We should break background images up into gradients and images. Gradients should be included with background colors on the colors page - images should be shown by themselves.

Generate sample abstraction code for things like grid systems, font-sizes, skins, and spacing scales. Could then dump the code out into a text area to be copied.

Want to add d3.js and start to output some stats as graphs and pie charts.

Add conditional messaging warning against too many floats. Show how grid system can be a good abstraction.

Visualize margin and padding scale by assigning values to width of block elements.

Things seem haphazardly placed across the overview.

Devise a system of organizing principles that can be used across the app.

Things to consider grouping by:

• High-level stats vs. properties
• Structural properties vs. skin
• Unique vs. total
• Actionable vs. not

Show how many classes you would need on something to override your highest specificity score. This should be helpful in illustrating relationship between filesize and maintainability problems that pop up.

We need to get a custom url and point heroku there. Depends on issue #32