tastytea
/
hugo-theme-nocolor
Watch 1
Star 0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Activity
Hugo theme with no predefined colors.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
35 Commits
1 Branch
Branch: main
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'main'
${ noResults }
tastytea 381ab23cae
Make admonitionblock-labels bold. 		1 week ago
archetypes Add AsciiDoc archetype. 3 weeks ago
layouts Use nav element for top navigation. 2 weeks ago
static/assets Make admonitionblock-labels bold. 1 week ago
.editorconfig Add EditorConfig. 3 weeks ago
CODE_OF_CONDUCT.adoc Add COC and contributing guidelines. 3 weeks ago
CONTRIBUTING.adoc Add COC and contributing guidelines. 3 weeks ago
LICENSE Add LICENSE. 3 weeks ago
README.adoc Add extra_foot.html. 2 weeks ago
theme.toml Bumped min_version to 0.58. 2 weeks ago

README.adoc

nocolor is a Hugo theme with no predefined colors and minimal styling. It is based on Slick.

Features

  • Supports taxonomies of tags, categories and series with their own pages.

  • RSS Feed with complete entries.

  • Open Graph, Schema.org and Twitter Cards support.

  • Fully customizable menu entries.

  • No JavaScript, no bundled fonts, no external requests.

Installation

Just download the theme or clone it into your themes/ directory:

cd themes && git clone https://schlomp.space/tastytea/hugo-theme-nocolor.git nocolor

Then reference it in your config:

theme = "nocolor"

Or when building the site, pass it in to the CLI:

hugo -t nocolor

Modification

Please take a look at the configuration example for Slick. It is valid for nocolor too.

You can add things to the end of the <head> section by overwriting the partial template extra-head.html or above the footer by overwriting extra_foot.html. The common way to do it is to create layouts/partials/extra_head.html or layouts/partials/extra_foot.html, respectively.

If you want source code highlighting, take a look at tomorrow-pygments.

How to contribute

Read the Code of Conduct.

Reporting bugs or suggesting enhancements

Before reporting a bug, please perform a search to see if the problem has already been reported. If it has, add a comment to the existing issue instead of opening a new one. Same for enhancements.

You can also contact me via E-Mail, XMPP or the Fediverse if you don’t want to open an account.

Pull requests

Please use similar coding conventions as the rest of the project. The basic rule to remember is to write code in the same style as the existing/surrounding code.

You can also send me your patches via E-Mail, ideally using git format-patch or git send-email.