MkDocs/mkdocstrings 404 CSS TIL update
Posted on 2025-02-28 22:23 +0000 in Coding • 1 min read
Following on from my post this
morning, regarding the problem I was
having with _mkdocstrings.css
being 404 any time I deployed by
documentation, build with mkdocs
/mkdocstrings
, to GitHub Pages...
It's come to light that I was doing this on hard mode, pretty much.
While trying to figure out the best way of deploying the docs, I'd stumbled
on ghp-import
and had been using that. On the other hand, MkDocs has it's
own command for doing the same thing: mkdocs
gh-deploy
.
Timothée pointed out to
me
that he never runs into this problem, but he used this command. As it turns
out, if you use mkdocs gh-deploy
it creates the .nojekyll
file by
default.
And how does it do this? It uses the ghp-import
code and uses a switch it
has to achieve exactly
this.
In fact... the command line version even has a switch for it!
-n, --no-jekyll Include a .nojekyll file in the branch.
This is off by default, when you run the command itself, but I wish I'd noticed this when I was first experimenting. O_o
Anyway, thanks to Timothée's pointers, I've now managed to simplify how I
build and publish the docs from
textual-fspicker
,
and I'll apply this to other projects too.