| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
For pages with translations, add links with hreflang attributes to the
default sitemap template. This helps Google to show the correct
language page in its search results. The syntax used is based on
Google's example at [1].
Also update the sitemap template docs to reflect the changes in the
default template.
[1]
https://support.google.com/webmasters/answer/2620865?hl=en&topic=2370587&ctx=topic
Fixes #2569
|
|
|
|
|
|
|
|
|
|
This reverts commit 8ac1fcd0ceb5d2e55e16a9caa7f6f0d646a07668.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #3301
Fixes #3302
|
|
Add "Getting started with Hugo and the plain-blog theme, on NearlyFreeSpeech.Net"
|
|
This commit also adds a new command, docshelper, with some utility funcs that adds a JSON datafiles to /docs/data that would be a pain to create and maintain by hand.
Fixes #3242
|
|
Use `--enableGitInfo` when publishing.
This gives a much better out-of-the-box editing experience.
|
|
Additional information about the Pygments dependency in the "installing from source" chapter.
|
|
|
|
|
|
Fixes #3264
|
|
Fix #3200
|
|
|
|
|
|
Livefyre.com is down.
Livefyre was integrated into Adobe's offering.
The product is now called Adobe Experience Manager Livefyre.
Wikipedia points to web.livefyre.com which redirects to the link I provided in the commit.
|
|
|
|
This isn't meant to be the final useer docs on this feature!
|
|
/cc @rdwatters
|
|
This page was a real chore chore on the POC. In the event that a new doc site won't be approved by v20, this will at least clean up the broken links I found during my audit. I would like to eventually create this as a [data file](https://github.com/spf13/hugo/pull/2508#commitcomment-18705617) since md tables get unwieldy pretty quickly.
|
|
limitted → limited
|
|
|
|
Per forum:
https://discuss.gohugo.io/t/site-recent-deprecated-or-removed/5851/2
|
|
|
|
|
|
Add vendoring and make targets. Require Go 1.8+ and remove mention of
GOPATH (just assume $HOME/go).
Due to time contraints, the contributing tutorial was only slightly
updated to make obvious corrections.
Fixes #3153
|
|
|
|
Backported from https://hugodocs.info/getting-started/installing/
with added mention for Fedora and Red Hat.
|
|
Backported from https://hugodocs.info/getting-started/installing/
Fixes #3143
|
|
|
|
|
|
Accept JSON frontmatter without leading "{\n" so that one line
frontmatters such as `{"param":"paramvalue"}` no longer silently render
empty html.
|
|
|
|
|
|
Themes is currently not included in the description that follows `tree -a` even
though it is autogenerated for you by `new site`.
|
|
|
|
|
|
Previously this was left empty, but it is very handy to have a list
of term pages for a given taxonomy. This list can now be paginated
like other page lists. It makes it possible to render summary
content from each terms index page for instance. It also makes it
possible to sort the term pages in the same way that other page
lists can be sorted. An RSS feed is now generated for
KindTaxonomyTerm pages as well.
This also fixes a bug in HugoSites.createMissingPages. Previously
it would only check for existing KindTaxonomyTerm pages if the
taxonomy had any terms defined. So for a taxonomy with no terms
but a taxonomy terms page it would generate a second empty terms
page.
|
|
|
