Live data from Hacker News

Skeleton 2.0 CSS Framework

getskeleton.com

21–30 of 124 posts

Re: Skeleton 2.0 CSS Framework

#21

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

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.

Re: Skeleton 2.0 CSS Framework

#22

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 so much for the hard work. I've been using Skeleton for a personal project even though it hadn't been updated in over 2 years. As a (mostly) backend developer, Skeleton has proven to be the best possible starting point for me to learn on; there's nothing tricky about it.

This is a very nice early Christmas present!

Re: Skeleton 2.0 CSS Framework

#23

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

Hi Dave, great work on Skeleton. Was the original project a side-project or was it in use for projects at Twitter and / or Medium? Wondering about how it seems to be a sort of antithesis to Bootstrap (as in no preprocessor / small footprint / sane defaults).

Re: Skeleton 2.0 CSS Framework

#24

Looks 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" options in their browsers or on their phones, which solves this problem from my point of view.

Re: Skeleton 2.0 CSS Framework

#26

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, I'm still in love with Skeleton, and 2.0 looks very nice. And it's great timing as I'm including it in the update to our web development recipes book.

Keep up the awesome work.

Re: Skeleton 2.0 CSS Framework

#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 2.0 release, and thanks for all of the hard work!

Re: Skeleton 2.0 CSS Framework

#29
post #24

Looks 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 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.

Re: Skeleton 2.0 CSS Framework

#30

Looks 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.
Post reply on HN