You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If using output.html.additional-css, the filename given will be included at the top of all files... including, unmodified, in files in deeper directories.
This means additional-css pretty much presently doesn't work for mdbooks that use directories. :(
Workarounds
None that I've discovered.
I considered a workaround of setting additional-css = ["custom.css", "../custom.css"], but this is (sensibly enough) rejected during mdbook build because the latter file doesn't exist.
I considered a workaround of making a symlink back up to my custom css file in each dir I have, but it doesn't get copied into the site build dir, so this also doesn't work.
If using
output.html.additional-css
, the filename given will be included at the top of all files... including, unmodified, in files in deeper directories.This means
additional-css
pretty much presently doesn't work for mdbooks that use directories. :(Workarounds
None that I've discovered.
I considered a workaround of setting
additional-css = ["custom.css", "../custom.css"]
, but this is (sensibly enough) rejected duringmdbook
build because the latter file doesn't exist.I considered a workaround of making a symlink back up to my custom css file in each dir I have, but it doesn't get copied into the site build dir, so this also doesn't work.
related
#789 is probably related.
The text was updated successfully, but these errors were encountered: