tweak: lower base font size to 18px

set title case on posts

Author: studioromeo

src/posts/2013-04-25-easy-digital-downloads-receipt-bcc.md

@@ -1,4 +1,5 @@
 ---
+title: Easy Digital Downloads Receipt BCC
 summary: Earlier this evening Pippin, author of Easy Digital Downloads tweeted about an idea for a simple little plugin to extend EDD's customer receipts
 ---
 

src/posts/2013-06-11-using-guard-phpunit-with-composer.md

@@ -1,5 +1,5 @@
 ---
-title: Using guard-phpunit with composer
+title: Using Guard-phpunit with Composer
 ---
 
 While reading through a book on unit testing with PHP I ran into a few issues using guard with phpunit. This article guides me (and maybe you) through the process of installing & configuring guard with PHPUnit.

src/posts/2013-11-12-anchor-cms-in-laravel-part-1.md

@@ -1,4 +1,5 @@
 ---
+title: Anchor CMS in Laravel Part One
 summary: Part 1 of building AnchorCMS in Laravel. I really like AnchorCMS, its super clean and simple and I like the extensibility of Laravel. Can we combine the two?
 ---
 

src/posts/2023-02-11-dev-diaries-episode-1.md

@@ -32,7 +32,7 @@ We could just risk it and fix problems as we discover them but that sounds like
 
 A few years ago my friend [Tom](https://www.tomseldon.co.uk) created a section in the app for dev tooling to live which is super handy. A new tool was added which had one job…
 
-## The Task
+## The task
 
 For every topic downloaded in the app, first run all the transformers split between old and new, then compare them! If they match then great carry on. If they don't match then stop and show where they differ in something thats easy to use.
 
@@ -42,7 +42,7 @@ We'd also need to test this against other content languages such as Spanish. Dif
 
 Ok well to build this we have to solve a few problems along the way.
 
-## Problem 1: How to Flip Between Old and New Transformers
+## Problem #1: How to flip ­between old and new transformers?
 
 First up we want to restrict how much code we have to write at once before we can get to testing. The transformation layer is sits below the repository layer so thats where we need to switch between old and new transformers. Each repository extends a `BaseRepository` class which contains some helper methods that all repositories can use.
 
@@ -70,7 +70,7 @@ find (topicId) {
 
 Cool thats the first problem sorted, we can now toggle between old and new transformers 🙌
 
-## Problem 2: How Can We Toggle the Feature on Demand
+## Problem #2: How can we ­toggle the feature on demand?
 
 In the past our feature flag looked at the state from two sources, either remotely via firebase or locally via the codebase depending on the type of flag it was. This is fine 99% of the time but for our tool we wanted to be able to toggle the feature at runtime, otherwise we'd be comparing the same transformer against itself 🤦‍♂️
 
@@ -100,7 +100,7 @@ Cool, so this allows us to change the state of a flag whenever we want. A nice b
 
 ![A screenshot of the app with a list of feature flags. Next to it are toggles that are currently disabled](/img/2023/dev-dairy-episode-1/featureflag.png)
 
-## Making the Page
+## Making the page
 
 Ok so the page is actually pretty simple, it's just some text that describes what it does and a button that starts the testing.
 
@@ -228,7 +228,7 @@ This is pretty similar to the mock code earlier. We disable the flag, test, enab
 
 If they don't match we throw an error with the repository and topic that failed. Also we log to the console both old and new JSON so we can dig into it and see whats up.
 
-### Quality of Life Extras
+### Quality of life extras
 
 We're more or less done with the tool now which is great news but I wanted to add a few extra things just to make life using the tool a bit nicer. As it stands if there was a difference in the output between transformers it would be pretty tricky to know exactly where that difference is, these objects are often quite big and heavily nested!
 

src/posts/2023-04-23-dev-diaries-episode-2.md

@@ -1,5 +1,5 @@
 ---
-title: Lessons Learned the Hard Way With Dependencies
+title: Lessons Learned the Hard Way with Dependencies
 summary: Learning the hard way that sometimes it's better to build your own than to struggle with existing tools
 tags:
     - Dev Diaries
@@ -25,17 +25,17 @@ Theres a lot that some dependencies offer. They're often authored by multiple pe
 
 But be careful. It's worth taking the time to look at the dependencies available to you. Look at the common things like:
 
--   How many authors are there?
--   Whats the activity like on the repository? Is there a lot of recent action or has it been untouched for years? This might not be a bad thing if the dependency does what it needs to and has no bugs but it could also be a sign of a dead project.
--   Whats the license like? Can you even use this dependency? Is there a fee you need to pay?
+-   _How many authors are there?_
+-   _Whats the activity like on the repository?_ <br/>Is there a lot of recent action or has it been untouched for years? This might not be a bad thing if the dependency does what it needs to and has no bugs but it could also be a sign of a dead project.
+-   _Whats the license like?_ <br/>Can you even use this dependency? Is there a fee you need to pay?
 
-But there are also more nuanced things to look at, personal to you and your team / project.
+There are also more nuanced things to look at, personal to you, your team & project.
 
-Check out the code. How much of what it does is relevant to your needs? For example the dependency we were using was complaint to the entire OpenID Connect spec. We only needed the Authorization Code flow so a lot of the code in the dependency was redundant. When it came to something being wrong we had a lot of irrelevant code to comb through to understand what was going on.
+Check out the code. How much of what it does is relevant to your needs? For example our dependency included code for the entire OpenID Connect spec. We only needed the Authorization Code flow so a lot of the code in the dependency was redundant. During debugging this meant we had a lot of irrelevant code to comb through to understand what was going on.
 
-If you do need to tweak, can you? Without it being a bit of a pain in the bum. Some dependencies that are a bit larger make use of adapter / strategy patterns that allow you to write custom code that adheres to an interface the dependency asks for. If you can't is it patchable?
+If you do need to tweak, can you? Without it being a bit of a pain in the bum. Some dependencies that are a bit larger make use of adapter / strategy patterns that allow you to write custom code that adheres to an interface. If you can't, is it patchable?
 
-Lastly should you need to switch to something else, what options are available to you? Are you spoilt for choice or is it more slim pickings? If its the latter how confident are you in being able to replace it with something you've written?
+Lastly should you need to switch to something else, what options are available to you? Are you spoilt for choice or is it slim pickings? If its the latter how confident are you in being able to replace it with something you've written?
 
 As for us, we're on the road towards writing our own package. It's a slow process but we're getting there, cobbling together knowledge from specs and other projects to build something that works for us.
 

src/scss/base.body.scss

@@ -1,5 +1,5 @@
 html {
-    font-size: 125%;
+    font-size: 112.5%;
 }
 
 body {

src/scss/settings.scss

@@ -16,7 +16,7 @@ $colour-green-dark: darken($colour-green, 10%);
 $colour-green-light: lighten($colour-green, 45%);
 
 // Widths & Spacing
-$container-width: 46rem;
+$container-width: 50rem;
 $article-gutter: 3.125rem;
 $article-gutter-mobile: $article-gutter / 2;