v4.0.9

• Bug fixes

Full Changelog: v4.0.8...v4.0.9

v4.0.8

• Bug fixes

Full Changelog: v4.0.7...v4.0.8

v4.0.7

What's Changed

• Move font-feature-settings and font-variant-ligatures to @font-face declaration
• Update license year
• Add www.sagbot.com to USER.md list by @Lurgrid in #483
• add adamperkowski.dev to USERS.md by @adamperkowski in #484
• Update USERS.md by @imortio in #487

New Contributors

• @Lurgrid made their first contribution in #483
• @adamperkowski made their first contribution in #484
• @imortio made their first contribution in #487

Full Changelog: v4.0.6...v4.0.7

v4.0.6

What's Changed

• add KaTeX support as a community feature by @amtoine in #468

New Contributors

• @amtoine made their first contribution in #468

Full Changelog: v4.0.5...v4.0.6

v4.0.5

Update marketing stuff v2

v4.0.4

Update marketing stuff for Terminal.css

Full Changelog: v4.0.3...v4.0.4

4.0.3

• Fixes issues with headings (duplicated h1)
• Fixes styling for headings
• Adapts to updated terminal.css

Full Changelog: v4.0.2...v4.0.3

v4.0.2

Update README

Full Changelog: v4.0.1...v4.0.2

v4.0.1

Updates related to Hugo Themes collection.

v4.0.0

We came back with the version 4.0.0!

The new version is more customizable than ever, thanks to Terminal.css. You can even generate matching favicon and default og-image.

Terminal.css was built because many people want their websites to look like Terminal Theme, but (unfortunately) they don't use Hugo. This simple service allows anyone to taste the style of the theme. Terminal.css is stupidly simple because we love simple websites.

On the other hand, many people were asking me about adding new color schemes to Terminal Theme and I wasn't so sure about that... But after Terminal.css came to life I thought: Why not mix both?

---

Things that have been deprecated and removed from the theme:

• Sass (scss files). We use vanilla CSS now, since color-mix() has finally been adopted by the browsers. This is handy because you can use simple JS to manipulate the color scheme, whenever you want.
• oneSizeHeadings param. This can be simply replaced with a few lines of CSS.
• favicon param. Now, just replace /static/favicon.png with your own file.

Due to Hugo's updates, a language configuration also has slightly changed. But this is not directly related to the theme.