* 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>
* Upgrade mermaid-js/mermaid @ 0918b97
* Update exampleSite with new mermaid graph (stateDiagram-v2) example
* Update content of mermaid.js with officially distributed v8.8.0 minified version
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
Since the old link redirects to "Hugo Modules" documentation, which isn't fitting for this kind of theme, I changed it to the short tutorial in the getting started guide. Not perfect but better than having a mismatching guide, confusing users (such as myself).
