Using the `{{ .URL }}` token results in a warning:

    WARN 2019/10/13 15:12:12 Page's .URL is deprecated and will be removed in a
    future release. Use .Permalink or .RelPermalink. If what you want is the
    front matter URL value, use .Params.url.

Steps to reproduce
==================

Follow along with the Quick Start guide at
https://gohugo.io/getting-started/quick-start/

Running `hugo server -D` emits a warning that `.URL` is deprecated.

* Adds an author to blog posts.

See #113

* Feedback #209, fully contain author in {{with}}

Co-authored-by: Bud Parr <budparr@gmail.com>

* Fixes #180.

* Trying to fix .RSSLink deprecation message.

These have been deprecated by Google

* feat: add commento block

Signed-off-by: Kirill K <kovalev.kirill.a@gmail.com>

* fix: use params section in config example

Signed-off-by: Kirill K <kovalev.kirill.a@gmail.com>

* fix: use defer to execute script after page load

Signed-off-by: Kirill K <kovalev.kirill.a@gmail.com>

* Create fr.toml

French translation

* Social link to "mastodon" added

* Some statics partials are cached, to optimise rendering

* Caching moved so that the i18n menu will work as expected. Refs #35

In English, the translation that is supposed to be shown on top of the table of contents looks like this:

```toml
[whatsInThis]
other = "What's in this {{.Type }}"
```

When it is invoked, there are two mistakes: `{{ i18n "whatsInThis" humanize .Type }}`.

The first mistake is that you cannot call `humanize` in this context. The more severe one is that if you remove `humanize` it will pass the `.Type` directly to the i18n and that tries to extract `.Type` from it.

* Create fr.toml

French translation

* Social link to "mastodon" added

* Some statics partials are cached, to optimise rendering

* Create fr.toml

French translation

* Social link to "mastodon" added

* add initial translation

* readd _copy params to templates

I updated the documentaiton as well as changed the contact page in the
exampleSite to use this feature as a demo.

Fixes #130

Fixes #149

Keep in spirit with https://medium.com/@svinkle/why-let-someone-know-when-a-link-opens-a-new-window-8699d20ed3b1 but address issue #145

* Open social media in new tab and add Medium

svg file pulled from Medium post on their logos
and brand guides dated Aug 22, 2017

https://medium.design/logos-and-brand-guidelines-f1a01a733592

* Add new-window accessibility icon for social media icons

Visible on-hover of link-transition class, this PR also
adds a description to the social media icons indicating that
they will open in a new window.

This way, users will be able to see and hear (via a reader)
when a tab will open in a new window.

This approach is based on the one outlined here:
https://medium.com/@svinkle/why-let-someone-know-when-a-link-opens-a-new-window-8699d20ed3b1

(it's already on the header). Fixes #135

via PR #134 @looer

Added config variable so this doesn't show up

Show "reading time" and "word count" but only if one of the following are true:
1) A global config `params` value is set `show_reading_time = true`
 2) A section front matter value is set `show_reading_time = true`
3) A page front matter value is set `show_reading_time = true`

Signed-off-by: Daniele Ricci <daniele@casaricci.it>

Gitlab is a popular Git repository manager using an opensource license.
This commit adds the Gitlab social icon.

This applies the flexbox directive `justify-between` to the nav items, not the icons themselves.

Fixes #127

Fixes #115

See #97

* Add custom_css parameter.

* Copy documentation from hugo-octopress.

Fixes #97

* Add assets-webpack-plugin

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

* Add generated Webpack Assets file

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

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

* Update stylesheet

Note sure why this was updated

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

* Add CSS file from generated file

Replaces hardcoded path

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