exception_handler 0.8.0.0 → 0.8.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 49e2fc9996c4c5b2d6f795f5e08214d8fcb6d8228b735416903da5bd0e149ac6
-  data.tar.gz: 7c08ef59fa0f7766c07ce6da3c6a92d90dd543ad4c7bb1e3884289bd309e309d
+  metadata.gz: ba54148f25815a5f2df409c4261ade99ffa4f2f96c4a0ae354149ba539bffac3
+  data.tar.gz: ee20ae2ed6c8be539b8ffb0388da0b2680aaaaf5aa793a0df49fe38e5230ea2e
 SHA512:
-  metadata.gz: 937f0e527726d0c0af814b16b9a276290dad5181eb482280d9ed9230bde06d8094a88ef9e8d5abe27656c86c593b20a7ffcde427c7d0782cd55ba7d7b3d1be2c
-  data.tar.gz: 1ca6e353d9a05b023bcc2ca23321135cd7215b6a7be448d69979b698b309033a3c73d435678313f584fb8caac6e7eb48323ab2d7f73bcf62235a03df78ffb228
+  metadata.gz: e5a14eeb3beb2ffab2fe1289acd377423242d980294cf0872e85ba86aeb7165027de92b2057d034a1730ff4e38fb716b38052c81d1502143a658367e1a1ae23c
+  data.tar.gz: '0890e4e17d5bb8c94cefb0dc24adb8d40f7fc49c8c9cb7f4e6904221e61750dd23f886ce1af3141316f5dc14152e8ae6cabc1bd3285a90a6e5c3646d8fa7783d'

data/.coveralls.yml

@@ -0,0 +1 @@
+service_name: travis-ci

data/.gitignore

@@ -22,6 +22,7 @@ tmp
 mkmf.log
 *.tmp
 .rspec_status
+/coverage/
 
 ##########################################################
 ##########################################################

data/.rspec

@@ -1,3 +1,3 @@
---format progress
---color
---require spec_helper
+--format progress
+--color
+--require spec_helper

data/.travis.yml

@@ -5,3 +5,9 @@ rvm:
  - 2.4.4
  - 2.5.1
  - ruby-head
+notifications:
+    - false
+scripts:
+  - bundle exec rspec
+after_script:
+  - bundle exec rake coveralls:push

data/README.md

@@ -1,179 +1,106 @@
-<p align="center">
-  <strong>💣 README Currently Being Updated 💣 - Gem Incorporated into 💀 <a href="https://www.vpsdeploy.com" title="Custom VPS Deployment For Rails"><u>VPSDeploy.com - VPS Deployment Solution</u></a> 💀 -<br/><code>Custom Programming Tutorials</code> + <code>Deployment Infrastructure</code> For Cloud VPS Providers...</strong>
-</p>
-<hr />
-
 ![Exception Handler](readme/title.jpg "Exception Handler Logo")
 
-<p align="center">
-  <img src="./readme/dev.png" /><br />
-</p>
-
-<p align="center">
-  <img src="/readme/titles/initial.png" width="90%" />
-</p>
-
-<p align="center">
-  <strong>➡️ <code>ExceptionHandler</code> is a <a href="https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677"><code>Custom Error Pages Gem</code></a> For Ruby on Rails ⬅️</strong> - With <strong>160,000+ downloads</strong>, it is one of the most <br /> <strong>popular</strong>, <strong>robust</strong> & <strong>extensible</strong> exceptions management gems for <strong><a href="https://rubygems.org/gems/exception_handler">Ruby on Rails 4 & 5+</a></strong>...
-</p>
+<!-- Intro -->
+<div id="intro">
+  <h4 align="center"><code><strong><a href="https://www.github.com/richpeck/exception_handler">ExceptionHandler</a></strong></code> is presently the MOST POPULAR exceptions gem for <a href="https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677">CUSTOM Rails error pages</a>.</h4>
+  <p align="center">
+    With <strong>290,000+ downloads</strong>, it is the *only* gem to provide <strong>custom 400/500 exception pages for Rails 5 & 6</strong>
+  </p>
+  <p><img src="./readme/dev.png" /></p>
+  <h4 align="center">Current <a href="https://github.com/richpeck/exception_handler/releases"><u>0.8.0.0</u></a> (August 2018)</h4>
+</div>
 
+<!-- Badges -->
 <p align="center">
   <a href="http://badge.fury.io/rb/exception_handler"><img src="https://badge.fury.io/rb/exception_handler.svg" align="absmiddle"></a>
   <a href="http://rubygems.org/gems/exception_handler"><img src="http://ruby-gem-downloads-badge.herokuapp.com/exception_handler/0.5.1?type=total&color=brightgreen" align="absmiddle" /></a>
   <a href="https://codeclimate.com/github/richpeck/exception_handler"><img src="https://codeclimate.com/github/richpeck/exception_handler/badges/gpa.svg" align="absmiddle"/></a>
-  <a href="https://gemnasium.com/richpeck/exception_handler"><img src="https://gemnasium.com/richpeck/exception_handler.svg" align="absmiddle"></a>
   <a href='https://coveralls.io/github/richpeck/exception_handler?branch=master'><img src='https://coveralls.io/repos/github/richpeck/exception_handler/badge.svg?branch=master' alt='Coverage Status' align="absmiddle" /></a>
   <a href="https://travis-ci.org/richpeck/exception_handler"><img src="https://travis-ci.org/richpeck/exception_handler.svg?branch=master" align="absmiddle"></a>
 </p>
 
-<p align="center">
-  <img src="readme/branded/1.jpg" width="425" title="Fully Branded Error Pages" />
-  <img src="readme/branded/2.jpg" width="425" title="Fully Branded Error Pages" />
-</p>
-
-<p align="center">
-  <b>Version <a href="https://github.com/richpeck/exception_handler/releases/tag/v0.8.0.0">🏹 <code>0.8.0.0</code> 🏹</a> has now introduced a number of <b>⭐️ KEY UPGRADES ⭐️</b> including...</b> <br /> 🚧 <strong><A href="#config">New Config Settings</a></strong> 🚧 ▪️ <strong>💻 <strong><A href="#views">Custom Views Options</a></strong> 💻</strong> ▪️ <strong>💬 <a href="#locales"><code>4xx</code>/<code>5xx</code> Locales</a> 💬</strong>...  
-</p>
-
-<p align="center">
-  <img src="readme/branded/1.jpg" width="425" title="Fully Branded Error Pages" /> <img src="readme/branded/2.jpg" width="425" title="Fully Branded Error Pages" />
-  <img src="readme/branded/3.jpg" width="425" title="Fully Branded Error Pages" /> <img src="readme/branded/4.jpg" width="425" title="Fully Branded Error Pages" />
-</p>
-
-<p align="center">
-  <strong>
-    ⚠️ Tutorial shows how it works ⚠️
-    <br /><a href="mailto: rpeck@frontlineutilities.co.uk" title="rpeck@fl.co.uk">✉️ Support Email ✉️</a>
-  </strong>
-</p>
-
 <!-- Navigation -->
 <div id="navigation">
   <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
   <p align="center">
