Awesome!
Skeleton 2.0 CSS Framework
11–20 of 124 posts
Re: Skeleton 2.0 CSS Framework
#12I've been using Skeleton for a while, so it's nice to see an update. I have a 1200px wide version, so if anybody's interested, I'll post it on my GitHub page.
Re: Skeleton 2.0 CSS Framework
#13Hey 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 :)
Thanks for continuing development on Skeleton! My current blog design is largely based on Skeleton 1.x, but it looks like I'll be updating it this week.
Re: Skeleton 2.0 CSS Framework
#14Hey 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 :)
Thanks for continuing development on Skeleton! My current blog design is largely based on Skeleton 1.x, but it looks like I'll be updating it this week.
Rad man - So, it should ALMOST be a straight drag and drop replacement of the normalize/skeleton.css for the old grid/layout/reset.css, but if you were doing nested columns that's gonna get you. Please let know how it goes – hi@getskeleton.com
Re: Skeleton 2.0 CSS Framework
#15Two 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.
1. There are not hover classes for tables. I'm not in love with table hover classes, BUT, zebra-striping (like every other row) seems like it could by useful. That said, I don't want to create subclasses of any components really (buttons is one exception). It also should be super easy to implement w/ Skeleton – tr:nth-child(even) { background-color: red }
2. List nesting was just because I basically never go deeper than two levels and I wanted to properly indent them. Didn't want code bloat for something I think would be rarely used.
Re: Skeleton 2.0 CSS Framework
#16I've been using Skeleton for a while, so it's nice to see an update. I have a 1200px wide version, so if anybody's interested, I'll post it on my GitHub page.
:) Awesome man. Fwiw, the new version makes it super, super, super easy to scale since the grid is % based now. Can just change the max-width of the .container and voila. Done.
Re: Skeleton 2.0 CSS Framework
#17Glad to see it back. So simple and clean.
Re: Skeleton 2.0 CSS Framework
#18Nice, looking forward to using this. I'm a CSS/JS framework creator myself (Ionic), but often when working on simple websites with a designer I just need a nice grid and some clean defaults. Congrats on 2.0!
Re: Skeleton 2.0 CSS Framework
#19Two 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.
I'm not the author, but there are no hover classes for tables or alternating rows, as seen in the source, which is very readable [0]. Also, each additional level of list-nesting requires additional CSS, so it's actually impossible to support arbitrarily nested lists as seen in most word processors.
[0] https://github.com/dhg/Skeleton/blob/master/css/skeleton.css
Re: Skeleton 2.0 CSS Framework
#20Looks 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 (unfortunately -- makes it very difficult when I'm on my iphone sometimes), and am not sure why people do this. Is it just "common wisdom" that has been copy-and-pasted down through the ages without anyone questioning it, or does it provide some benefit that outweighs the (pretty big) drawback of reduced accessibility?
Thanks!