SelectNav.js – responsive drop-down menu – pure JavaScript

SelectNav.js is a JavaScript plugin that lets you convert your website navigation into a select drop-down menu. Used together with media queries it helps you to create a space saving, responsive navigation for small screen devices.

mobile-dropdown-navigation-02-selectnav-ad06af950d8aa770b5c774d266090450

vía SelectNav.js – responsive drop-down menu – pure JavaScript.

SVG with external CSS and media queries – Lab – Graham Bird

This page demonstrates two interesting aspects of SVG that you may not be aware of: styling the SVG with an external CSS file and amending the SVG based on media queries. Below are the four most common ways to display SVG in a browser. If both external CSS and media queries are working, you should see four green Twitter birds with FTW.

It appears that displaying SVG with the <object> tag is still the best method (assuming it doesn’t have to be a background) as it honours both external CSS references and media queries in all modern browsers – plus of course it allows fallback content for browsers that don’t support SVG.

vía SVG with external CSS and media queries – Lab – Graham Bird.

Pure CSS3 LavaLamp Menu – Script Tutorials

LavaLamp CSS3I think that you have already seen animated menus with LavaLamp effect (based on jQuery plugin). Today I would like you to tell how to repeat same behavior only with CSS3 (without any javascript). I have to use CSS3 transitions in our menu (to animate elements). So, if you are ready, lets start.

vía Pure CSS3 LavaLamp Menu – Script Tutorials.

Other tutorials:

jQuery MagicLine Navigation | CSS-Tricks

CoffeeScript

CoffeeScript is a little language that compiles into JavaScript. Underneath all those awkward braces and semicolons, JavaScript has always had a gorgeous object model at its heart. CoffeeScript is an attempt to expose the good parts of JavaScript in a simple way.

The golden rule of CoffeeScript is: “It’s just JavaScript”. The code compiles one-to-one into the equivalent JS, and there is no interpretation at runtime. You can use any existing JavaScript library seamlessly from CoffeeScript (and vice-versa). The compiled output is readable and pretty-printed, passes through JavaScript Lint without warnings, will work in every JavaScript runtime, and tends to run as fast or faster than the equivalent handwritten JavaScript.

CoffeeScript

vía CoffeeScript.