Making a Wikigit is quick, and most of the technical work that used to be involved is now done for you. You don’t set up a server, you don’t wire two services together, and you don’t need to know any code. You pick a name and choose where your pages should live.
Go to the Create page on wikigit.org and you’ll be walked through three things.
your-name.wikigit.org
That’s the whole setup. Everything after this — writing pages, changing the look, inviting others — happens inside the wiki you just made.
This is the one real decision, and it’s the question of who holds the files.
Host it for me. wikigit.org keeps your pages in a repository on your behalf. You need nothing but your sign-in, and there’s nothing to manage. This is the easiest path and the right one for most people. If you ever want the files under your own account, you can move them out later — you’re not locked in.
Use my own GitHub repo. Your pages live in a GitHub repository you own. You install the Wikigit app on that repo, enter its name, and wikigit.org serves your wiki from it. Pick this if you already live in GitHub or want the content unambiguously in your own hands from day one. Either way the identity and editing experience is the same.
Open any page and click Edit to prove it works — change a line, save, watch it appear. Then make it yours:
Everything above uses wikigit.org to host the moving part for you. If you’d rather own the entire stack, you can: the Engine is a small Bun server you can run on your own host behind a reverse proxy, with the reader served as static files from anywhere. That’s more work and more control, and it’s the exception, not the path most wikis take.