-    <b>⌚️ <a href="#introduction">Introduction</a> ⌚️</b> ❙ <strong>✔️ <a href="#installation">Installation</a> ✔️</strong> ❙ <strong>🔨 <a href="#setup">Setup</a> 🔨</strong> ❙ <strong>☎️ <a href="#support">Support</a> ☎️</strong> ❙ <strong>⭐ <a href="#changelog">Changelog</a> ⭐</strong>
+    <strong>
+      📝 <a href="#introduction">Introduction</a> -
+      ⚠️ <a href="#installation">Installation</a> -
+      🔧 <a href="#configuration">Configuration</a> -
+      ☎️ <a href="#support">Support</a> -
+      ⭐ <a href="#changelog">Changelog</a>
+    </strong>
   </p>
   <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
 </div>
 
-<!-- Version -->
-<p align="center">
-  <img src="./readme/version.jpg" />
-</p>
-
-<p align="center">
-  <img src="readme/check.png" height="22" title="Fully Responsive"               align="absmiddle" />&nbsp; <strong>Responsive</strong> &nbsp;
-  <img src="readme/check.png" height="22" title="Branded Error Pages"            align="absmiddle" />&nbsp; <strong>Branded Error Pages</strong> &nbsp;
-  <img src="readme/check.png" height="22" title="Middleware Exception Handling"  align="absmiddle" />&nbsp; <strong>Middleware Exception Handling</strong> &nbsp;
-  <img src="readme/check.png" height="22" title="Keep Users Informed"            align="absmiddle" />&nbsp; <strong>Fully Customizable</strong> &nbsp;
-</p>
-
-<p align="center">
-  <img src="readme/branded/1.jpg" width="425" title="Fully Branded Error Pages" /> <img src="readme/branded/2.jpg" width="425" title="Fully Branded Error Pages" />
-  <img src="readme/branded/3.jpg" width="425" title="Fully Branded Error Pages" /> <img src="readme/branded/4.jpg" width="425" title="Fully Branded Error Pages" />
-</p>
-
 <!-- Introduction -->
 <div id="introduction">
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
-  <p>
-    <h3>⌚️ Introduction ⌚️</h3>
-  </p>
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
+  <h4>📝 Introduction</h4>
 </div>
 
