This means that the current `.Site` and ´.Hugo` is available as a globals, so you can do `site.IsServer`, `hugo.Version` etc.
Fixes#5470Fixes#5467Fixes#5503
The advice in this page is actually the opposite. Relative URLs output the wrong URL for theme assets on the Hugo website.
See relevant advice in the repository's [README](https://github.com/gohugoio/hugoThemes#common-permalink-issues)
I hadn't noticed this page (if I had noticed I would have sent a PR earlier because the advice offered here is plain wrong).
The reason I am merging this PR right away is due to [this](https://github.com/gohugoio/hugoThemes/issues/504#issuecomment-443253163) comment by a confused theme author.
If you feel that this could be improved feel free to reword and amend as you see fit but the bottom line is that for themes that are going to be published on Hugo Themes authors should create absolute paths in their templates.
cc: @bep @digitalcraftsman @kaushalmodi
When the page parser was rewritten in 0.51, this was interpreted literally, but commented out front matter is used in the wild to "hide it from GitHub", e.g:
```
<!--
+++
title = "hello"
+++
-->
```
Fixes#5478
An inline shortcode's name must end with `.inline`, all lowercase.
E.g.:
```bash
{{< time.inline >}}{{ now }}{{< /time.inline >}}
```
The above will print the current date and time.
Note that an inline shortcode's inner content is parsed and executed as a Go text template with the same context as a regular shortcode template.
This means that the current page can be accessed via `.Page.Title` etc. This also means that there are no concept of "nested inline shortcodes".
The same inline shortcode can be reused later in the same content file, with different params if needed, using the self-closing syntax:
```
{{< time.inline />}}
```
Fixes#4011
PurgeCSS removes unused CSS from the output. This PR only uses PurgeCSS on the base utility classes to avoid unexpected issues where JS or content-based classes get removed.
* Swap src for assets directory
Assets directory is the default for Hugo Pipes
* Use "Typefaces" package
This method is cleaner because we can pull in our fonts with a require statement https://github.com/KyleAMathews/typefaces
* Use Hugo Pipes method of calling resources
* Update dependencies
* [wip] Revamp Webpack
* Tweak Webpack for Tachyons
* Use simple build scripts
* Update dependencies
* Fix content that referenced files that don't exist
* Add all scripts
* Improve styles/js preload and cache
* Add to whitelist
* Add fonts to headers for preload
* Move preloads to header file
* Update styles
* Improve manifest usage
The manifest partial was in the site but not included in head
* Update readme
* Remove extra check on asset resources
* Call assets directly in header file
In the newly consolidated file cache implementation, we forgot that we also look in the theme(s) for assets (SCSS transformations etc.), which is not good for Netlify and the demo sites.
Fixes#5460
Bjørn Erik Pedersen