jedfoster

$cmln-toc-entry-number-padding-right: 1rem;

$selector: "";
@for $i from 1 through 6 {
	$selector: "#{$selector} ul li";
	#{$selector} a .tocnumber { min-width: $cmln-toc-entry-number-padding-right + 0.25rem + 0.75rem * $i; }
}

jedfoster

#3D Text in Sass

Inspired by @mdo

jedfoster

// ----
// Sass (v3.3.0.rc.1)
// Compass (v0.13.alpha.10)
// ----

/*
A slightly more automated approach to BEM modifier classes:
using '&' parent selector interpolation, modifiers extend their bases,
so that HTML markup requires only the modifier class not the base *and* modifier
*/

jedfoster

<div class='container'>

  <h1>SASS - Variables</h1>
  <h2><span>Basic</span> - Getting Started</h2>

  <p id='mypara'>Lorem ipsum dolor sit amet, consectetur
  adipiscing elit, sed do eiusmod tempor <br>
  incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis
  nostrud exercitation ullamco laboris nisi</p>

jedfoster

<h1>Theming UI Components</h1>

<p>Each component needs to be aware that it may be used within a colour scheme so it needs to own the process 
of creating the various classes required to support different uses. Sometimes semantic classes are the way forward, 
but perhaps we should just allow the use of names to describe the particular style (think Solarized & Darcula, not Primary, Secondary, Success, etc.)</p>
<p>Here we create a themes map, which contains the colour definitions for a variety of named themes. 
This makes it easier to re-use a colour scheme across components and removes the cases where
two component modifier classes (with different names) confusingly implement the same colour scheme. 
e.g. no <code>.btn--primary</code> and <code>.panel--brand</code> which actually use the same colours</p>
<p>Read more about this approach in this blog post - <a href="http://www.ian-thomas.net/a-sassy-approach-to-theming-components/" class="link-t-sassmeister-dark">A Sassy Approach To Theming Components</a></p>

jedfoster

Local SSL websites on macOS Sierra

These instructions will guide you through the process of setting up local, trusted websites on your own computer.

These instructions are intended to be used on macOS Sierra, but they have been known to work in El Capitan, Yosemite, Mavericks, and Mountain Lion.

NOTE: You may substitute the edit command for nano, vim, or whatever the editor of your choice is. Personally, I forward the edit command to Sublime Text:

alias edit="/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl"

jedfoster

The task of predicting election results is fraught with failure. When opinion polls, run on statistical methodologies, themselves get it wrong more often than not, what chance does a prognosis based on subjective analysis and anecdotal evidence fare? Not even a wild one.

Yet I attempt. Because events that alter the voting preference of an entire nation to cause a regime change are like black swan events. High impact events that cause to defeat the current incumbent are an extreme rarity. Therefore the uncertainty is reduced and we can reach a reasonable conclusion.

The null hypothesis is that Mr. Modi will win 2019. In ordinary language, this is the prevalent belief. The alternative hypothesis or the contrarian claim, is that Mr. Modi will not win. 

In statistics, you would take a random population sample to calculate a test static and examine its value. If the value is in the region of rejection, the prevalent belief is rejected, thus accepting the contrarian claim. Otherwise, that is, the test statistic 

jedfoster

Vim without NERD tree or CtrlP

I used to use NERD tree for quite a while, then switched to CtrlP for something a little more lightweight. My setup now includes zero file browser or tree view, and instead uses native Vim fuzzy search and auto-directory switching.

Fuzzy Search

There is a super sweet feature in Vim whereby you can fuzzy find your files using **/*, e.g.:

:vsp **/*<partial file name><Tab>

jedfoster

jedfoster

.
├── actions
├── stores
├── views
│   ├── Anonymous
│   │   ├── __tests__
│   │   ├── views
│   │   │   ├── Home
│   │   │   │   ├── __tests__
│   │   │   │   └── Handler.js