<button>Let's Go !</button>| <!DOCTYPE html> | |
| <html prefix="og: http://ogp.me/ns#"> | |
| <head> | |
| <!-- content-type, which overrides http equivalent header. Because of charset, this meta should be set at first. --> | |
| <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> | |
| <!-- Overrides http equivalent header. This tells IE to use the most updated engine. --> | |
| <meta http-equiv="X-UA-Compatible" content="IE=Edge"> | |
| <!-- Tells crawlers how to crawl this page, and the role of this page. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta --> | |
| <meta name="robots" content="index, follow"> |
| 'use strict' | |
| const timeout = ms => new Promise(res => setTimeout(res, ms)) | |
| function convinceMe (convince) { | |
| let unixTime = Math.round(+new Date() / 1000) | |
| console.log(`Delay ${convince} at ${unixTime}`) | |
| } | |
| async function delay () { |
| db.currentOp().inprog.forEach( | |
| function(op) { | |
| if(op.secs_running > 5) printjson(op); | |
| } | |
| ) |
| @mixin grid-offset( | |
| // Mobile First Media Queries | |
| $small-up-screens: false, | |
| $medium-up-screens: false, | |
| $large-up-screens: false, | |
| $xlarge-up-screens: false, | |
| $xxlarge-up-screens: false, | |
| // Specific Range Media Queries | |
| $small-only-screens: false, | |
| $medium-only-screens: false, |
| // | |
| // Grid Columns | |
| // | |
| // A mixin to help make Foundation's grid-column mixin easier | |
| // to use when specifying multiple media quries/screen sizes | |
| @mixin grid-columns( | |
| // Mobile First Media Queries | |
| $small-up-screens: false, | |
| $medium-up-screens: false, |
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso
| # | |
| # Sample nginx.conf optimized for EC2 c1.medium to xlarge instances. | |
| # Also look at the haproxy.conf file for how the backend is balanced. | |
| # | |
| user "nginx" "nginx"; | |
| worker_processes 10; | |
| error_log /var/log/nginx_error.log info; |
| function slugify(text) | |
| { | |
| return text.toString().toLowerCase() | |
| .replace(/\s+/g, '-') // Replace spaces with - | |
| .replace(/[^\w\-]+/g, '') // Remove all non-word chars | |
| .replace(/\-\-+/g, '-') // Replace multiple - with single - | |
| .replace(/^-+/, '') // Trim - from start of text | |
| .replace(/-+$/, ''); // Trim - from end of text | |
| } |
