We look for .Params.featured_image
If found > we use that as URL
If we find a Page resource matching the value of the above, we use its .RelPermalink
If none of the above we look for an resource whose filepath contains `featured` or `cover` and use its .RelPermalink if found
Fixes#233Fixes#407
Previously the default date format (`January 2, 2006` ) was used for
blog and single page date visualizations.
The new parameter `date_format` can be used to override this format.
This allows the visualization of localized dates or a changed precision
(down to the minute or up to the month or year of publication).
Co-authored-by: Regis Philibert <login@regisphilibert.com>
* Add support for auto-detection of featured images.
* Rename Partial, Add Documentation
Renamed the partial to func/GetFeaturedImage.html.
Additionally added more documentation in the partial to explain how it
worked, and what values were returned.
Co-authored-by: Sean Zimmermann <sz2243@columbia.edu>
The way relURL was used meant that one needed to preface the custom_css
entries with a slash, or the href would be incorrectly set to
subdircss/mycss.css rather than subdir/css/mycss.css, in the case of
a baseURL in a subdir.
Co-authored-by: Nick White <git@njw.name>
* Use | relLangURL for the base urlº
This way, when you click on the header it maintains you in the same language you previously selected.
* Use .Site.Home.RelPermalink as proposed by @regisphilibert
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.
* 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.
* 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
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`
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#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.
* 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
