Alex Kilgour alexkilgour

example. set this up in markdown. then view in nice viewer with - http://gist.io/4195552

Theme & Color

I use Soda Theme (dark), with Monokai.

Packages

First add Package Control. For SublimeText 2, paste the following in Terminal:

import urllib2,os; pf='Package Control.sublime-package'; ipp = sublime.installed_packages_path(); os.makedirs( ipp ) if not os.path.exists(ipp) else None; urllib2.install_opener( urllib2.build_opener( urllib2.ProxyHandler( ))); open( os.path.join( ipp, pf), 'wb' ).write( urllib2.urlopen( 'http://sublime.wbond.net/' +pf.replace( ' ','%20' )).read()); print( 'Please restart Sublime Text to finish installation')

Component javascript hooks

Accessing DOM elements

This should be added to any DOM element you need to access via javascript
Should be added as part of the html not using .data()
Should never be removed or edited
Should be used only to access the element(s)
Names should be lowercase, hyphen separated, descriptive

Fenced code blocks inside ordered and unordered lists

This is a numbered list.
I'm going to include a fenced code block as part of this bullet:
```
Code
More Code
```

Keybase proof

I hereby claim:

I am alexkilgour on github.
I am howlingmad (https://keybase.io/howlingmad) on keybase.
I have a public key whose fingerprint is 2BCE 7576 861D 7D10 F373 18DD 3CCD EE9B 867E C911

To claim this, I am signing this object:

How we write CSS

Our approach to writing CSS aims to provide a framework for working that allows individual teams the flexibility to make project appropriate decisions within a company wide strcuture. By following a consistent approach across teams we aim to make it easier to move developers around and allow for the easy evolution of our approach within a large company.

We advocate a componentised approach that is designed for scale, is based on SASS (using the SCSS syntax), follows the BEM Methodology, and borrows elements from OOCSS, Utility Classes, and ITCSS.

Architecture

The architecture is split into a series of 'levels' with each level representing a folder that contains our SASS split out into different

Create a template that includes handlebars expressions that all the addition of classes

<!-- button.hbs -->
<a id="{{id}}" data-component="{{jsHook}}" class="c-button {{utilityClasses}} {{extensionClasses}}">
  {{text}}
</a>

You can then extend the component within your app by either adding a utility class, or by extending the component with a modifier

Proposed structure for Oscar frontend

Current: oscar-sites-bmc

https://github.com/springernature/oscar/wiki/working-with-css

oscar-sites-bmc
└── src
    └── main

	/**
	* The pseudo-element 'content' property doesnt accept normal (») style
	* HTML entities. These variables below easy the pain of looking up the HEX codes...
	*
	* Referenced from http://www.danshort.com/HTMLentities/
	*
	* TODO: Add all the other entities? Worth it? Some day? Maybe?
	*/

	// Punctuation

	// rounding down to specified decimal places
	var round = function(value, decimals) {
	return Math.floor(value * Math.pow(10,decimals)) / Math.pow(10,decimals);
	}