Replaces hardcoded path

Signed-off-by: budparr <budparr@gmail.com>

This file is generated by Webpack and writes the names of our hashed assets

Signed-off-by: budparr <budparr@gmail.com>

2.0 Enhancements

- Improve template structure
- Fixed issue where flexbox was configured improperly and the side column expanded with longer content.
- No longer assume that posts are called "post"
- Simplify tag handling
- Improve related posts handling
- Support native Table of contents (if declared in params)
- Add DISQUS commenting (if disqusShortname added to config)
- Uses Hugo's Related content feature 
- Add asset hashing to Webpack for performance

Let's say your `.Site.Title` is "My Website". The code grabs `.Site.Title`, and then then checks to see if there's a `.Title`. When you're on the homepage, `.Title` is equivalent to `.Site.Title`, so that the browser bar will read:

> My Website | My Website

If we qualify `.Title` by confining to the `.Params` namespace, then the site title isn't duplicated:

```<title>{{ block "title" . }}{{ .Site.Title }} {{ with .Params.Title }} | {{ . }}{{ end }}{{ end }}</title>```

> My Website

But it still picks up `.Title` from posts and pages, where a content title exists in front matter:

> My Website | About Me

Fixes #70

* Parmeterize number of recent posts in index.html

* Replace .Site.Params.recent_posts_number with $.Param "recent_posts_number" in index.html

Fixes #50

Hugo's `.Summary` did not behave as I expected it to, not stripping out
HTML, so I removed the anchor block from around the posts and moved the
links to the image, title and a read more button.

* Adding support for favicon

* Fixing html tag

* add linkedin

* update github svg to fix spacing

* add colors from brandcolors.net

* add github social link

* add github css

* fix css error breaking rollover

Fixes #43

* using Hero sample image in the theme's /static folder
* fall back to site config
* fall back to hard coded default if none set in page or site params

This helps with theme portability.

Also use Site.RegularPages in its default sort, as this is probably what most people want.