Since a while, Hugo has its own mechanism for code highlightning.
We remove the old highlightning code provided by the client-side javascript library highlight.js and all its related files.
This also solves issues introduced by Hugos own highlightning because in our theme we are currently highlighting the code twice leading to unpredictiable results.
This will also fix an issue were light code highlightning themes weren't displayed correctly because our styles are overwriting color information.
Another advantage is the huge list of supported languages which by far exceeds our current list.
On the downside, this is a breaking change because our current color theme isn't supported by Hugo.
* enabled mermaid by default
* implemented logic to use internal oder cdn mermaid
* added english documentation
* added french translation for the mermaid options
* Removed useless test print
* Hugo does not use upper case letters in params
* fixed false sample link
* improved mermaid pages
* fixed always load mermaid if no frontmatter specified
* applied 3 new params to default config
* Implemented Home Button logic
* Applied default style
* applied same landingpage ref to logo partials
* added sample image, how the button will looks like
* added en documentation on how to configure the button
* translated home button configuration to french via deepl
* applied home button style to theme variants
* set button disabled by default
* fixed mermaid samples
* removed obsolete css files
* changed default version of mermaid cdn
* renamed mermaidURL to customMermaidURL and removed css link
* improved mermaid configuration description
Co-authored-by: Arthur Ferdinand Lindner <Arthur-Ferdinand.Lindner@Telekom.de>
Co-authored-by: Arthur Ferdinand Lindner <arthur.lindner@outlook.de>
* enabled mermaid by default
* implemented logic to use internal oder cdn mermaid
* added english documentation
* added french translation for the mermaid options
* Removed useless test print
* Hugo does not use upper case letters in params
* fixed false sample link
* improved mermaid pages
* fixed always load mermaid if no frontmatter specified
* fixed mermaid samples
* removed obsolete css files
* changed default version of mermaid cdn
* renamed mermaidURL to customMermaidURL and removed css link
* improved mermaid configuration description
Co-authored-by: Arthur Ferdinand Lindner <Arthur-Ferdinand.Lindner@Telekom.de>
Co-authored-by: Arthur Ferdinand Lindner <arthur.lindner@outlook.de>
Previously adding custom css files would require the end user to copy
the header or footer partial into their overrides. They would then
need to maintain that partial into the future.
This config allows a user to provide a list of custom css files to load
into the theme, meaning they do not need to clone the partial.
```
[params]
custom_css = ["css/foo.css", "css/bar.css"]
```
Inspiration taken from https://discourse.gohugo.io/t/how-to-override-css-classes-with-hugo/3033/4
`<script src="{{"js/html5shiv-printshiv.min.js" | relURL}}{{ if not .Site.Params.disableAssetsBusting }}?{{ now.Unix }}{{ end }}"></script>`
This was only ever needed for IE8 (which is not supported with this theme since it uses a newer version of jQuery). Furthermore it should be loaded in the head anyway. IE9 supports HTML5 tags and does not need this polyfill at all.
I'm seeing issues where the check icon is not rendered. It seems like it this `<i></i>` element was mistakenly missing the additional class required in order for it to actually render the font-awesome check icon. So, I added the `fa-check` class locally and now it works as expected.
This is useful because using "alt" attribute is generally a good idea. But I had to change this in my project because I am running automated tests and this was causing an error from my over-zealous error-checker robot. Fair enough.
Removing class="" because it does not add a whole lot
Removing role="" because it is invalid HTML (cannot be empty) and generates HTML-errors in validators.