-➡️ [**`ExceptionHandler`**](https://rubygems.org/gems/exception_handler) ⬅️ was designed to replace Rails' error pages ([`400.html`, `422.html`, `500.html`](https://github.com/rails/rails/tree/ef0b05e78fb0b928c7ef48d3c365dc849af50305/railties/lib/rails/generators/rails/app/templates/public)) with dynamic views...
+---
+<div>
+  <p><b><code>ExceptionHandler</b></code> replaces Rails' default error pages with <strong>dynamic views</strong>.</p>
+  <p>It does this by injecting <a href="https://guides.rubyonrails.org/configuring.html#rails-general-configuration"><code>config.exceptions_app</code></a> with our controller - allowing us to populate erroneous responses with our own HTML. To understand how this works, you need to appreciate how Rails handles errors:</p>
+  <p align="center"><a href="https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/middleware/show_exceptions.rb#L44"><img src="readme/show_exceptions.png" width="550"></a></p>
+  <p>Rails uses <a href="https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/middleware/show_exceptions.rb"><code><strong>ActionDispatch::ShowExceptions</strong></code></a> (above) to generate error responses.</p>
+  <p>Because web browsers (Rails is a web framework) can only interpret <a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Response_message">HTTP responses</a>, Ruby/Rails exceptions have to be translated into something a browser can read. This is done by calling the above middleware.</p>
+  <p>--</p>
+  <p>As highlighted, an HTTP response is built independent of the Rails stack. This includes assigning an HTTP status code and HTML response body. It's the response body which <code><strong>ExceptionHandler</strong></code> is designed to override.</p>
+</div>
 
+<!-- Sep -->
 <p align="center">
-  <img src="./readme/http_codes.png" />
+  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
 </p>
 
-The gem inserts a custom [ `controller`](app/controllers/exception_handler/exceptions_controller.rb) into [`exceptions_app`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration), allowing us to render custom HTML for erroneous requests.
-
-The controller uses a *single* method/view to build a response to errors. This view remains the same for *every* exception; the ONLY change is the *[layout](/app/views/layouts/exception.html.erb)* - depending on the HTTP response being returned (`4xx`/`5xx`).
-
-The beauty lies in the *simplicity* through which this is achieved → rather than having many different elements, its SOLE focus is to provide different HTML responses via differing *layouts*. `ExceptionHandler` does this within the scope of [`ActionView`](http://guides.rubyonrails.org/action_view_overview.html), allowing for the use of `views`, `helpers` and `data` from the database.
-
-Gem works 100% out of the box in `production`, and has the option to be called in [`dev`](#dev) if necessary.
-
---
-
-### 📑 HTTP
-
-The most important thing to understand is that *it doesn't matter* which errors Ruby/Rails raises - they *all* need to be wrapped in a [valid HTTP response](https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html). Due to the nature of HTTP, you only need to facilitate responses for [`4xx`](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors) - [`5xx`](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_errors).
-
-This means that all you're really doing is taking "Ruby" errors and giving them an appropriate [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) & [message body](https://en.wikipedia.org/wiki/HTTP_message_body) (HTML). Rails handles the process for you - the *only* thing we need to worry about is how the HTML is generated.  
-
-What confuses most is the way in which Rails does this. The process is handled by [`ActionDispatch::ShowExceptions`](https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/middleware/show_exceptions.rb#L44) - which builds a new response out of the one passed to it by the exception generator. Through this process, it calls whichever class is present in [`exceptions_app`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration)...
-
-    # show_exceptions.rb
-    def render_exception(request, exception)
-      backtrace_cleaner = request.get_header "action_dispatch.backtrace_cleaner"
-      wrapper = ExceptionWrapper.new(backtrace_cleaner, exception)
-      status  = wrapper.status_code
-      request.set_header "action_dispatch.exception", wrapper.exception
-      request.set_header "action_dispatch.original_path", request.path_info
-      request.path_info = "/#{status}"
-      response = @exceptions_app.call(request.env) #-> this is where the HTML is generated
-      response[1]["X-Cascade"] == "pass" ? pass_response(status) : response
-    rescue Exception => failsafe_error
-      $stderr.puts "Error during failsafe response: #{failsafe_error}\n  #{failsafe_error.backtrace * "\n  "}"
-      FAILSAFE_RESPONSE
-    end
-
-In other words, what a user *sees* has very little to do with the fact Rails experienced an error. `ExceptionHandler` doesn't change this behaviour - it simply adds our own controller/views setup to provide the HTML...
-
-<p align="center">
-  <img src="./readme/middleware.jpg" />
-</p>
+<!-- Installation -->
+<div id="installation">
+  <h4>⚠️ Installation</h4>
+</div>
 
-To better explain, there are **<a href="https://tzamtzis.gr/2017/digital-analytics/http-status-codes/">5️⃣ types of HTTP status code</a>** - [`10x`][10x], [`20x`][20x], [`30x`][30x], [`40x`][40x], & [`50x`][50x].
+---
 
-Each does its own thing, but what's important is they *ALL* describe "responses" that your web browser will receive for HTTP requests. The only *erroneous* status codes are `4xx` (client error) or `5xx` (server error)...
+<div>
+  <p>
+    💎 <u><a href="https://rubygems.org/gems/exception_handler">RubyGems</a></u> (Code) |
+    💻 <u><a href="https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677">Medium</a></u> (Tutorial)
+  </p>
+  <pre><code># Gemfile
+gem 'exception_handler', '~> 0.8.0.0'</code></pre>
+  <p>Because <b>ExceptionHandler</b> is built around a Rails engine, there is <b>nothing</b> to be done to get it working in production. Installing the Gem <b><i>should</i></b> translate your production 4xx/5xx error pages into dynamic views.</p>
+  <p>Environments <u>other</u> than production (development/staging) required the <a href="#dev"><code>dev</code></a> variable to be <code>true</code>.</p>
+</div>
 
+<!-- Sep -->
 <p align="center">
-  <img src="./readme/HTTP.png" />
+  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
 </p>
 
-The point is that when you're dealing with "errors" online, you're *actually* dealing with erroneous **HTTP STATUS CODES**. The response delivered with these codes is *ALWAYS* going to remain the same; difference lying in how they're built (on the server).
-
-By default, `NGinx` + `Apache` use "static" HTML pages to show the errors - if we're using Rails, we have the ability to create *our own* pages. This is exactly what our gem has been designed to do.
-
-**`ExceptionHandler`** provides Rails with the ability to serve ***dynamic*** exception pages, built with **your *own*** layouts/views. By overriding the <a href="http://guides.rubyonrails.org/configuring.html#rails-general-configuration">`exceptions_app`</a> hook, it provides a custom `controller`, `model` and `views` to display custom error pages.
+<!-- configuration -->
+<div id="configuration">
+  <h4>🔧 Configuration</h4>
+</div>
 
-The system is 100% compatible with Rails 4 & 5 and has already been downloaded **180,000+** times...
+---
 
 <p align="center">
-  <img src="readme/branded/1.jpg" width="425" title="Fully Branded Error Pages" /> <img src="readme/branded/2.jpg" width="425" title="Fully Branded Error Pages" />
-  <img src="readme/branded/3.jpg" width="425" title="Fully Branded Error Pages" /> <img src="readme/branded/4.jpg" width="425" title="Fully Branded Error Pages" />
+   <g-emoji class="g-emoji" alias="file_folder" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4c1.png">📁</g-emoji> <a href="#config">Config</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="computer" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4bb.png">💻</g-emoji> <a href="#dev" title="Dev Mode">Dev</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="floppy_disk" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4be.png">💾</g-emoji> <a href="#db">Database</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="email" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/2709.png">✉️</g-emoji>   <a href="#email">Email</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="eyeglasses" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f453.png">👓</g-emoji> <a href="#views">Views</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="speech_balloon" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4ac.png">💬</g-emoji> <a href="#locales">Locales</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="clipboard" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4cb.png">📋</g-emoji> <a href="#layouts">Layouts</a>&nbsp;&nbsp;&nbsp;&nbsp;<g-emoji class="g-emoji" alias="no_entry" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/26d4.png">⛔️</g-emoji> <a href="#custom-exceptions">Custom Exceptions</a>
 </p>
 
-<!-- Setup -->
-<div id="setup">
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
-  <h3 align="center">🔨 Setup 🔨</h3>
-  <p align="center">-- <br />The <i>most</i> important thing to appreciate about the gem is that it's designed to be <b><em>completely</em> unobtrusive</b>.</p>
-  <p align="center">This means that if you're looking at using it, </p>
-  <p align="center"><img src="./readme/dev.png" /></p>
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>  
-  <p align="center">
-    <a href="#config"><img src="readme/titles/icons/config.png" alt="Configuration Options" align="absmiddle" height="24" /> Config</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#dev" title="Dev Mode"><img src="readme/titles/icons/dev.png" alt="Dev" align="absmiddle" height="24" /> Dev</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#database"><img src="readme/titles/icons/database.png" alt="Database" align="absmiddle" height="24" />  Database</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#email"><img src="readme/titles/icons/email.png" alt="Email" align="absmiddle" height="24" />  Email</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#views"><img src="readme/titles/icons/views.png" alt="Views" align="absmiddle" height="24" />  Views</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#locales"><img src="readme/titles/icons/locales.png" alt="Locales" align="absmiddle" height="20" />  Locales</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#custom-exceptions"><img src="readme/titles/icons/custom.png" alt="Custom Exceptions" align="absmiddle" height="18" />  Custom Exceptions</a>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#generators"><img src="readme/titles/icons/generators.png" alt="Generators" align="absmiddle" height="24" />  Generators</a>
-  </p>
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
-</div>
+---
 
 <!-- Config -->
-<p id="config">
-  <h4>🚧 Config 🚧</h4>
-</p>  
+<a name="config"></a>
 
-**The ONLY thing you need to configure `ExceptionHandler` is the [`config`](https://github.com/richpeck/exception_handler/blob/master/lib/exception_handler/config.rb)**.
+The **ONLY** thing you need to manage `ExceptionHandler` is its [`config`](https://github.com/richpeck/exception_handler/blob/master/lib/exception_handler/config.rb) settings.
 
-Whilst the gem **works out of the box** (without any configuration), if you want to manage the [`layouts`](#layouts), [`email`](#email), [`dev`](#dev) or the [`database`](#db), you'll need to set the appropriate values in the config hash ([invoked at init](https://github.com/richpeck/exception_handler/blob/master/lib/exception_handler/engine.rb#L44)).
+Whilst the gem **works out of the box** (without any configuration), if you want to manage the [`layouts`](#layouts), [`email`](#email), [`dev`](#dev) or the [`database`](#db), you'll need to set the appropriate values in the config hash.
 
-This can be done in `config/application.rb` or `config/environments/[env].rb` ↴
+This is done in `config/application.rb` or `config/environments/[env].rb` ↴
 
-```
+```rb
 # config/application.rb
 
 module YourApp
@@ -189,6 +116,11 @@ module YourApp
       db:         nil, # allocates a "table name" into which exceptions are saved (defaults to nil)
       email:      nil, # sends exception emails to a listed email (string // "you@email.com")
 
+      # Custom Exceptions
+      custom_exceptions: {
+        #'ActionController::RoutingError' => :not_found # => example
+      },
+
       # On default 5xx error page, social media links included
       social: {        
         facebook: nil, # Facebook page name   
@@ -238,7 +170,6 @@ module YourApp
 
       }
     }
-
   end
 end
 ```  
@@ -247,31 +178,36 @@ For a full retinue of the available options, you'll be best looking at the [`con
 
 --
 
-If using an [`engine`](http://guides.rubyonrails.org/engines.html), **DON'T need an `initializer`**:
-
-    # lib/engine.rb
-    module YourModule
-      class Engine < Rails::Engine
+If using an [`engine`](http://guides.rubyonrails.org/engines.html), you **DON'T need an `initializer`**:
+```rb
+# lib/engine.rb
+module YourModule
+  class Engine < Rails::Engine
 
-        # => ExceptionHandler
-        # => Works in and out of an initializer
-        config.exception_handler = {
-          dev: nil, # => this will not load the gem in development
-          db:  true # => this will use the :errors table to store exceptions
-        }
-      end
+    # => ExceptionHandler
+    # => Works in and out of an initializer
+    config.exception_handler = {
+      dev: nil, # => this will not load the gem in development
+      db:  true # => this will use the :errors table to store exceptions
+    }
+  end
+end
+```
 
-    end
+The best thing about using a `config` options block is that you are able to only define the options that you require.
 
-The best thing about using a `config` options block is that you are able to only define the options that you require. This means that if you have particular options you *only* wish to run in `staging`, or have single options for `production` etc...  
+If you have particular options you *only* wish to run in `staging`, or have single options for `production` etc, this setup gives you the ability to manage it properly...
 
 ---
 
-<p id="dev">
-  <h4>💻 Dev 💻</h4>
-</p>  
+<!-- Dev -->
+<div id="dev">
+  <h5>💻 Dev</h5>
+</div>
+
+As explained, `ExceptionHandler` does *not* work in `development` by default.
 
-As explained, `ExceptionHandler` does not work in `development` mode by default. This is because it overrides the `exceptions_app` middleware hook - which is only invoked in `production` or `staging`...
+This is because it overrides the `exceptions_app` middleware hook - which is *only* invoked in `production` or `staging`.
 
 <p align="center">
   <img src="./readme/dev.png" />
@@ -285,26 +221,33 @@ To get it working in `development`, you need to override the [`config.consider_a
 
 This is normally done by changing the setting in your Rails config files. However, to make the process simpler for `ExceptionHandler`- we've added a `dev` option which allows you to override the hook through the context of the gem...
 
-```
+```rb
 # config/application.rb
 config.exception_handler = { dev: true }
 ```
 
-This disables [`config.consider_all_requests_local`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration), making Rails behave as it would in production:
+This disables [`config.consider_all_requests_local`](http://guides.rubyonrails.org/configuring.html#rails-general-configuration), making Rails behave as it would in production.
 
-![Dev][dev_img]
+Whilst simple, it's not recommended for extended use. Very good for testing new ideas etc.
 
-Obviously, this has other connotations including the likes of making your requests go through your production server etc. For this reason, it's *STRONGLY* recommended you only use the `dev` option to test your layouts etc.  
+---
 
-----
+<!-- DB -->
+<div id="db">
+  <h5>💾 DB</h5>
+</div>
 
-<p id="database">
-  <h4>💾 Database 💾</h4>
-</p>  
+To save exceptions to your database, you're able to set the `db` option.
 
-If you want to save exceptions to your database, you will need to migrate a new
+Because we use a `controller` to manage the underlying way the system works, we're able to invoke the likes of a [`model`](https://github.com/richpeck/exception_handler/blob/master/app/models/exception_handler/exception.rb) with other functionality.
 
-```
+Ths is done automatically with the latest version of `ExceptionHandler`.
+
+To do this, once you've populated the option with either `true` or a `string`, run `rails db:migrate` from your console.
+
+Our new [`migration system`](https://github.com/richpeck/exception_handler/tree/readme#migrations) will automatically run the migration.
+
+```rb
 # config/application.rb
 config.exception_handler = { db: true }
 ```
@@ -313,124 +256,213 @@ This enables `ActiveRecord::Base` on the [`Exception`](app/models/exception_hand
 
 In order for this to work, your db needs the correct table.
 
-To do this, once you've enabled the option, run `rails db:migrate` from your console. Our new [`migration system`](https://github.com/richpeck/exception_handler/tree/readme#migrations) will automatically run the migration.
-
 ---
 
-<p id="email">
-  <h4>✉️ Email ✉️</h4>
-</p>  
+<!-- Email -->
+<div id="email">
+  <h5>✉️ Email</h5>
+</div>
 
-**`ExceptionHandler` also now sends email notifications.**
+`ExceptionHandler` also sends **email notifications**.
 
 If you want to receive emails whenever your application raises an error, you can do so by adding your email to the config:
 
-    # config/application.rb
-    config.exception_handler = {
-      email: "your@email.com"
-    }
+```rb
+# config/application.rb
+config.exception_handler = {
+  email: "your@email.com"
+}
+```
 
 > **Please Note** this requires [`ActionMailer`](http://guides.rubyonrails.org/action_mailer_basics.html). If you don't have any outbound SMTP server, [`SendGrid`](http://sendgrid.com) is free.
 
-[Full tutorial here](https://github.com/richpeck/exception_handler/wiki/2-Email)
+From version [`0.8.0.0`](https://github.com/richpeck/exception_handler/releases/tag/v0.8.0.0), you're able to define whether email notifications are sent on a per-error basis:
 
+```rb
+# config/application.rb
+config.exception_handlder = {
+
+  # This has to be present for any "notification" declarations to work
+  # Defaults to 'false'
+  email: "test@test.com",
+
+  # Each status code in the new "exceptions" block allows us to define whether email notifications are sent
+  exceptions: {
+    :all => { notification: true },
+    :50x => { notification: false },
+    500 =>  { notification: false }
+  }
+}
+```
 ---
 
-<p id="views">
-  <h4>👓 Views 👓</h4>
-</p>
+<!-- Views -->
+<div id="views">
+  <h5>👓 Views</h5>
+</div>
+
+What *most* people want out of the view is to change the way it ***looks***. This can be done without changing the "view" itself.
 
-The **views** system in `ExceptionHandler` is modular.
+To better explain, if [`ExceptionsController`](https://github.com/richpeck/exception_handler/blob/master/app/controllers/exception_handler/exceptions_controller.rb) is invoked (by `exceptions_app`), it has **ONE** method ([`show`](https://github.com/richpeck/exception_handler/blob/master/app/controllers/exception_handler/exceptions_controller.rb#L42)).
 
-What *most* people want out of the view is to change the way it ***looks***. This can be done without changing the exception "view" itself...
+This method calls the [`show` view](https://github.com/richpeck/exception_handler/blob/master/app/views/exception_handler/exceptions/show.html.erb), which is *entirely* dependent on the locales for content & the layout for the look.
+
+This means that if you wish to change how the view "looks" - you're *either* going to want to change your [layout][layouts] or the [*locales*](#locales). There is NO reason to change the `show` view itself - it's succinct and entirely modular. Whilst you're definitely at liberty to change it, you'll just be making the issue more complicated than it needs to be.
+
+--
+
+We've also included a number of routes which shows in [`dev`](dev) mode (allowing you to test):
 
 <p align="center">
-  <img src="./readme/dev.png" />
+  <img src="./readme/routes.jpg" />
 </p>
 
-To better explain, if [`ExceptionsController`](https://github.com/richpeck/exception_handler/blob/0.8/app/controllers/exception_handler/exceptions_controller.rb) is invoked (by `exceptions_app`), it has **ONE** method ([`show`](https://github.com/richpeck/exception_handler/blob/0.8/app/controllers/exception_handler/exceptions_controller.rb#L42)). This method calls the [`show` view](https://github.com/richpeck/exception_handler/blob/0.8/app/views/exception_handler/exceptions/show.html.erb), which is *entirely* dependent on the locales for content & the layout for the look.
+---
 
-This means that if you wish to change how the view "looks" - you're *either* going to want to change your *layouts* or the [*locales*](#locales). There is NO reason to change the `show` view itself - it's succinct and entirely modular. Whilst you're definitely at liberty to change it, you'll just be making the issue more complicated than it needs to be.
+<!-- Locales -->
+<div id="locales">
+  <h5>💬 Locales</h5>
+</div>
 
--
+[Locales](https://github.com/richpeck/exception_handler/blob/Readme/config/locales/exception_handler.en.yml) are used to create interchangeable text (translations/internationalization).
 
-If you wish to change the "layout" / "look", there are **two** options...
+--
 
- * Firstly, you can create your own layout. This is done by changing the
+In `ExceptionHandler`, it provides the wording for each type of error code.
 
- * Secondly,
+By default, the English name of the error is used (`"404"` will appear as `"Not Found"`) - if you want to create custom messages, you're able to do so by referencing the error's ["status_code"](https://github.com/rack/rack/blob/master/lib/rack/utils.rb#L492) within your locales file:
 
----
+```yml
+# config/locales/en.yml
+en:
+  exception_handler:
+    not_found:              "Your message here" # -> 404 page
+    unauthorized:           "You need to login to continue"
+    internal_server_error:  "This is a test to show the %{status} of the error"
+```
 
-<p id="locales">
-  <h4>💬 Locales 💬</h4>
-</p>  
+You get access to [`%{message}` and `%{status}`](https://github.com/richpeck/exception_handler/blob/master/app/views/exception_handler/exceptions/show.html.erb#L1), both inferring from an [`@exception`](https://github.com/richpeck/exception_handler/blob/master/app/controllers/exception_handler/exceptions_controller.rb#L20) object we invoke in the controller...
 
-Locales are used to denote interchangeable text (for different languages).
+ - `%{message}` is the error's actual message ("XYZ file could not be shown")
+ - `%{status}` is the error's status code ("Internal Server Error")
 
-We've used it for a different purpose - to provide text for our "show" view. The beauty of this is that 1) It's entirely modular & 2) It's extensible (we are able to use as many locales as required)...
+--
 
-[[ locales ]]
+By default, only `internal_server_error` is customized by the gem:
 
+```yml
+# config/locales/en.yml
+en:
+  exception_handler:
+    internal_server_error: "<strong>%{status} Error</strong> %{message}"
+```
+---
+
+<!-- Layouts -->
+<div id="layouts">
+  <h5>📋 Layouts</h5>
+</div>
 
-The `ExceptionHandler` view is populated by [`@exception.description`](app/models/exception_handler/exception.rb#L121), which pulls from the `locales`.
+The most attractive feature of `ExceptionHandler` (for most) is its ability to manage [`layouts`](https://guides.rubyonrails.org/layouts_and_rendering.html#structuring-layouts) for HTTP status.
 
-If you want custom messages, you need the following. The key is defined by the HTTP [`status_code`](https://github.com/rack/rack/blob/1.5.2/lib/rack/utils.rb#L544)
+--
 
-    # config/locales/en.yml
-    en:
-      exception_handler:
-        not_found: "Your message here"
-        unauthorized: "You need to login to continue"
-        internal_server_error: "This is a test to show the %{status} of the error"
+The reason for this is due to the way in which Rails works → the "layout" is a "wrapper" for the returned HTML (the "styling" of a page). If you have no layout, it will render the "view" HTML and nothing else.
 
-You get access to `%{message}` and `%{status}`, both inferring from `@exception`.
+This means if you want to change the "look" of a Rails action, you simply have to be able to change the `layout`. You should not change the view at all.
 
----
+To this end, `ExceptionHandler` has been designed around providing a [SINGLE VIEW](app/controllers/exception_handler/exceptions_controller.rb#L44) for exceptions. This view does not need to change (although you're welcome to use a [`generator`][generators] to do so) - the key is the `layout` that's assigned...
 
-<p id="layouts">
-  <h4>📋 Layouts 📋</h4>
-</p>  
+- [`4xx`](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors) errors are given a `nil` layout (by default) (inherits from `ApplicationController` in your main app)
+- [`5xx`](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_errors) errors are assigned our own [`exception`](app/views/layouts/exception.html.erb) layout:
+
+```rb
+# config/application.rb
+config.exception_handler = {
+
+  # The new syntax allows us to assign different values to each HTTP status code
+  # At the moment, only 'layout' & 'notification' are supported
+  # We plan to include several more in the future...
+
+  exceptions: {
+    all: { layout: nil } # -> this will inherit from ApplicationController's layout
+  }
+}
+```
 
-![Layout][layout_img]
+The `layout` system has changed between [`0.7.7.0`](releases/tag/v0.7.7.0) and [`0.8.0.0`](releases/tag/v0.8.0.0).
 
-If you want to change the various layouts, you need to use the [`config`](#config) to set them.
+Building on the former's adoption of HTTP status-centric layouts, it is now the case that we have the `all`, `5xx` and `4xx` options - allowing us to manage the layouts for blocks of HTTP errors respectively:
 
-![Layout][layouts_img]
+```rb
+# config/application.rb
+config.exception_handler = {
+
+  # Old (still works)
+  # No "all" / "4xx"/"5xx" options
+  layouts: {
+    500 => 'exception',
+    501 => 'exception'
+  },
+
+  # New
+  exceptions: {
+    :all => { layout: 'exception' },
+    :4xx => { layout: 'exception' },
+    :5xx => { layout: 'exception' }, # -> this overrides the :all declaration
+    500  => { layout: nil } # -> this overrides the 5xx declaration
+  }
+}
+```
 
-By default, `5xx` errors are shown with our [`exception` layout][layout] - this can be overridden by changing the `config` to use a layout of your choice. If you want to inherit the `ApplicationController` layout, assign the codes to `nil`.
+We've bundled the [`exception`](app/views/layouts/exception.html.erb) layout for `5xx` errors because since these denote internal server errors, it's best to isolate the view system as much as possible. Whilst you're at liberty to change it, we've found it sufficient for most use-cases.
 
 ---
 
+<!-- Custom Exceptions -->
+<div id="custom-exceptions">
+  <h5>⛔️ Custom Exceptions</h5>
+</div>
 
-<p id="custom-exceptions">
-  <h4>⛔️ Custom Exceptions ⛔️</h4>
-</p>
+As mentioned, Rails' primary role is to convert Ruby exceptions into HTTP errors.
 
-**Custom Exceptions also supported in [`0.7.5`](https://github.com/richpeck/exception_handler/releases/tag/0.7.5)**
+Part of this process involves mapping Ruby/Rails exceptions to the equivalent HTTP status code.
 
-Rails handles this for us - [**`config.action_dispatch.rescue_responses`**][rescue_responses]  ↴
+This is done with [`config.action_dispatch.rescue_responses`](https://github.com/rack/rack/blob/master/lib/rack/utils.rb#L492).
 
-![ActionDispatch][config.action_dispatch.rescue_responses]
+<p align="center">
+  <img src="./readme/custom_exceptions.png" />
+</p>
 
-You need to add to the `rescue_responses` hash in your app's config (mapped to [`status codes`](https://github.com/rack/rack/blob/1.5.2/lib/rack/utils.rb#L544)):
+Whilst this works well, it may be the case that you want to map your own classes to an HTTP status code (default is `Internal Server Error`).
 
-    # config/application.rb
-    config.action_dispatch.rescue_responses["ActionController::YourError"] = :bad_request
+If you wanted to keep this functionality inside `ExceptionHandler`, you're able to do it as follows:
 
-Because `HTTP` can only process `4xx` / `5xx` errors, if `Rails` raises an exception, it needs to assign one of the error status codes. **Default** is [`internal_server_error`](https://github.com/rack/rack/blob/1.5.2/lib/rack/utils.rb#L595) - if you'd prefer your app to just return `500` errors for your custom exception, you don't need to explicitly declare them.
+```rb
+# config/application.rb
+config.exception_handler = {
+  custom_exceptions: {
+    'CustomClass::Exception' => :not_found
+  }
+}
+```
 
----
+Alternatively, you're able to still do it with the default Rails behaviour:
 
-<p id="generators">
-  <h4>💼 Generators 💼</h4>
-</p>
+```rb
+# config/application.rb
+config.action_dispatch.rescue_responses = { 'CustomClass::Exception' => :not_found }
+```
+---
 
-**You can generate `ExceptionHandler` into your own application.**
+<!-- Generators -->
+<div id="generators">
+  <h5>💼 Generators</h5>
+</div>
 
-[[ Generator ]]
+If you want to edit the `controller`, `views`, `model` or `assets`, you're able to invoke them in your own application.
 
-The following commands will copy the directories...
+This is done - as with other gems - with a single [`generator`](https://github.com/richpeck/exception_handler/blob/master/lib/generators/exception_handler/views_generator.rb) which takes a series of arguments:
 
     rails g exception_handler:views
     rails g exception_handler:views -v views
@@ -439,74 +471,68 @@ The following commands will copy the directories...
     rails g exception_handler:views -v assets
     rails g exception_handler:views -v views controllers models assets
 
-If you don't include any switches, this will copy **all** the folders put into your app.
+If you don't include any switches, this will copy **all** `ExceptionHandler`'s folders put into your app.
 
 Each switch defines which folders you want (EG `-v views` will only copy `views` dir).
 
 ---
 
-<p id="migrations">
-  <h4>✔️ Migrations (deprecated) ✔️</h4>
-</p>
+<!-- Migrations -->
+<div id="migrations">
+  <h5>✔️ Migrations</h5>
+</div>
 
-**You *DON'T* need to generate a migration any more**.
+You **DON'T** need to generate a migration anymore.
 
 From [`0.7.5`](https://github.com/richpeck/exception_handler/releases/tag/0.7.5), the `migration` generator has been removed in favour of our own [migration system](lib/exception_handler/engine.rb#L58).
 
 The reason we did this was so not to pollute your migrations folder with a worthless file. Our migration doesn't need to be changed - we only have to get it into the database and the gem takes care of the rest...
 
-> If you set the `db` option in config, run `rails db:migrate` and the migration will be run.
+> If you set the [`db`][db] option in config, run `rails db:migrate` and the migration will be run.
 
 To rollback, use the following:
 
     rails db:migrate:down VERSION=000000
 
-The drawback to this is that if you remove `ExceptionHandler` before you rollback the migration, it won't exist anymore. You can **only** fire the `rollback` when you have `ExceptionHandler` installed.
+The drawback to this is that if you remove `ExceptionHandler` before you rollback the migration, it won't exist anymore.
 
-<!-- Support -->
-<div id="support">
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
-  <h3>☎️ Support ☎️</h3>
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>  
-</div>
+You can **only** fire the `rollback` when you have `ExceptionHandler` installed.
 
-<p align="center"><b>🚨 <em>Obviously</em>, if you've taken the time to use the gem, it makes sense to <a href="https://github.com/richpeck/exception_handler/issues">support</a> it 🚨!</b></p>
+<!-- Sep -->
+<p align="center">
+  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+</p>
 
-The fastest way to get a **direct response** is via [email](mailto:rpeck@frontlineutilities.co.uk).
+<!-- Support-->
+<div id="support">
+  <h4>☎️ Support</h4>
+</div>
 
-You're also welcome to access our [**Issues**](https://github.com/richpeck/exception_handler/issues) page to contact us directly. You could also use [**StackOverflow**](https://stackoverflow.com/questions/tagged/ruby-on-rails+exceptionhandler)...
+---
 
- - ⚠️ [**Issues**](https://github.com/richpeck/exception_handler/issues) ⚠️
- - 🚩 [**StackOverflow**](https://stackoverflow.com/questions/tagged/ruby-on-rails+exceptionhandler) 🚩
- - ✉️ [**Email**](mailto:rpeck@frontlineutilities.co.uk) ✉️
- - ✏️ [**Medium**](https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677) ✏️
- - 🎥 [**YouTube**](https://www.youtube.com/channel/UC247lm76ECX1aSvVuhXxe6g) 🎥 ↴
+<div>
+  <p>You're welcome to contact me directly at <u><a href="mailto:rpeck@frontlineutilities.co.uk"></a><a href="mailto:rpeck@frontlineutilities.co.uk" ref="nofollow">rpeck@frontlineutilities.co.uk</a></u>.</p>
+  <p>Alternatively, you may wish to post on our <u><a href="https://github.com/richpeck/exception_handler/issues">GitHub Issues</a></u>, or <u><a href="https://stackoverflow.com/questions/tagged/ruby-on-rails+exceptionhandler" rel="nofollow">StackOverflow</a></u>.</p>
+  <p>--</p>
+  <p><a href="https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677" rel="nofollow"><img src="readme/medium.png" target="_blank" alt="Medium" style="max-width:100%;"></a></p>
+</div>
 
+<!-- Sep -->
 <p align="center">
-  <a href="https://www.youtube.com/channel/UC247lm76ECX1aSvVuhXxe6g"><img src="./readme/youtube.png" /></a>
+  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
 </p>
 
 <!-- Changelog -->
 <div id="changelog">
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>
-  <h3>⭐ Changelog ⭐</h3>
-  <p align="center"><img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" /></p>   
+  <h4>⭐ Changelog</h4>
 </div>
 
-The most important thing to appreciate is...
-
-<p align="center"><b>➡️ <code><a href="https://www.rubygems.org/gems/exception_handler">ExceptionHandler</a></code> is designed to provide <strong><A href="https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677">custom error pages</a></strong> for Ruby on Rails. ⬅️</b></p>
-
-<p>If you're looking at adding <em><b>extra</b></em> functionality (such as a debugger), you'll probably be better looking at the likes of <code><a href="https://rubygems.org/gems/better_errors">better_errors</a></code> or <code><a href="https://rubygems.org/gems/gaffe">gaffe</a></code>. Whilst we'll certainly look at adding - or integrating - other features (if they're requested), our core intention has always been to provide an exception handling stack that was both simple and customizable.</p>
-
---
-
-What we've built so far...
+---
 
-### 👻 [1.0.0.0](https://github.com/richpeck/exception_handler/releases/tag/v1.0.0.0)
+[**1.0.0.0**](https://github.com/richpeck/exception_handler/releases/tag/v1.0.0.0)
   - [ ] TBA
 
-### 🏹 [0.8.0.0](https://github.com/richpeck/exception_handler/releases/tag/v0.8.0.0)
+[**0.8.0.0**](https://github.com/richpeck/exception_handler/releases/tag/v0.8.0.0)
  - [x] [README](https://github.com/richpeck/exception_handler/issues/52) (focus on utility)
  - [x] Introduction of `4xx`,`5xx`,`:all` for layouts config
  - [x] Changed `layouts` to `exceptions` in config    
@@ -514,20 +540,19 @@ What we've built so far...
  - [x] Streamlined migration
  - [x] Updated model
 
-### 👽 [0.7.7.0](https://github.com/richpeck/exception_handler/releases/tag/v0.7.7.0)
+[**0.7.7.0**](https://github.com/richpeck/exception_handler/releases/tag/v0.7.7.0)
  - [x] [HTTP status layouts](#layouts)
 
-### ⚡ 0.7.0.0
+**0.7.0.0**
  - [x] Wildcard mime types
  - [x] [Custom exceptions](#custom_exceptions)
  - [x] Test suite integration
- - [x] [Email](#email)
  - [x] [Model backend](#database)
  - [x] Sprockets 4+
  - [x] New layout
  - [x] Readme / wiki overhaul
 
-### Ⓜ️ 0.6.5.0
+**0.6.5.0**
  - [x] Streamlined interface
  - [x] ActiveRecord / Middleware overhaul
  - [x] Supports Sprockets 4+ ([`manifest.js`](http://eileencodes.com/posts/the-sprockets-4-manifest/))
@@ -535,7 +560,7 @@ What we've built so far...
  - [x] Asset overhaul & improvement
  - [x] Removed dependencies
 
-### ✔️ 0.5.0.0
+**0.5.0.0**
  - [x] Locales
  - [x] Email notifications
  - [x] Full test suite
@@ -546,42 +571,41 @@ What we've built so far...
  - [x] Rails asset management improvement
  - [x] Reduced gem file size
 
-### ⭕ 0.4.7.0
+**0.4.7.0**
  - [x] New config system
  - [x] Fixed controller layout issues
  - [x] Streamlined middleware
  - [x] New layout & interface
 
-<!-- Sep -->
-<p align="center">
-  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
-</p>
+ <!-- Sep -->
+ <p align="center">
+   <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+ </p>
 
-[![404 + 500 Errors][banner]][rubygems]
+ [![404 + 500 Errors][banner]][rubygems]
 
-<p align="center">
-  <strong><a href="https://rubygems.org/gems/exception_handler"><code>ExceptionHandler</code></a> is now the • LEADING • custom error pages gem for Rails 4 & 5...</strong>
-  <br />
-  No other gem is as simple or effective at providing branded exception pages in production...
-</p>
+ <p align="center">
+   <strong><a href="https://rubygems.org/gems/exception_handler"><code>ExceptionHandler</code></a> provides custom error pages gem for Rails 5+</strong>
+   <br />
+   No other gem is as simple or effective at providing branded exception pages in production
+ </p>
 
-<p align="center">
-  <a href="http://badge.fury.io/rb/exception_handler"><img src="https://badge.fury.io/rb/exception_handler.svg" align="absmiddle"></a>
-  <a href="http://rubygems.org/gems/exception_handler"><img src="http://ruby-gem-downloads-badge.herokuapp.com/exception_handler/0.5.1?type=total&color=brightgreen" align="absmiddle" /></a>
-  <a href="https://codeclimate.com/github/richpeck/exception_handler"><img src="https://codeclimate.com/github/richpeck/exception_handler/badges/gpa.svg" align="absmiddle"/></a>
-  <a href="https://gemnasium.com/richpeck/exception_handler"><img src="https://gemnasium.com/richpeck/exception_handler.svg" align="absmiddle"></a>
-  <a href='https://coveralls.io/github/richpeck/exception_handler?branch=master'><img src='https://coveralls.io/repos/github/richpeck/exception_handler/badge.svg?branch=master' alt='Coverage Status' align="absmiddle" /></a>
-  <a href="https://travis-ci.org/richpeck/exception_handler"><img src="https://travis-ci.org/richpeck/exception_handler.svg?branch=master" align="absmiddle"></a>
-</p>
+ <p align="center">
+   <a href="http://badge.fury.io/rb/exception_handler"><img src="https://badge.fury.io/rb/exception_handler.svg" align="absmiddle"></a>
+   <a href="http://rubygems.org/gems/exception_handler"><img src="http://ruby-gem-downloads-badge.herokuapp.com/exception_handler/0.5.1?type=total&color=brightgreen" align="absmiddle" /></a>
+   <a href="https://codeclimate.com/github/richpeck/exception_handler"><img src="https://codeclimate.com/github/richpeck/exception_handler/badges/gpa.svg" align="absmiddle"/></a>
+   <a href='https://coveralls.io/github/richpeck/exception_handler?branch=master'><img src='https://coveralls.io/repos/github/richpeck/exception_handler/badge.svg?branch=master' alt='Coverage Status' align="absmiddle" /></a>
+   <a href="https://travis-ci.org/richpeck/exception_handler"><img src="https://travis-ci.org/richpeck/exception_handler.svg?branch=master" align="absmiddle"></a>
+ </p>
 
-<p align="center">
-  <strong>➡️ <a href="https://rubygems.org/gems/exception_handler">Download & Info</a> ⬅️ </strong>
-</p>
+ <p align="center">
+   <strong>➡️ <a href="https://rubygems.org/gems/exception_handler">Download & Info</a> ⬅️</strong>
+ </p>
 
-<!-- Sep -->
-<p align="center">
-  <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
-</p>
+ <!-- Sep -->
+ <p align="center">
+   <img src="https://cdn-images-1.medium.com/max/800/1*CKyKxRXLovcrUOB-s8_jCw.png" width="100%" />
+ </p>
 
 :copyright: <a href="http://www.fl.co.uk" align="absmiddle" ><img src="readme/fl.jpg" height="22" align="absmiddle" /></a> <a href="http://stackoverflow.com/users/1143732/richard-peck?tab=profile" align="absmiddle" ><img src="https://avatars0.githubusercontent.com/u/1104431" height="22" align="absmiddle" /></a> <a href="https://github.com/joehilton" align="absmiddle" ><img src="https://avatars2.githubusercontent.com/u/5063592?s=460&v=4" height="22" align="absmiddle" /></a> <a href="https://github.com/toymachiner62" align="absmiddle" ><img src="https://avatars3.githubusercontent.com/u/485782" height="22" align="absmiddle" /></a> <a href="https://github.com/andrewclink" align="absmiddle" ><img src="https://avatars0.githubusercontent.com/u/688916" height="22" align="absmiddle" /></a> <a href="https://github.com/Startouf" align="absmiddle" ><img src="https://avatars2.githubusercontent.com/u/7388889" height="22" align="absmiddle" /></a> <a href="https://github.com/Tonkonozhenko" align="absmiddle" ><img src="https://avatars0.githubusercontent.com/u/1307646" height="22" align="absmiddle" /></a> <a href="https://github.com/mabako" align="absmiddle" ><img src="https://avatars3.githubusercontent.com/u/125113" height="22" align="absmiddle" /></a> <a href="https://github.com/frankzhao" align="absmiddle" ><img src="https://avatars3.githubusercontent.com/u/555499" height="22" align="absmiddle" /></a>
 
@@ -594,43 +618,10 @@ What we've built so far...
 <!-- Images   https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#images -->
 
 <!-- Images -->
-[dev_mode]:         readme/dev_mode.jpg
-[dev_img]:          readme/dev.png
-[layouts_img]:      readme/layouts.jpg
-[layout_img]:       readme/layout.png
-[view_img]:         readme/view.jpg
-[http_codes]:       readme/http_codes.png
-[config]:           readme/config.jpg
-[config.action_dispatch.rescue_responses]: readme/config.action_dispatch.rescue_responses.jpg
-[banner]:           readme/banner.jpg
-[gem]:              readme/gem.jpg
-[gemfile]:          readme/gemfile.jpg
-[middleware]:       readme/middleware.jpg
-[exceptions_app]:   readme/exceptions_app.jpg
-[view]:             readme/titles/view.jpg
-[dev]:              readme/titles/dev.jpg
-[db]:               readme/titles/db.png
-[support]:          readme/titles/support.png "Support"
-[changelog]:        readme/titles/changelog.png "Changelog"
-[contribution]:     readme/titles/contributions.png "Contributions"
-[fl]:               readme/fl.jpg "Frontline Utilities LTD"
-[profile]:          https://avatars0.githubusercontent.com/u/1104431 "R Peck"
+[banner]:readme/banner.jpg
 
 <!-- Links -->
-[better_errors]: https://github.com/charliesome/better_errors
-[layout]: app/views/layouts/exception.html.erb
-[status_codes]: http://guides.rubyonrails.org/layouts_and_rendering.html#the-status-option
-[stackoverflow]: http://stackoverflow.com/questions/ask?tags=ruby-on-rails+exception-handler
-[rescue_responses]: http://guides.rubyonrails.org/configuring.html#configuring-action-dispatch
-[latest]: https://github.com/richpeck/exception_handler/releases/latest
-[show_exception]: https://github.com/rails/rails/blob/4-0-stable/actionpack/lib/action_dispatch/middleware/show_exceptions.rb
-[exception_app]: http://guides.rubyonrails.org/configuring.html#rails-general-configuration
 [rubygems]: http://rubygems.org/gems/exception_handler
-[frontlineutilities.co.uk]: http://www.frontlineutilities.co.uk
-[stackoverflow.com]: http://stackoverflow.com/users/1143732/richard-peck?tab=profile
-[fork]: #fork-destination-box
-[pull]:  http://github.com/richpeck/exception_handler/pulls
-[issues]: http://github.com/richpeck/exception_handler/issues
 
 [10x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#1xx_Informational_responses
 [20x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#2xx_Success
@@ -638,5 +629,15 @@ What we've built so far...
 [40x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors
 [50x]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_errors
 
+<!-- Local Links -->
+[db]: #db
+[email]: #email
+[dev]: #dev
+[layouts]: #layouts
+[locales]: #locales
+[configuration]: #configuration
+[generators]: #generators
+[custom-exceptions]: #custom-exceptions
+
 <!-- ################################### -->
 <!-- ################################### -->