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
This allows for "cache per Hugo project", making `hugo --gc` work as expected, even if you have several Hugo projects running on the same PC.
See #5439
This allows for "cache per Hugo project", making `hugo --gc` work as expected, even if you have several Hugo projects running on the same PC.
See #5439
Cameron Moore