Resucitate `styx` - `mdbook` isn't good enough

[blaggacao]

I realized, the sharing model of mdbook documentation is far below my nix-infused expectations of the minimum viable threshhold.

Nix is perfect staging environment for metadata (think: reconciliation loops interfacing with third party systems, your infrastructure and just about everything you want), that also may find double-use geared towards documentation.

mdbook just doesn't work very well for that scenario.

styx seemes — with a little reparative and proactive maintenance ahead — ideally suited.

@siraben I tried to contact you in matrix, fwiw.

https://github.com/styx-static/styx

[disassembler]

I got it working just well enough I could deploy my website using flakes with a fork, but it definitely needs some love... https://github.com/disassembler/styx

[blaggacao]

https://github.com/styx-static/styx/pull/65 uff :smiley:

Meanwhile, we must content with a fork: https://github.com/divnix/styx

[siraben]

@blaggacao currently traveling, will get back when I'm free.

[blaggacao]

@siraben I've gone a little wild yesterday by sort of finishing off the 1.0.0 release work. Since I'm not yet acrively using styx, I'm only as confident as yhe test suite and the styx-site (with some local wip adaptions).

I beleive, styx-as-framework needs further hammering into shape through a swappable eval.nix consolidates interface (similar to colmena) for tight integration with std*, but that latter oart need not bother you.

If we can get styx upstream a bit modernized, I'm already totally happy

[blaggacao]

And there is (new) https://github.com/danth/coricamu