Grav has a great plugin for code highlighting.

It utilises the jQuery plugin highlight.js.

Markdown Extra allow the use of code fencing with 3 backticks. The plugin adds code highlighting by including the language name after the ticks. eg.

    ``` javascript
    code goes here  

But I couldn't find a list of the supported languages, so I've pulled them out of the code:

Lang Lang Lang
apache bash coffeescript
cpp cs css
diff dts ini
java javascript json
http makefile markdown
nginx objectivec perl
php python ruby
sql twig xml

Grav can also change the syntax colouring theme with a change in the front matter.

Valid theme options are:

Theme Theme Theme
arta ascetic atelier-dune.dark
atelier-dune.light atelier-forest.dark atelier-forest.light
atelier-heath.dark atelier-heath.light atelier-lakeside.dark
atelier-lakeside.light atelier-seaside.dark atelier-seaside.light
brown_paper codepen-embed color-brewer
dark default docco
far foundation github
googlecode hybrid idea
ir_black kimbie.dark kimbie.light
learn magula mono-blue
monokai_sublime monokai obsidian
paraiso.dark paraiso.light pojoaque
railscasts rainbow school_book
solarized_dark solarized_light sunburst
tomorrow-night-blue tomorrow-night-bright tomorrow-night-eighties
tomorrow-night tomorrow vs
xcode zenburn agate
androidstudio atelier-cave.dark atelier-cave.light
atelier-estuary.dark atelier-estuary.light atelier-plateau.dark
atelier-plateau.light atelier-savanna.dark atelier-savanna.light
atelier-sulphurpool.dark atelier-sulphurpool.light darkula
github-gist pojoaque school_bank

View a live demo of the themes.

Pixel Density, Demystified” by @pnowelldesign

How pixel density works and how it affects your designs.

PX, DPI, PPI, PT, DP – I'm 99% sure I've got my head around this. Great explanation.

This week I found a bug in a plug-in we've been using on a Craft project.

The plugin is Google Maps for Craft, it's been in beta for quite a while but is based on the long released Google Maps for ExpressionEngine.

In the end it was a simple bug to fix – aren't they always? - but it took a while to understand how everything worked and where to fix.

It was a JS bug rather than a PHP bug but that's beside the point.

Code sharing, Version Control, GitHub and the Web is amazing

I could have filed a bug and crossed my fingers, but for a 'free' product that's not how it works. All the code is available on GitHub so I forked and found a fix myself. As our project is in Git I'd be able to keep a track of my changes if the plugin gets updated, but there's no need to email Justin with a fix because GitHub can handle it.

I forked, applied the fix and submitted a pull request all on GitHub – not forgetting that's all in the Browser.

As I typed in a message to go with the pull request I sat back in wonder about the tools at our disposal. This wasn't possible 10 years ago. Things move fast compared to other industries and we adapt to what's 'normal' just as quickly – it's easy to forget how much has changed.

How great is it to be a Web Dev in 2016?