hugo/.gitignore

/hugo
docs/public*
/.idea
.vscode/*
hugo.exe
*.test
*.prof
nohup.out
cover.out
*.swp
*.swo
.DS_Store
*~
vendor/*/
*.bench
*.debug
coverage*.out

dock.sh

GoBuilds
dist

hugolib/hugo_stats.json
resources/sunset.jpg

vendor
Add tpl/site and tpl/hugo This means that the current `.Site` and ´.Hugo` is available as a globals, so you can do `site.IsServer`, `hugo.Version` etc. Fixes #5470 Fixes #5467 Fixes #5503 2018-11-26 04:11:22 -05:00			`/hugo`
Remove ^M from file to make line-endings consistent 2017-07-18 12:06:50 -04:00			`docs/public*`
			`/.idea`
resources: Add timeout to the HTTP request in Get Workaround for https://github.com/golang/go/issues/49366 2021-12-02 08:13:24 -05:00			`.vscode/*`
Remove ^M from file to make line-endings consistent 2017-07-18 12:06:50 -04:00			`hugo.exe`
			`*.test`
			`*.prof`
			`nohup.out`
			`cover.out`
			`*.swp`
			`*.swo`
			`.DS_Store`
			`*~`
Add vendoring with govendor 2016-09-18 18:10:10 -04:00			`vendor/*/`
makefile: Add test-cover-html 2016-11-27 17:21:10 -05:00			`*.bench`
hugolib: Remove superflous debug file 2018-03-12 18:35:38 -04:00			`*.debug`
Add GoBuilds to .gitignore 2016-12-19 11:12:11 -05:00			`coverage*.out`

Add Hugo Piper with SCSS support and much more Before this commit, you would have to use page bundles to do image processing etc. in Hugo. This commit adds * A new `/assets` top-level project or theme dir (configurable via `assetDir`) * A new template func, `resources.Get` which can be used to "get a resource" that can be further processed. This means that you can now do this in your templates (or shortcodes): ```bash {{ $sunset := (resources.Get "images/sunset.jpg").Fill "300x200" }} ``` This also adds a new `extended` build tag that enables powerful SCSS/SASS support with source maps. To compile this from source, you will also need a C compiler installed: ``` HUGO_BUILD_TAGS=extended mage install ``` Note that you can use output of the SCSS processing later in a non-SCSSS-enabled Hugo. The `SCSS` processor is a _Resource transformation step_ and it can be chained with the many others in a pipeline: ```bash {{ $css := resources.Get "styles.scss" \| resources.ToCSS \| resources.PostCSS \| resources.Minify \| resources.Fingerprint }} <link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen"> ``` The transformation funcs above have aliases, so it can be shortened to: ```bash {{ $css := resources.Get "styles.scss" \| toCSS \| postCSS \| minify \| fingerprint }} <link rel="stylesheet" href="{{ $styles.RelPermalink }}" integrity="{{ $styles.Data.Digest }}" media="screen"> ``` A quick tip would be to avoid the fingerprinting part, and possibly also the not-superfast `postCSS` when you're doing development, as it allows Hugo to be smarter about the rebuilding. Documentation will follow, but have a look at the demo repo in https://github.com/bep/hugo-sass-test New functions to create `Resource` objects: * `resources.Get` (see above) * `resources.FromString`: Create a Resource from a string. New `Resource` transformation funcs: * `resources.ToCSS`: Compile `SCSS` or `SASS` into `CSS`. * `resources.PostCSS`: Process your CSS with PostCSS. Config file support (project or theme or passed as an option). * `resources.Minify`: Currently supports `css`, `js`, `json`, `html`, `svg`, `xml`. * `resources.Fingerprint`: Creates a fingerprinted version of the given Resource with Subresource Integrity.. * `resources.Concat`: Concatenates a list of Resource objects. Think of this as a poor man's bundler. * `resources.ExecuteAsTemplate`: Parses and executes the given Resource and data context (e.g. .Site) as a Go template. Fixes #4381 Fixes #4903 Fixes #4858 2018-02-20 04:02:14 -05:00			`dock.sh`

Automate the Hugo release process This commit adds a work flow aroung GoReleaser to get the Hugo release process automated and more uniform: * It can be run fully automated or in two steps to allow for manual edits of the relase notes. * It supports both patch and full releases. * It fetches author, issue, repo info. etc. for the release notes from GitHub. * The file names produced are mainly the same as before, but we no use tar.gz as archive for all Unix versions. * There isn't a fully automated CI setup in place yet, but the release tag is marked in the commit message with "[ci deploy]" Fixes #3358 2017-04-13 10:59:05 -04:00			`GoBuilds`
			`dist`
Add GOPATH Hugo building tip 2018-10-09 05:09:00 -04:00
Collect HTML elements during the build to use in PurgeCSS etc. The main use case for this is to use with resources.PostProcess and resources.PostCSS with purgecss. You would normally set it up to extract keywords from your templates, doing it from the full /public takes forever for bigger sites. Doing the template thing misses dynamically created class names etc., and it's hard/impossible to set up in when using themes. You can enable this in your site config: ```toml [build] writeStats = true ``` It will then write a `hugo_stats.json` file to the project root as part of the build. If you're only using this for the production build, you should consider putting it below `config/production`. You can then set it up with PostCSS like this: ```js const purgecss = require('@fullhuman/postcss-purgecss')({ content: [ './hugo_stats.json' ], defaultExtractor: (content) => { let els = JSON.parse(content).htmlElements; return els.tags.concat(els.classes, els.ids); } }); module.exports = { plugins: [ require('tailwindcss'), require('autoprefixer'), ...(process.env.HUGO_ENVIRONMENT === 'production' ? [ purgecss ] : []) ] }; ``` Fixes #6999 2020-03-03 06:25:03 -05:00			`hugolib/hugo_stats.json`
resources: Fix test on Windows 2019-07-25 10:54:05 -04:00			`resources/sunset.jpg`
Add GOPATH Hugo building tip 2018-10-09 05:09:00 -04:00
Create lightweight forks of text/template and html/template This commit also removes support for Ace and Amber templates. Updates #6594 2019-12-10 02:02:15 -05:00			`vendor`