Andreas Oldeskog aolde

DEPRECATED

Please see: https://github.com/kevinSuttle/html-meta-tags, thanks for the idea @dandv!

Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/

Basic HTML Meta Tags

Here is a high level overview for what you need to do to get most of an Android environment setup and maintained.

Prerequisites (for Homebrew at a minimum, lots of other tools need these too):

XCode is installed (via the App Store)
XCode command line tools are installed (xcode-select --install will prompt up a dialog)
Java

Install Homebrew:

ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"

$/
  artifacts/
  build/
  docs/
  lib/
  packages/
  samples/
  src/
 tests/

Styling native elements

Native HTML controls are a challenge to style. You can style any element in the web platform that uses Shadow DOM with a pseudo element ::pseudo-element or the /deep/ path selector.

video::webkit-media-controls-timeline {
  background-color: lime;
}

video /deep/ input[type=range] {

Install Docker on Windows Nano Server

Connect remotely to the nano server

Open PowerShell as Administrator
Test-WSMan xx.xxx.xxx.xx
Enable-PSRemoting
Enter public IP address of nano server: $ip = "xx.xxx.xxx.xx"
Set-Item WSMan:\localhost\Client\TrustedHosts "$ip" -Force
Enter-PSSession -ComputerName $ip -Credential "~\Administrator"

Sony Bravia HTTP API

The sony bravia has a HTTP API interacted with using a Pre-Shared key. There's a more complex auth flow but I've not described it here.

There wasn't any documentation, so I've written some. If you're a TV integrator don't read this, you'll laugh. I'm probably just getting confused by UPnP.

Disclaimer: I've only tested this on my TV, which is a KDL-50W829B. Your TV might not have all of the services; see Available services section for how to discover what your TV supports.

	var parser = document.createElement('a');
	parser.href = "http://example.com:3000/pathname/?search=test#hash";

	parser.protocol; // => "http:"
	parser.hostname; // => "example.com"
	parser.port; // => "3000"
	parser.pathname; // => "/pathname/"
	parser.search; // => "?search=test"
	parser.hash; // => "#hash"
	parser.host; // => "example.com:3000"

	/* ---------------------------------------------------------- */
	/* */
	/* A media query that captures: */
	/* */
	/* - Retina iOS devices */
	/* - Retina Macs running Safari */
	/* - High DPI Windows PCs running IE 8 and above */
	/* - Low DPI Windows PCs running IE, zoomed in */
	/* - Low DPI Windows PCs and Macs running Firefox, zoomed in */
	/* - Android hdpi devices and above */

	#
	# Assumptions
	#
	# 1. If you have a Octopus release deployed, say 1.0.0.73, there is a git
	# tag set for that commit in GitHub that is "v1.0.0.73".
	#
	# 2. You have TeamCity label each successful build in GitHub with the format
	# "v{build number}. Sidenote: it appears that TeamCity only labels the
	# default branch, but not feature branches.
	#

	/**
	* This file/module contains all configuration for the build process.
	*/

	/**
	* Load requires and directory resources
	*/
	var join = require('path').join,
	bowerrc = JSON.parse(require('fs').readFileSync('./.bowerrc', {encoding: 'utf8'})),
	bowerJSON = bowerrc.json.replace(/^\.?\/?/, './'),