The "Completion of the Hugo Quick Start" is an assumption, and there you install a hugo theme via git submodule, than it's necessary to add the rows I have added.
The < and > characters in the URL weren't getting escaped, instead acting as if they were HTML elements. This meant the URL was displayed as https://gitlab.com///pipelines, instead of https://gitlab.com/<YourUsername>/<your-hugo-site>/pipelines.
The referenced image (`publysher/hugo`) is outdated, leading to the following error: `Current theme does not support Hugo version 0.22.1. Minimum version required is 0.24.1`. The current version of hugo is 0.26. I forked the publysher repo, bumped it to 0.26 and pushed it to my Docker hub (monachus is my username on Docker Hub).
I'm an engineer at Rancher Labs and an active user of Gitlab. I've enabled notifications for Hugo releases, so as they come out, I'll tag and release an updated Docker image. I'm happy to be the target repo for this piece of documentation.
- changes the link to asciidoc from the python tool to the ruby and .js processor.
Asciidoctor extends the language much more than the python implementation, and if folks click on the python link they will likely run into processor issues when Asciidoctor attempts to process the .adoc files.
f887bd7b Add script to pull theme changes
e89bbb2f Update README
78155dec Merge commit '9301947b25099dd402065104b340b1a480906a74' as 'themes/gohugoioTheme'
9301947b Squashed 'themes/gohugoioTheme/' content from commit 7dd8a302
e7557a34 Remove gohugoioTheme submodule
a78bbe22 Add link to Go issue
31d1ef40 Add example for taxonomy terms with metadata
da978cc7 Fix links in Blackfriday extension documentation
950ad115 Fix reference to Blackfriday Extensions section
12d1d026 Add documentation for Blackfriday Extensions
8c2b8fb5 Fix explaination for uglyURLs config option
378aded7 Use community repository for Arch Linux installation guide
56455e7e Improve 0.26 release notes
be7db03a netlify: Build with the new 0.26
d430b2d3 Bump version to 0.26
61adaca0 releaser: Prepare repository for 0.27-DEV
abef29a6 releaser: Add release notes to /docs for release of 0.26
5937fe41 releaser: Bump versions for release of 0.26
033752f1 Merge commit 'e81208265bb3cdb7606d051a23d83aeebcb7d34d'
bec2bd12 Make the title case style guide configurable
f1739a44 Merge commit '50ec65fbe1a48475d3320775dab2c47389c02114'
a1aac0e5 helpers: Add support for French Guillemets
b8dc1592 doc: Merge commit '2c0d1ccdcd95de0bddeb39dca2e4d08f0d8056d7'
7b3e31b8 Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943'
a37e7201 Bump versions to 0.26-DEV
git-subtree-dir: docs
git-subtree-split: f887bd7b4e3e7c7e76cd63951e5b0d37d8fe0ac7
There is no information on how you can add custom metadata to your
taxonomy terms. What you need to do is add front matter data in the file
/content/<TAXONOMY>/<TERM>/_index.md
Then you will be able to access the taxonomy term as a page in a
taxonomy terms template.
That is why I added instructions in /content-management/taxonomies on
how to add custom metadata. And in /templates/taxonomy-templates/ I
added an example on how you can display that metadata in the taxonomy
terms template.
I think that would be enough to guide the user in how to add custom
metadata to their taxonomy terms.
