[neovive]

We're in the same boat. I brought Confluence into our org almost a decade ago — it was the best collaborative wiki tool at the time. Over time the price has increased while the quality of the tool has not kept pace with other options. This seems to be the trend as software companies grow into large "enterprise" providers.

Looking at our Confluence usage over the years, I noticed that we use it primarily as a knowledgebase/documentation tool and less for collaboration. With our on-prem license expiring, we are migrating to a dedicated knowledgebase for our FAQ and frequently changing content and switching to a Markdown tool + Git for our more formal documentation.

[unethical_ban]

>I brought Confluence into our org almost a decade ago — it was the best collaborative wiki tool at the time

I respectfully disagree with that assertion! I remember 2012 (okay, 11 years ago). I had just joined a new team at work, and the documentation for the team was a lot of vendor PDFs and some .txt files from the lead stored on a network drive.

The company was just implementing Confluence, but it was slow on client and server side with no HA. That is the fault of the server team, not Atlassian, but still the software was ick.

I spun up a shadow-IT Dokuwiki server that was much easier to use for a small team with text-based documentation needs. It had a naive "calendar" plugin that allowed the quick creation of pages based on date, which we used for oncall hand-off. Backup was zipping the data folder on the server.

It was probably 3 more years until our hand was forced to use the "enterprise standard" for business continuity purposes.

[gwright]

Could you share what markdown/git tooling you've identified?

[neovive]

Sure. We're focusing first on converting everything to plain Markdown and using a Git repo to manage the content. Writers can use whatever Markdown tool they prefer for this. (I'm using Obsidian and others are iA Writer.) I have yet to decide on the docs publishing tool, but I'm testing Astro, Vitepress, and Markdoc for publishing. I'm leaning towards Astro since it's very flexible, easy to add small bits of interactivity via MDX, and has a nice collection of themes. VitePress is also very nice, super fast, and very easy to publish. Since only the developers and tech writers need to collaborate on the docs, we're following a docs-as-code approach — using GitHub issues, comments, and pull requests.

[HankB99]

Not speaking for the GP. I use MkDocs and keep my personal notes. The only weak spot for me is that I haven't fully grokked search and as my notes grow, it can be harder to find things. I alternate between figuring out how search and how to bolt on some other search utility.

MkDocs includes a utility to publish to Github pages but I keep my notes on a self hosted Gitea server and serve using "python -m http".

[vorpalhex]

For something quick and easy consider https://github.com/gollum/gollum#markups which powers Github Wikis.

Note that multi-user auth is NOT supported out of the box however.

[belthesar]

Obsidian is a pretty good solution for this in my experience