Switch to Duckquill for documentation

[daudix]

It's been a while since #784, in which I've created my own Zola theme.

Demo is available on daudix.github.io/distrobox.

The main differences are that all Markdown files now live under the content directory, all layouts and styling is now managed by Duckquill submodule, which means easy updates, and of course the looks, copy button for code blocks, cross-site search, and other QoL improvements :D

In terms of syntax everything is pretty similar to Jekyll, the link syntax is different though, which means they don't work without building the site.

Since GitHub Pages automatically build only Jekyll sites, I've added a new workflow that builds the site to the gh-pages branch on every new commit in the release branch, and tests the build on pull requests. GitHub Pages source will need to be changed to the gh-pages branch.

[89luca89]

Thanks @daudix is there a way to keep the doc directory as is?
the idea is that docs here, and website (and man pages too!) are all in sync and easily discoverable

sending the repo docs in content seems like "hiding" them from the repo

[daudix]

I understand your concerns, the content can't be directly under the docs directory, and I didn't know that the man pages are being generated from the docs, so I'll turn this into a draft until the details are worked out.

[89luca89]

I understand your concerns, the content can't be directly under the docs directory, and I didn't know that the man pages are being generated from the docs, so I'll turn this into a draft until the details are worked out.

got it thanks

maybe we can have ./docs in the main repo (like now) and symlink into content? would that work?

[89luca89]

@daudix can we do the reverse?

right now ./docs is a link to ./site/content, can we do so that ./site/content is the link to docs?
so that docs are kept where they are