WordPress has gotten a facelift. 3.8 brings a fresh new look to the entire admin dashboard. Gone are overbearing gradients and dozens of shades of grey — bring on a bigger, bolder, more colorful design!
WordPress 3.8 is here! I used the beta versions for quite a while and I’m really happy with 3.8 and I really enjoy the new admin panel design. Go ahead update your WordPress and see for yourself.
A slightly less common issue, and one I’ve come up against myself, is the desire to only keep certain parts of a codebase private.
You want to know how to do that with Git(Hub)? Go on over to this nice 24 ways article.
Last summer the Mozilla Developer Network MDN underwent a massive platform change, moving from a hosted third-party solution to our own custom Django application code-named Kuma. That move laid the ground work for our latest major MDN upgrade: a complete front-end redesign, included many new features as well as usability and accessibility enhancements.
The awesome MDN has a completely new design and it looks really good. Even with webplatform.org around I still go to the MDN if I need to look something up.
I got everything set up a couple of days ago and fired a tweet out about how, for once, my desk looked presentable. I got a few replies asking me about a few things, so I thought I’d also put together a short post about my setup and the tools I use. I enjoy reading about other peoples’ setups, so I thought I might as well share my own.
Harry posted a nice overview about his new setup for working as a freelancer from home. Looks quite nice and I like how simple his software setup is. I’m not quite there yet, but I kick out more and more apps.
For those of you who haven’t heard of Sequel Pro, it’s a simple to use, good looking app to manage your MySQL databases. I just used it for the first time and it’s really easy to use and it’s free. Go download it. And maybe donate a few bucks?
For some reason, I seem to have a fascination with CSS loaders these days. After recreating the Google loader with clean CSS recently, I set off to recreate the classic spinner with CSS. Yes, I know this has been done zillions of times, but I wanted a clean, maintainable, reusable solution, not just a proof of concept. Something with not tons of CSS and/or HTML elements.
Very nice, simple and clean solution building a CSS only spinner.
ResponsiveComments was designed to bring simple conditional loading to the client side. Although not the complete answer to conditional loading in responsive web design, ResponsiveComments provides a solution to simple conditional loading, directly within your markup, using HTML comments, media queries and feature detection.
This year, it should be no surprise that people use mobile devices to buy things online. But when you compare this years early holiday shopping numbers with last year, the growth actually is pretty surprising.
Just in case anybody needs to be convinced that responsive Design is more than just a side-feature of a website.
This is what the Mozilla community is all about — championing a web where people know more and do more, a web that they can make their own and use to make their lives better.
As I’ve said a few times in the past already, I love what Mozilla and Firefox stand for and I appreciate what they do, but more often than not their products are not as good as the ones from others and that makes it hard for me to use or to support them. And that in turn makes me kinda sad.
The fact that Blink is apparently calling src-N dead in the water because one implementor opposes (WebKit) and yet haven’t said the same about srcset which is also opposed by an implementor (Mozilla) speaks volumes to the rationale here: it’s not because there isn’t a consensus, it’s because of who is wielding the heavier stick. The fact that the RICG have thrown their support behind src-N appears to not really figure into the equation.
So here we are 21 months after the RICG was started. We finally have a solution that both the RICG and a majority of implementors are interested in, and it looks like it’s at risk of not happening because of one single implementor dissenting opinion. The fact that the currently discussed solution on the WHATWG list is a frankenstein combination of HTML and inline CSS doesn’t do much to elevate my spirits
True words by Tim Kadlec on the responsive images solution or should I say debacle? Go read it, now.
You probably build websites and think your shit is special. You think your 13 megabyte paralax-ative home page is going to get you some fucking Awwward banner you can glue to the top corner of your site. You think your 40-pound jQuery file and 83 polyfills give IE7 a boner because it finally has box-shadow. Wrong, motherfucker. Let me describe your perfect-ass website
I’m probably the last one linking to this, but it’s so good. :D