Why have a max width of 960px?
"The grid is a 12-column fluid grid with a max width of 960px"
Skeleton 2.0 CSS Framework
31–40 of 124 posts
Re: Skeleton 2.0 CSS Framework
#32This looks great. I love the simplicity of it and how classnames are handled and just the overall lightweight feeling. Sidetone: I had to go to the github page to see browser support, maybe you can add it to the website. Thanks
Re: Skeleton 2.0 CSS Framework
#33Two questions: Are there hover-classes for tables etc. that can easily be applied? What about striped/alternating rows? And how come I can only nest lists 2 levels deep? Other than that, it looks great.
It's hundreds of requests like this that create bloated UI frameworks!
Re: Skeleton 2.0 CSS Framework
#34Hey ya'll - I'm Dave the creator of Skeleton. Grateful to see it on HN. I wrote about why I created v2.0 in a weird format here: https://medium.com/@dhg/dear-skeleton-452f4bb07d69 I'm hoping the update really helps anyone who's been using Skeleton for a while or anyone trying to get into RWD. Thanks :)
I started using Skeleton nearly 3 years ago and there are still bits of it lingering in my base shared scss files in one form or another.
Thanks for your hard work.
Re: Skeleton 2.0 CSS Framework
#35This looks really simple, I like it. Is it pure CSS or is there JavaScript involved?
It's pure CSS. Download it and take a look, it really is simple.
Re: Skeleton 2.0 CSS Framework
#36Looks really awesome! One piece of feedback I have is that I don't think it's wise to put "maximum-scale=1" in the viewport meta-tag because it makes pages hard to read for people with less-than-perfect vision (because it prevents zooming in on phones). I created a github issue about this too: https://github.com/dhg/Skeleton/issues/173 Is there an actual benefit to having this on web pages? I see it a lot (unfortunat…
I can see your point, but want to add why I recently started to add this meta-tag on most of my responsive sites: 1. images start to look blurry 2. input fields change the scale of the page and seem to confuse some users (at least in some test-cases). On the other hand I try to improve accessability by making sites screen-reader-friendly and using high contrasts. I have also seen a lot of people using "bigger fonts"…
I've struggled with these issues before, and have tried then backed away from the same maximum-size solution.
Fortunately, #2 can be resolved easily by setting input,textarea{font-size:16px}. There are problems with 16px for all inputs (especially if using a custom font with different metrics than the default), but it preserves a significant usability feature. A fair trade, even if it means using system default inside of inputs.
Regarding blurry images, I favor suboptimal delivery of content over failure to deliver every time.
Great work on the framework, keep it up!
Re: Skeleton 2.0 CSS Framework
#37Hey ya'll - I'm Dave the creator of Skeleton. Grateful to see it on HN. I wrote about why I created v2.0 in a weird format here: https://medium.com/@dhg/dear-skeleton-452f4bb07d69 I'm hoping the update really helps anyone who's been using Skeleton for a while or anyone trying to get into RWD. Thanks :)
Just wanted to say thanks for making this. Skeleton introduced me to the basics of responsive design and my company now uses it in several applications.
So glad to hear it man. That's why I built it :)
Re: Skeleton 2.0 CSS Framework
#38Looks really awesome! One piece of feedback I have is that I don't think it's wise to put "maximum-scale=1" in the viewport meta-tag because it makes pages hard to read for people with less-than-perfect vision (because it prevents zooming in on phones). I created a github issue about this too: https://github.com/dhg/Skeleton/issues/173 Is there an actual benefit to having this on web pages? I see it a lot (unfortunat…
It removes the 300ms delay while the browser waits for a double-tap (to make sure you really meant to click on that link and not zoom in), which is supposed to be a huge UX improvement.
Note that Android no longer applies the 300ms delay regardless of viewport scalability.
http://updates.html5rocks.com/2013/12/300ms-tap-delay-gone-a...
There are a number of plugins to remove the 300ms delay from other touch browsers. Here's one: https://github.com/ftlabs/fastclick
Re: Skeleton 2.0 CSS Framework
#39Why have a max width of 960px? "The grid is a 12-column fluid grid with a max width of 960px"
> "The max width can be changed with one line of CSS and all columns will resize accordingly."
Re: Skeleton 2.0 CSS Framework
#40Hey ya'll - I'm Dave the creator of Skeleton. Grateful to see it on HN. I wrote about why I created v2.0 in a weird format here: https://medium.com/@dhg/dear-skeleton-452f4bb07d69 I'm hoping the update really helps anyone who's been using Skeleton for a while or anyone trying to get into RWD. Thanks :)
Very nice! If anyone else was unfamiliar with "rem"s (root em), this short article helps: http://snook.ca/archives/html_and_css/font-size-with-rem
It also expands on the comment in skeleton.css on how font-size: 62.5% skales 1 em to be 10 px (it would appear 16 px is the default).