tastytea
/
hugo-theme-nocolor
1
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.
74 Commits
1 Branch
465 KiB
 
 
Branch: main
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'main'
${ noResults }
 ZIP  TAR.GZ
tastytea 9821bf6c65
Replace .URL with .RelPermalink in header. 		3 weeks ago
archetypes Add toc options to AsciiDoc archetype. 4 months ago
assets Don't specify element for classes in CSS. 1 month ago
images Update screenshots. 4 months ago
layouts Replace .URL with .RelPermalink in header. 3 weeks ago
.editorconfig Add EditorConfig. 1 year ago
CODE_OF_CONDUCT.adoc Add COC and contributing guidelines. 1 year ago
CONTRIBUTING.adoc Add COC and contributing guidelines. 1 year ago
LICENSE Add LICENSE. 1 year ago
README.adoc Add custom ARIA labels. 1 month ago
theme.toml Fix original author info. 4 months ago

README.adoc

nocolor

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.

  • Ability to inject own CSS file.

Installation

git submodule add --branch main https://schlomp.space/tastytea/hugo-theme-nocolor.git themes/nocolor
echo 'theme = "nocolor"' >> config.toml

Update with git submodule update --remote. If you don’t keep your blog in a git repository, install it with git clone https://schlomp.space/tastytea/hugo-theme-nocolor.git themes/nocolor or unpack the archive into themes/nocolor.

Configuration & Modification

Please take a look at the configuration example for Slick. It is valid for nocolor too, with these exceptions:

  • favicon and css have to be in in the assets folder.

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.

Custom ARIA labels

Some elements can’t be labeled by default because we don’t know what’s going to be in it. Custom ARIA labels are supported for the top menu and the bottom menu.

config.toml
[params]
    [params.aria]
        menu_top = "Main"
        menu_bottom = "Contact"

Syntax highlighting with Asciidoctor

If you want source code highlighting with AsciiDoc, you’ll need pygmentize from the package pygments. Set this in your config file:

config.toml
pygmentsCodefences = true
pygmentsCodeFencesGuessSyntax = false
pygmentsUseClasses = true

Run pygmentize -L styles for a list of available styles and generate a CSS file:

pygmentize -f html -S <style> -a .highlight \
           | grep -v '^[^\.]' | sed -E 's/ \.(\w+) \{/ \.tok-\1 {/' > static/syntax.css

And add :source-highlighter: pygments at the top of your posts, below the front matter. Make sure to include the generated CSS file.

Good to know

Table of contents are only written when the word count exceeds 400 and the toc field in your content’s front matter is set to true. See the Hugo documentation for details. You can overwrite the template by adding the file layouts/partials/toc.html to your blog.

Screenshots

Screenshot

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.