The background rendered properly if dark mode was specified explicitly in the config.toml, but not if the config.toml specified auto mode and then dark mode was chosen by the client.
* Add files via upload
import from scss files from ../vendor
* added academicons import
import from _academicons-import.sass
* added license for academicons
* added academicons fonts/scss in vendor
* added academicons in static/fonts
* changed social.html to differentiate between fontawesome and academicons
* deleted academicons manually loading
in the first steps I had implemented academicons manually before I added it in the assets/sass
* Delete .DS_Store
* Delete .DS_Store
* Delete .DS_Store
---------
Co-authored-by: bpkleer <benk@sowi.jlug.de>
* fix-262
* Replacing Moment.js with native JavaScript
* Update config.toml
Adding the "auto" option of themeStyle to the comment.
* Remains of Google+ removed
* Fix for issue 260
* Fix for issue 283
* Remove double import of Font Awesome
* Revert "Remove double import of Font Awesome"
This reverts commit 913d0f34fe49593215efc1c56e199894a3aa0603.
* Remove double import of Font Awesome
* fix-262
* Replacing Moment.js with native JavaScript
* Update config.toml
Adding the "auto" option of themeStyle to the comment.
* Remains of Google+ removed
* Fix for issue 260
* Fix for issue 283
Setting "a $h-color" was breaking correct color rendering for blog post titles in light theme. It was trying to override the href element color i.e. # dbdbdb with title color # 222222
- Uses the scroll-behavior property to achieve smooth scrolling with
less JS
- Solves anchor link bugs
- Linkifies headings in posts so they can be easily hyperlinked to directly
Footnotes are using a fragment format with a colon inside ("#fn:1" for
example). However, ":" is a special character for jQuery
(http://api.jquery.com/category/selectors/), thus the target anchor is
never found and the scrolling does not happen.
This change selects the right target element using vanilla Javascript to
bypass special characters that could be in the fragment part.
* Center the navbar again on the home page
* Favor the project page for listing projects
The project listing has its own page we can link to instead of going
back to the (potentially fading in) home page each time.
