'extensions': ['codehilite(css_class=highlight)', 'extra', 'headerid', 'toc'],
'extension_configs': {
'markdown.extensions.codehilite': {'css_class': 'highlight'}
'output_format': 'html5'
View .travis.yml
- make publish
provider: pages
local_dir: ./output
skip_cleanup: true
github_token: $GH_TOKEN # Set in dashboard
target_branch: master
branch: source
View hmac_laravel.php
public function verifyRequest(Request $request, $secret) {
// Per the Shopify docs:
// Everything except hmac and signature...
$signature = $request->except(['hmac', 'signature']);
// Sorted lexilogically...
// Special characters replaced...
foreach ($signature as $k => $val) {

Anatomy of a Meltdown

In children, a lot of people mistake them for temper tantrums, but meltdowns are a different animal. Meltdowns are often as much physiological as they are emotional in nature.

After going through my last one, I thought I’d write about it. Both in an effort to bring myself back online, and to help others understand what goes on from the point of view of someone “on the inside.”


While there may be a “final straw” that triggers a meltdown event, that final trigger is usually the tip of a much larger stressor or series of stressors. I once saw it discribed as a reaction to “too much” — too much noise, too much light, too many people. It’s a fitting description, I think.

View Makefile
github: publish
ghp-import -b $(GITHUB_PAGES_BRANCH) -n $(OUTPUTDIR)
@git push -fq https://${GH_TOKEN}$(TRAVIS_REPO_SLUG).git $(GITHUB_PAGES_BRANCH) > /dev/null
View css
*:target::before {
height: 30px;
margin-top: -63px;
display: block;
content: " ";
visibility: hidden;
View index.html
<!-- The container can be anything, I just used <div> for the sake of getting this up there. -->
<!-- Let's add an overlay with some text! -->
<div class="framed with-overlay">
<img src="path/to/image.jpg" />
<div class="overlay">An overlay</div>
<!-- Or, just have the frame itself -->
<div class="framed">