Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Skeleton 2.0 CSS Framework

getskeleton.com

Post reply on HN
Print view View original

71–80 of 124 posts

Re: Skeleton 2.0 CSS Framework

#71

Post by marshallford »

dhgamache wrote: post #6

Hey 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 the 2.0 update Dave! I having been using Skeleton as a starting point for side-projects for a couple of years now. I really like how light it is compared to Bootstrap.

Happy Holidays!

Re: Skeleton 2.0 CSS Framework

#72

Post by jordanlev »

Chris_Newton wrote: post #70
jordanlev wrote: post #67

Earlier quoted context omitted.

Ah, thanks for the explanation. I do vaguely recall hearing about this issue a while back, but never grokked the details. I find it interesting that people would prefer to disable zooming just to avoid wonkiness on orientation changes -- seems like a way less important issue. But hey, design is all about making choices, so I can understand how other people might weight those issues differently than I do. A followup q…

... does this imply that the orientation change issue isn't a problem if you use media queries properly? I wouldn’t quite say that. It’s more that whatever effort you put into using media queries to adapt your site somewhat intelligently for visitors with different devices is wasted if those devices ignore your media queries and just naïvely scale everything instead. For example, one site I work on has a single-colum…

Thank you so much for the detailed explanation. Makes sense, and gives me a much better understanding of the trade-offs. Cheers!

Re: Skeleton 2.0 CSS Framework

#73

Post by AlwaysBCoding »

gamesurgeon wrote: post #28

Skeleton is the only "sane" CSS boilerplate framework I've encountered. It's incredibly minimal -- the entire framework is so small and elegant that I can crank out websites without delving into the subtleties of the documentation. I find it really intuitive to use, and while I don't do a lot of web dev, when I do it's almost always with Skeleton. Anyways, I'm so glad you're working on Skeleton again! Congrats on the…

Semantic UI is really good as well.

http://semantic-ui.com/

Re: Skeleton 2.0 CSS Framework

#74

Post by ummjackson »

dhgamache wrote: post #6

Hey 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 :)

Dave, just wanted to say I love Skeleton, have used it for years and you rock. Thanks! :)

Re: Skeleton 2.0 CSS Framework

#75

Post by necrodawg »

AlwaysBCoding wrote: post #73
gamesurgeon wrote: post #28

Skeleton is the only "sane" CSS boilerplate framework I've encountered. It's incredibly minimal -- the entire framework is so small and elegant that I can crank out websites without delving into the subtleties of the documentation. I find it really intuitive to use, and while I don't do a lot of web dev, when I do it's almost always with Skeleton. Anyways, I'm so glad you're working on Skeleton again! Congrats on the…

Semantic UI is really good as well. http://semantic-ui.com/

Semantic UI is ~0.5MB minified while Skeleton is ~20KB.

Re: Skeleton 2.0 CSS Framework

#76

Post by bbcbasic »

dhgamache wrote: post #6

Hey 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 :)

Thank you Dave.

I am excited to use this. I need a simple CSS (dare I say 'framework').

I will use this for a personal project app and post back the link when I am done.

Re: Skeleton 2.0 CSS Framework

#77

Post by roywiggins »

dhgamache wrote: post #48
dkersten wrote: post #29

Earlier quoted context omitted.

I read a lot on my phone and I don't have great eyesight. If I cannot zoom the website I'm looking at, I often cannot read it.

I honestly hadn't considered this case. Let me dig into it and see if I can find a solution that works best all around.

An option to increase text size in the interface is probably going to be even better than allowing zoom, since it will reflow the text and not require the user to scan left and right around the zoomed-in text.

Re: Skeleton 2.0 CSS Framework

#79

Post by maradori »

e12e wrote: post #40
dhgamache wrote: post #6

Hey 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).

Thank you for sharing such an informative article!

Re: Skeleton 2.0 CSS Framework

#80

Post by bobbykjack »

roywiggins wrote: post #77
dhgamache wrote: post #48

Earlier quoted context omitted.

I honestly hadn't considered this case. Let me dig into it and see if I can find a solution that works best all around.

An option to increase text size in the interface is probably going to be even better than allowing zoom, since it will reflow the text and not require the user to scan left and right around the zoomed-in text.

Of course, this is how our browsers used to work before the makers decided to remove or hide that feature. I've never seen it on a mobile device. Does anyone understand the reasons behind that move? Even if you think page zoom is 'better' than text scale, surely it doesn't make sense to disable the latter altogether?
Post reply on HN