Bash snippets to use in GeekTool
#!/bin/sh | |
# Alot of these configs have been taken from the various places | |
# on the web, most from here | |
# https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
# Set the colours you can use | |
black='\033[0;30m' | |
white='\033[0;37m' | |
red='\033[0;31m' |
// Bootstrap Mid-Small - col-ms-* - the missing grid set for Bootstrap3. | |
// | |
// This is a hack to fill the gap between 480 and 760 pixels - a missing range | |
// in the bootstrap responsive grid structure. Use these classes to style pages | |
// on cellphones when they transition from portrait to landscape. | |
// | |
// NOTE: Here I use SASS instead of LESS for styling. To convert to LESS | |
// replace '$screen' with '@screen' and '$grid' with '@grid'. | |
// | |
// See https://github.com/twbs/bootstrap/issues/10203 for more info. |
Please set the $vertical variable to false to see the horizontal version.
Forked from Peiwen Lu's Pen CSS3 Timeline.
A Pen by Nathan Scott on CodePen.
/*------------------------------------*\ | |
DROPDOWNS | |
\*------------------------------------*/ | |
// Based on the CSS from this blog post on CSS Wizardry: | |
// http://csswizardry.com/2011/02/creating-a-pure-css-dropdown-menu/ | |
// Predefine the variables below in order to alter and enable specific features. | |
$inuit-dropdown-inter-radius: $inuit-btn-radius !default; | |
$inuit-dropdown-max-width: 250px; |
Working out what sizes/formats/filenames to use for favicons is confusing---especially if you're trying to support legacy browsers. There are some great lists out there, but they are often out-of-date or incomplete. So here's a new one:
Place favicon.ico
in root directory---include a 16x16 and 32x32 image. This will be effective for most browsers. Do not add a link to the head---browsers that can use png icons may ignore them in favour of the lower-quality ico if you do.
favicon.png
as a 32x32 icon for browsers that can handle png.
Icons for use in modern browsers (eg. Safari 8+) and mobile devices.
--- | |
layout: none | |
--- | |
<?xml version="1.0" encoding="UTF-8"?> | |
<rss version="2.0" xmlns:excerpt="http://wordpress.org/export/1.2/excerpt/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:wp="http://wordpress.org/export/1.2/"> | |
<channel> | |
<title>{{ site.name }}</title> | |
<link>{{ site.url }}</link> | |
<description>{{ site.description | xml_escape }}</description> | |
<pubDate/> |
Without plugins, it's difficult to use obfuscated email addresses in Hugo. Additionally, Hugo will aggressively escape anything you introduce to a template, especially if it's a href
attribute.
To use a character entities obfuscation technique (eg. that of http://wbwip.com/wbw/emailencoder.html), place email.html
in the layouts/shortcodes
folder, and place emails.yml
in the data
folder.
The contact
email in emails.yml
is the character entity-encoded form of [email protected]
. It will be the default email used if you call the email shortcode (by using {{< email >}}
or {{< email contact >}}
in your page content) without any parameters. You can add other emails to emails.yml
and use them in the email shortcode by passing their key as a parameter, eg: {{< email newKey >}}
Method (and limitations) described here: http://nadeausoftware.com/articles/2007/05/stop_spammer_email_harvesters_obfuscating_email_addresses
I hereby claim:
- I am ngsctt on github.
- I am nathanscott (https://keybase.io/nathanscott) on keybase.
- I have a public key ASAQjsej-Kf0IgUTzM6b3NjkVOGr66gdevswYFB_N-_hmwo
To claim this, I am signing this object: