Hey everyone - I'm the creator of Skeleton. Just wanted to drop a note and say I wrote a little something about creating v2.0: https://medium.com/@dhg/dear-skeleton-452f4bb07d69
Basically I haven't touched it in a couple years because I got busy and figured it wasn't getting much use since it was competing with large, robust frameworks. Found out a couple weeks ago that wasn't true and it's been downloaded around half a million times.
It compelled me to get it together and keep working on it. Open to answer any questions about it :)
Very cool, I built my first responsive site with Skeleton.
Me too. I also use a Skeleton-based WP starter theme for all my projects even now.
That sounds like something I could use. Is that a public WP theme?
Well, it's freaking awesome. I considered Skeleton a couple years ago, but it seemed like it wasn't 100% sure where it was going. This update seems to completely alleviate that, and I'm super excited. Looking forward to using it on projects.
Thanks man! I'm sorry it wasn't at the point you were looking for, but hopefully now it's getting there :) If you find anything missing that you feel makes sense, hit me up and let me know. firstname.lastname@example.org
Great work Dave. I've used skeleton many times over. Thanks for putting it together. Love that it's lightweight and dead simple. I prefer it over any of the larger scale frameworks.
ps. Also stoked to see that you built the type around rems. Killer.
Much appreciated man. I actually built it with REMs and was surprised that I didn't really use the type scaling at smaller sizes...but I can totally see situations when it would be useful and there was no downside (except for maybe a slightly higher learning curve). Seemed worth it.
Hello Dave, I am a big fan of Skeleton and had a quick question for you. On your example landing page you have this in the code:
<code> <nav class="navbar container"> <h4 class="logo"></h4> <ul class="navbar-list"> <li class="navbar-list-item"> <a class="navbar-list-link">About</a> </li> <li class="navbar-list-item"> <a class="navbar-list-link">Jobs</a> </li> <li class="navbar-list-item"> <a class="navbar-list-link">Contact</a> </li> </ul> </nav> </code>But it doesn't display the logo or nav on the frontend. Is this on purpose? Thanks
Oh man - I totally spaced and didn't remove that, haha. I just removed it.
I was originally going to add a nav too, but felt like it didn't really contribute to Skeleton education, more like general CSS education.
Thanks for pointing that out.
No worries and thank you for a great lightweight framework.
Hey Dave! I wanted to say thanks because I learned a ton about responsive CSS and making frameworks by studying Skeleton's code years ago.
Just wanted to chime in and say that I, too, built my first responsive site with Skeleton. Pretty exciting to see this update! :)
Awesome to hear. Helping people get into responsive is a big part of why I originally built Skeleton :)
Really debating if I should use this or Foundation. Thoughts? (Amateur web developer working on a single page site.)
It depends. Foundation is a big package that contains many different things, but most importantly components with a theme. These components are forced on you, such as a certain color scheme for buttons, input areas, etc.
Skeleton is lightweight. It's a little more broken down to only what you need. I like using skeleton because I like building my own components/elements for when I need them.
Basically, Foundation comes with everything you need saving you time, where as Skeleton strips down what you need to only the essentials, giving you more work to do (which I personally like).
Ahh ok. I always thought Skeleton was supposed to be quicker to implement.
I use stuff like Foundation and Bootstrap for rapid prototype development. I like to start with Skeleton once I'm building for production.
Skeleton is awesome! I just put together a sass fork if anyone was planning on doing the same: https://github.com/zbtaylor/sass-skeleton
We must have been thinking the same thing: https://github.com/nafoster/Skeleton
I like your folder structure better than mine, but I would suggest compressing the skeleton.css file. I liked Skeleton because it was light-weight, and I think we should keep it that way.
Great job though!
In case anyone is wondering, V2.0 is the first real update to skeleton in a couple years.
Awesome! Like many here, skeleton was the first framework I used, and loved its simplicity. I know this might go against the minimalism of the framework, but I'd love to have a LESS or SaSS based version.
I was thinking the same, but just looked at the source: https://github.com/dhg/Skeleton/blob/master/css/skeleton.css It's 392 lines. Converting to SASS doesn't seem very necessary. You can include skeleton as a dependency and have the rest of your project be in SASS or LESS.
Sure. But I'd love to be able to customize colors, fonts, sizes without having to override or modify the original. Not a huge issue, but I'd find it much more convenient to work like that.
Ahh wonderful! Skeleton was my first love and no other css file could ever replace it. Super stoked for this update! Good job, Dave!
I have been using Skeleton for the past few years and would like to personally thank you Matt. Let me buy you a coffee!
<3 thanks man. And anytime - hit me up @dhg on twitter.
my first responsive website was (probably) also with skeleton. dead simple and light. to this day is still my favourite option as it's really simple to work with for smaller projects. thanks!
It's back!! Thanks god
It's really great to see CSS frameworks, like Skeleton, which aren't overbearing on the design details or provide a collection of components. I've gotten a lot of use out of Bootstrap and Zurb's Foundation, but I've also often spent time overriding styles and reading documentation.
Taking a component approach to front-end development is very useful, but also necessarily dictates both markup and style. I think that's at odds with the supporting role a CSS framework should provide. It's more important to codify the common structural and layout patterns, such as typographic grids and sensible breakpoints.
I think Skeleton aligns pretty well with Harry Roberts's thinking behind what CSS frameworks should provide.
My first responsive site is also created with Skeleton. My current portfolio is on Skeleton 1.0!
I built my first responsive website using Skeleton, happy to see a new update :)
Also, I really loved the clean style of the website!
Glad to see Skeleton is still alive and kicking. (See what I did there?)
Looking good. Glad it embraces things like this:
<!-- Note: columns *cannot* be nested since that's tough with % based grid -->
One note of critique, at a face level: It seems like loading in Raleway from Google as the default font is an expensive default. Not that that is difficult to change, but just a thought.
Nice! I've built a few websites with Skeleton 1.0 and it's always been a pleasure to work with.
:) Glad to hear.
My first love has returned! Thanks for the great work Dave.
Excellent work on making the class names resemble plain english. Makes it easier to read the code instead of guessing what is going on.
Cool! I was looking at Skeleton the other day. A really lightweight framework without the bloat that we never use is really appreciated.
Any plans for adding classes for "prefix" and "suffix" for positioning columns. I appreciate you're wanting to keep it lightweight which is it's purpose of course :)