a042b67b5 Update installation instructions for Fedora, CentOS, Red Hat e99dcb0b5 Document `:sections` placeholder for permalinks f33c88a27 Fix and clarify documentation about Blackfriday extensions (mask) 5cab109c2 Add .Page.File documentation 62df7bb80 Add .Page.CurrentSection and .Page.Sections documentation 60b4414de Add .Page.Dir documentation 22038d1a8 shortcode-templates.md: Update year example 850d5ca41 Add note about theme versions in hosting-on-netlify.md 0509b8055 Update permalink example URL c68d61d3a Mention the available 'width' argument in 'figure' shortcode ed83b483a Update Nanobox deployment tutorial a7422f35d shortcode-templates.md: Remove stray period af2905fe4 Fix order of releases in news section 19d3ea064 Bump to 0.30.2 bbfa10343 Merge branch 'next' 36ed7cbe4 releaser: Prepare repository for 0.31-DEV f689770f6 releaser: Add release notes to /docs for release of 0.30.2 0045e712a releaser: Bump versions for release of 0.30.2 a9efc3bbd Add slug to 0.30.1 relnotes 9cf47a4a1 Release 0.30.1 1fa0bb23d releaser: Prepare repository for 0.31-DEV 5582208b6 releaser: Add release notes to /docs for release of 0.30.1 09693d155 releaser: Bump versions for release of 0.30.1 58adf5d0d Merge commit '325009c3fd4ac90021897b7e3e025c14e70ce162' 4ef5dcb9b releaser: Prepare repository for 0.31-DEV 02938a788 releaser: Add release notes to /docs for release of 0.30.1 7cfd01fc6 releaser: Bump versions for release of 0.30.1 db3a68e24 Fix typo 95a5d8b46 Fix format of summaryLength in TOML example config 2ad649a92 Make terms in taxonomy examples more coherent 1fac1e662 Make a link specifically point to Pygments HTML Formatter docs 11ae6be03 Fix minor typos in v0.30 release notes git-subtree-dir: docs git-subtree-split: a042b67b5b8834ee8292849708cba724f5d6644e
5.1 KiB
title | linktitle | description | date | publishdate | lastmod | categories | keywords | authors | menu | weight | sections_weight | draft | aliases | wip | toc | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Add Your Hugo Theme to the Showcase | Themes | If you've built a Hugo theme and want to contribute back to the Hugo Community, add your theme to the Hugo Showcase. | 2017-02-01 | 2017-02-01 | 2017-02-27 |
|
|
|
|
30 | 30 | false |
|
true | true |
A collection of all themes created by the Hugo community, including screenshots and demos, can be found at https://themes.gohugo.io. Every theme in this list will automatically be added to the theme site. Theme updates aren't scheduled but usually happen at least once a week.
tl;dr
- Create your theme using
hugo new theme <THEMENAME>
; - Test your theme against https://github.com/spf13/HugoBasicExample *
- Add a
theme.toml
file to the root of the theme with all required metadata - Add a descriptive
README.md
to the root of the theme source - Add
/images/screenshot.png
and/images/tn.png
* If your theme doesn't fit into the Hugo Basic Example
site, we encourage theme authors to supply a self-contained Hugo site in /exampleSite
.
{{% note %}}
The folder name here---exampleSite
---is important, as this folder will be picked up and used by the script that generates the Hugo Theme Site. It mirrors the root directory of a Hugo website and allows you to add custom content, assets, and a config
file with preset values.
{{% /note %}}
See the Hugo Artist theme's exampleSite for a good example.
{{% note %}} Please make your example site's content is as neutral as possible. We hope this goes without saying. {{% /note %}}
Theme Requirements
In order to add your theme to the Hugo Themes Showcase, the following requirements need to be met:
theme.toml
with all required fields- Images for thumbnail and screenshot
- A good README file instructions for users
- Addition to the hugoThemes GitHub repository
Add Your Theme to the Repo
The easiest way to add your theme is to open up a new issue in the theme repository with a link to the theme's repository on GitHub.
Create a theme.toml
File
theme.toml
contains metadata about the theme and its creator and should be created automatically when running the hugo new theme
. The auto-generated file is provided here as well for easy downloading:
{{< code file="theme.toml" download="theme.toml" >}} name = "" license = "MIT" licenselink = "https://github.com///blob/master/LICENSE.md" description = "" homepage = "https://example.com/" tags = [] features = [] min_version = 0.19
[author] name = "" homepage = ""
If porting an existing theme
[original] name = "" homepage = "" repo = "" {{< /code >}}
The following fields are required:
name = "Hyde"
license = "MIT"
licenselink = "https://github.com/spf13/hyde/blob/master/LICENSE.md"
description = "An elegant open source and mobile first theme"
homepage = "http://siteforthistheme.com/"
tags = ["blog", "company"]
features = ["blog"]
min_version = 0.13
[author]
name = "spf13"
homepage = "http://spf13.com/"
# If porting an existing theme
[original]
author = "mdo"
homepage = "http://hyde.getpoole.com/"
repo = "https://www.github.com/mdo/hyde"
{{% note %}}
- This is different from the
theme.toml
file created byhugo new theme
in Hugo versions before v0.14. - Only
theme.toml
is accepted; ie. nottheme.yaml
andtheme.json
. {{% /note %}}
Images
Screenshots are used for previews in the Hugo Theme Gallery. Make sure that they have the right dimensions:
- Thumbnail should be 900px × 600px
- Screenshot should be 1500px × 1000px
- Media must be located in
- /images/screenshot.png
- /images/tn.png
Additional media may be provided in the same directory.
Create a README File
Your theme's README file should be written in markdown and saved at the root of your theme's directory structure. Your README.md
serves as
- Content for your theme's details page at https://themes.gohugo.io
- General information about the theme in your GitHub repository (i.e., it's usual purpose)
Example README.md
You can download the following README.md
as an outline:
{{< code file="README.md" download="README.md" >}}
Theme Title
Need input from @digitalcraftsman on what could be added to this file.
{{< /code >}}
{{% note "Screenshots in your README.md
"%}}
If you add screenshots to the README, please make use of absolute file paths instead of relative ones like /images/screenshot.png
. Relative paths work great on GitHub but they don't correspond to the directory structure of themes.gohugo.io. Therefore, browsers will not be able to display screenshots on the theme site under the given (relative) path.
{{% /note %}}