I've found MDN to be the best resource: https://developer.mozilla.org/en/CSS
This app is using the data from MDN. It's similar to http://w3viewer.com/ which makes it easier to browse W3C specs.
InstaCSS: the CSS docs you always wish you had
51–60 of 93 posts
Re: InstaCSS: the CSS docs you always wish you had
#52Nice, but a few UX nitpicks: * Default to sort by relevence: Put the more relevant matching properties at the top. For example, I type "backg" instead the highest result being the obscure "-webkit-background-composite" ... actually most relevant result "background" which should be the first result instead of the third. * Default results list to condensed format: Instead of showing the full verbose docs for every matc…
Yes, needs better separator elements to distinguish between the hits. A condensed default view would help with this though.
Re: InstaCSS: the CSS docs you always wish you had
#53Hey there, creator of instacss here. Thanks for all the feedback! I posted this as a Show HN last week, but it's nice to see that someone has re-discovered it: http://news.ycombinator.com/item?id=3222253.
Since then I've added a few features, one of which being the ability to have permalinks so that you could use it as a google chrome search. This is why I push to the url bar as you type. I'm really open to feedback on how to do this without screwing with people's back buttons, since I agree that's pretty bad.
Re: InstaCSS: the CSS docs you always wish you had
#54Oh look, it's another site that loads nothing with JavaScript off. What is wrong with you? Progressively enhance, or gracefully degrade, or display something other than a completely blank page to non-JavaScript visitors. I harbor many doubts re: your competence in the realm of usability.
The percentage of users with Javascript disabled[1] is smaller than the percentage of users using Opera[2]. So there is nothing wrong with choosing to not support 2 out of every 100 users; that's simply a time/cost assessment. What's wrong with you? [1] http://developer.yahoo.com/blogs/ydn/posts/2010/10/how-many-... [2] http://www.w3schools.com/browsers/browsers_stats.asp
There is something wrong - in many countries you are mandated by law to make your site accessible :)
Of course this doesn't apply here, but I wanted to be dramatic. Should be piece of cake to just show the full content if javascript is off, since it is already loading all of it.
Re: InstaCSS: the CSS docs you always wish you had
#55One minor bug: I notice the anchor (and results!) changing as I type and backspace, but if I backspace all the way to an empty it is stuck on the single-letter anchor. Would be nice if it cleared out entirely and took me back to the empty front page.
Re: InstaCSS: the CSS docs you always wish you had
#56Earlier quoted context omitted.
Which is all well and good unless users don't have a choice. http://en.wikipedia.org/wiki/Comparison_of_screen_readers
Except, that's a poor argument: http://webaim.org/projects/screenreadersurvey3/#javascript
Except that most sites don't care about providing decent clues (correct mark-up, ARIA attributes, etc) for javascript interactions, so that's also a poor argument.
Re: InstaCSS: the CSS docs you always wish you had
#57Hey there, creator of instacss here. Thanks for all the feedback! I posted this as a Show HN last week, but it's nice to see that someone has re-discovered it: http://news.ycombinator.com/item?id=3222253 . Since then I've added a few features, one of which being the ability to have permalinks so that you could use it as a google chrome search. This is why I push to the url bar as you type. I'm really open to feedback…
An idea would be to separate the history push from the loading of the resources, and only push history after an action that denotes the user has found the result they were looking for (blur of input, pressing enter, etc) to avoid a search history filled with every keystroke of a query.
A different take would be to never automatically push the results to the url bar, but still parse the address bar for queries, and provide a permalink for each result with the hash in it.
Re: InstaCSS: the CSS docs you always wish you had
#58I think your DNS for www.instacss.com is broken:
;; ANSWER SECTION: www.instacss.com. 300 IN CNAME http://morning-warrior-3377.herokuapp.com/.
CNAME accepts only hostnames or (depends on your RFC-acceptance-level) a FQDN. No URI/URL
Re: InstaCSS: the CSS docs you always wish you had
#59I wouldn't say these are the css docks I wish I always had. see I want better presentation. I don't really want to scroll through the actual CSS docs from W3C, I want to get some quick view of what my search query returned (property, {values}, notes). After that I could click on the entry for that property and read it's docs. It's just information overload. Nice work though, but that's my suggestions.
Re: InstaCSS: the CSS docs you always wish you had
#60Hey there, creator of instacss here. Thanks for all the feedback! I posted this as a Show HN last week, but it's nice to see that someone has re-discovered it: http://news.ycombinator.com/item?id=3222253 . Since then I've added a few features, one of which being the ability to have permalinks so that you could use it as a google chrome search. This is why I push to the url bar as you type. I'm really open to feedback…
Would be nice if you share some of the used backend technology