Drupal 8 release candidate

Finally, Drupal 8 left beta and provided a release candidate last week. As soon as things slow down at work, it’ll be time to start learning the ins and outs of this. (I won’t be moving away from Drupal 7 for some time, because of all the custom modules I’ve come to depend on. But that doesn’t mean my next project can’t start with the new version.)

A complete guide to flexbox

I was overjoyed when I saw that the latest versions of Safari for both OS X and iOS did away with the need to use -webkit- prefixes in CSS animations and flexbox. I’m still including them for the time being, and probably will for at least a year, to ensure compatability. But it’s as good a reason to point out that if you’re not on the flexbox train, you’re missing out on some powerful stuff.

CSS tricks has a great page called “A Complete Guide to Flexbox“, and I’ve been referring back to it constantly as I use it more and more in my current project. If you haven’t memorized all the nuances of flexbox yet, keep this one handy.

jQuery 3.0 alpha released

It’s probably gonna be a big deal.

Previous to this, jQuery 1.x was the IE8-compatible version and 2.x was the forward-looking version which only worked in IE9 and modern browsers. This was confusing to a lot of newcomers who just assumed that 2.x was the latest and greatest version, so now we have”jQuery Compat” 3.x and jQuery 3.x instead.

Please note that there are some breaking changes, plus this is an alpha release, so don’t do anything reckless like using it in production untested.

Nine reasons NOT to use a CMS

This article is relevant to my interests. I’ve spent the last couple of months learning my way around Drupal 7 and the Panopoly distro (and waiting patiently for Drupal 8 to be ready to use), and it seems like every time I think I’ve finally got the hang of it, I find something new to try out.

Nevertheless, my employer’s primary marketing angle is that we create custom-built websites from scratch to meet our clients’ specific requirements, and I’m still the most comfortable when I can get straight into the HTML, CSS, JavaScript, PHP and SQL code to make things just right. Like it or not, using a CMS means accepting a few limitations. And with some clients, those limitations can be deal-breakers.

force browsers to print background colors of elements

Most browsers won’t print background colors, and print-only CSS can (or should) be set to force all text to be black so it looks good on a white background. But what about images? What if you have a logo with white text and a transparent background that’s normally displayed over a dark background? Webkit browsers support the -webkit-print-color-adjust: exact style, but that still leaves out Firefox. Continue reading