Supported platforms
```
facebook: "#"
twitter: "#"
github: "#"
gitlab: "#"
steam: "#"
instagram: "#"
youtube: "#"
pinterest: "#"
linkedin: "#"
reddit: "#"
flickr: "#"
deviantart: "#"
vk: "#"
mastodon: "#"
bandcamp: "#"
tumblr: "#"
medium: "#"
wikipedia: "#"
```
To be supported in future:
```
paypal: "#"
slack: "#"
twitch: "#"
stackoverflow: "#"
shutterstock: "#"
soundcloud: "#"
codepen: "#"
```
2. **Share** *(Type: Array | Accepts value: "facebook", "twitter", "linkedin", "whatsapp", "reddit", "email" | Optional | No default)*
Specify the name of social media platforms that you want your articles to be able to be shared on. You also need to set value in `position` parameter, for share icons to be displayed.
Example:
```yaml
social:
profiles:
facebook: "https://facebook.com/#myprofile"
twitter: "https://twitter.com/#myprofile"
github: "https://github.com/#myprofile"
gitlab: "https://gitlab.com/#myprofile"
share: ["facebook", "twitter", "linkedin", "telegram", "whatsapp", "reddit", "email"]
```
2. **Meta** *(Type: Map/Dict/Object | Accepts value: - | Required/Optional)*
1. **Author** *(Type: String | Accepts value: Text | Required | No default)*
It stores website-wide author(s). We won't be using `site.Authors` till it is finalised. See [here](https://github.com/gohugoio/hugo/issues/3088).
Example:
```yaml
author: "The Great Authors"
```
2. **Footer Message** *(Type: String | Accepts value: Text | Optional | No default)*
It is shown in footer above footer links.
Example:
```yaml
footerMessage: "Awesome footer message"
```
3. **Tagline** *(Type: String | Accepts value: Text | Required | No default)*
It is the tagline of the website/blog. It's displayed in website title, and on homepage.
Example:
```yaml
tagline: "A blog to satisfy you needs"
```
4. **Description** *(Type: String | Accepts value: Text | Required | No default)*
It is the description of website/blog and should include website/blog title (brand name) at least once, for great SEO benefits. Recommended character length: 50 to 160.
Example:
```yaml
description: "A really great description!"
```
5. **Content License** *(Type: String | Accepts value: Text | Required | No default)*
It is the license under which website/blog's content is distributed. It should be same as that specified in field 'copyright' above.
Example:
```yaml
contentLicense: "All rights reserved." # Another example: 'CC-BY-SA-3.0'
```
6. **Title Separator** *(Type: String | Accepts value: Text | Optional | Default: " | ")*
It is used in website/blog title, to separate (say) page title from website/blog title.
Example:
```yaml
titleSeparator: " | "
```
7. **Attribution** *(Type: String | Accepts value: enable/disable | Optional | Default: "enable")*
Allows to attribute Hugo team for awesome software and Softorage for great theme.
Example:
```yaml
attribution: "enable"
```
3. **Brand** *(Type: Map/Dict/Object | Accepts value: - | Highly Recommended)*
It stores brand related information. It contains:
1. **Name** *(Type: String | Accepts value: Text | Required | No default)*
It's the Brand's Name, usually just one/two word that is name of the brand.
2. **Logo - 500px** *(Type: String | Accepts value: URL | Required | No default)*
It's path (preferably relative path) to brand's logo with resolution 500px.
3. **Logo - 32px** *(Type: String | Accepts value: URL | Required | No default)*
It's path (preferably relative path) to brand's logo with resolution 32px. It will be shown on navbar as is.
4. **Color** *(Type: String | Accepts value: HEX/RGBA | Required | No default)*
It's the color to be shown on scroll for brand name on navbar.
5. **Navbar Config** *(Type: Array | Accepts value: "logo", "name" | Optional | Default: ["logo", "name"])*
It determines whether brand's logo and/or name should be visible on navbar.
Example:
```yaml
brand:
name: "ExampleBlog"
logo_500px: "/assets/favicon/android-chrome-512x512.png"
logo_32px: "/assets/favicon/favicon-32x32.png"
color: "#7d1fa5"
navbar: ["logo", "name"]
```
4. **Theme** *(Type: Map/Dict/Object | Accepts value: - | Optional)*
You can specify custom color pallet to form look for the website/blog of your own liking. It contains:
1. **Nav** *(Type: String | Accepts value: HEX/RGBA | Optional | Default: "#ffffff")*
It's navbar's background color.
2. **Antinav** *(Type: String | Accepts value: HEX/RGBA | Optional | Default: "#000000")*
It's a color in good contrast to `nav`.
3. **Mat** *(Type: String | Accepts value: HEX/RGBA | Optional | Default: "#f9f9f9")*
It's background color for cards (not of cards). It applies to the background on which cards are placed.
4. **Color-1** *(Type: String | Accepts value: HEX/RGBA | Optional | Default: "#7d1fa5")*
It's color-1 in the hero gradient. It is used throughout the theme.
5. **Color-2** *(Type: String | Accepts value: HEX/RGBA | Optional | Default: "#6d19fc")*
It's color-2 in the hero gradient. It is used throughout the theme.
6. **Borders** *(Type: String | Accepts value: rounded/square | Optional | Default: "rounded")*
Here, specify what kind of borders do you like for elements, like buttons.
Example:
```yaml
theme:
nav: "#ffffff"
antinav: "#000000"
mat: "#f9f9f9"
clr1: "#7d1fa5"
clr2: "#6d19fc"
borders: "rounded"
```
5. **Background Image** *(Type: Map/Dict/Object | Accepts value: - | Optional)*
1. **Landing Page** *(Type: String | Accepts value: URL | Optional | No default)*
It is path to background image for hero section on landing page. If specified, background image will be applied.
2. **Post** *(Type: String | Accepts value: enable/disable | Optional | Default: "enable")*
If enabled, image set in front-matter will be shown as background image for hero section of the post.
Example:
```yaml
backgImage:
landingPage: "/neven-krcmarek-V4EOZj7g1gw-unsplash.jpg"
post: "enable"
```
6. **Position** *(Type: Map/Dict/Object | Accepts value: - | Optional with caevets)*
It lets you customize *what* elements should be displayed and *where*. It contains:
1. **Social** *(Type: Map/Dict/Object | Accepts value: - | Optional)*
1. **Profiles** *(Type: String | Accepts value: footer/navbar | Optional | Default: "footer")*
It lets you customize where you want your social profiles to appear. You may use 'navbar' if number of items in main menu and social profiles are minimal, otherwise 'footer' is recommended.
2. **Share** *(Type: String | Accepts value: top/bottom | Optional | Default: "top")*
It lets you customize where you want your social sharing buttons to appear on a blog post.
2. **Menu on Navbar** *(Type: String | Accepts value: right/left | Optional | Default: "right")*
It lets you customize the position of main menu on navbar.
3. **Post's Meta** *(Type: Map/Dict/Object | Accepts value: - | Optional | No default)*
It lets you customize *which* elements from post's meta should be displayed, *where* and *how*.
It contains:
**readingTime** - **wordCount** - **author** - **lastUpdated** - **tags**
*(Type: Map/Dict/Object | Accepts value: - | Optional | No default)*
It lets you customize where (summary/content) you want to show a post's 'reading time', 'words count', 'author', 'last updated on', 'tags' and how (top/bottom).
```yaml
# For example,
position:
postMeta:
tags:
summary: "top"
content: "bottom"
# above code lets you show tags of your posts:
1. at the time when its 'summary' is being shown (for example, in the posts' list on landing page), at the top of the 'summary'.
2. at the time when its 'content' is being shown (for example, when a user visits the post itself), at the bottom of the 'content'.
# not including (say) 'readingTime' (or 'wordCount' or 'author' or 'lastUpdated' or'tags'), would simply omit 'readingTime' from appearing in 'summary' and 'content'.
# not includng only (say) 'summary' (or 'content') for (say) 'readingTime', would simply omit 'readingTime' from appearing in 'summary' (or 'content').
```
4. **Thumbnail** *(Type: String | Accepts value: right/left | Optional | Default: "left")*
Position of a post's image, when it appears as a thumbnail in a list (say) on landing page. Regardless of "right" or "left", it looks the same on mobile-view.
Example:
```yaml
position:
social:
profiles: "footer"
share: "bottom"
navbarMenu: "right"
postMeta:
readingTime:
summary: "top"
content: "top"
wordCount:
summary: "top"
content: "top"
author:
summary: "top"
content: "top"
lastUpdated:
summary: "top"
content: "top"
tags:
summary: "top"
content: "bottom" # default: "bottom"
thumbnail: "left"
```
7. **Fonts** *(Type: Map/Dict/Object | Accepts value: - | Optional )*
It lets you customize the fonts for various types of text elements, and in general too.
Let's see this customization property with an example:
```yaml
font:
general:
family: "Lato" # must match to a css font-family | default: "Lato"
#cdnLink: "" # a link tag for font other than Lato and Roboto | recommended
heading:
list: ["h1"] # accepts array of values: "h1", "h2", "h3", "h4", "h5", "h6" | default: ["h1"]
family: "Lato" # must match to a css font-family | default: "Lato"
#cdnLink: "" # a link tag for font other than Lato and Roboto | recommended
description:
family: "Lato" # must match to a css font-family | default: "Lato"
#cdnLink: "" # a link tag for font other than Lato and Roboto | recommended
brand:
family: "Lato" # must match to a css font-family | default: "Lato"
#cdnLink: "" # a link tag for font other than Lato and Roboto | recommended
footer:
family: "Lato" # must match to a css font-family | default: "Lato"
#cdnLink: "" # a link tag for font other than Lato and Roboto | recommended
copyright:
family: "Lato" # must match to a css font-family | default: "Lato"
#cdnLink: "" # a link tag for font other than Lato and Roboto | recommended
postMeta:
family: "Lato" # must match to a css font-family | default: "Lato"
#cdnLink: "" # a link tag for font other than Lato and Roboto | recommended
```
8. **Favicon Tags** *(Type: String | Accepts value: Text | Optional | No default)*
It stores HTML tags for your favicon (see example below). We recommend you to ensure that you have `"purpose": "maskable"` set for one icon in your `site.webmanifest` file (helps for PWA). We recommend `https://realfavicongenerator.net` since it's easy to use and free. By the way, we are not affiliated with them. We just like their product!
Example:
```yaml
faviconTags: |