Wikidot evacuation initiative

Right now, my focus is to make sure that Wikidot projects aren't gone as soon as Wikidot does. As part of this plan:

I create backups of Wikidot projects and host them publicly: https://github.com/luna-spirito/wikidot-kolorinko-export
I deploy a (for now, read-only) mirror for projects that desire one, taken down on first request, aiming to be as self-contained as possible. If you want one, please contact me via links above.

I'm trying to match Wikidot's behaviour & rendering as close as possible, so that minimal intervention is necessary, but:

We're still in beta, there are lots of known rendering issues I had no time to fix just yet, but I'm getting there.
Fully matching wikidot's broken behaviour is not always possible unless I deliberately reimplement its bugs in Dentrado.

Long-term Goal

My goal is to develop the platform for creative textual & web content, providing all the tooling necessary to:

manage large-scale knowledge databases (inspirational example: Obsidian),
brainstorm ideas,
publish and share content,
manage communities,
fearlessly collaborate on the content.

... all while trying my best to ensure:

preservation of human creativity,
performant always-available service,
- the intention is to provide a local-first application, and, generally, make Dentrado the Waffle House of the internet (always open, even in a hurricane), but this takes time.
user-friendly experience built on top of modern technologies.

Technology

Dentrado is unique in a way that it's built on top of experimental database technology, intended to make it much easier to implement complex features.

Key quirks of our approach:

Embedded, easy-to-deploy architecture: dentrado is just a single binary + a bunch of static assets. You can easily deploy it yourself: all it takes is a few lines in NixOS config.
We're HTTP/3-first.
We're realtime-first. Changes made to the website are automatically propagated to all connected clients.
We're multithreaded, for real: the core is built on top of Thread-per-Core architecture, which is meant to make it scale nicely with stronger hardware.
Pluggable architecture: components are interchangeable, making it easy to swap functionality instead of forcing every use case through a single narrow gate.

Key future priorities:

Distributed, low-latency reliable network, powered by eventual consistency. Each Dentrado instance is both capable of working autonomously and synchronizing its state with others as soon as this is possible.
Federated network. I don't trust any single point of failure, and dentrado.art isn't meant to be one. The service should be hostable by anyone. And, if one instance falls, others should be able to continue serving its content.
Version-control-system architecture, making it possible to freely experiment with existing content and roll back.
Local-first, Obsidian-like experience. Dentrado should be able to serve as an encrypted personal knowledge database, and shouldn't necessarily depend on network connection for normal function.

Codebase is written mostly in Rust, GitHub repo: https://github.com/luna-spirito/dentrado/ LLM-assistance is utilized to make solo developing the project of this scale feasible. The design is always human-written, the code is constantly verified.