It's well documented ( https://taskwarrior.org/docs/ ) had enables a number of different workflows and export and import options (I've dabbled with jira imports to task warrior for my own sorting views).

It's markdown, allows copy pasting images, works offline by synching using apple/google/microsoft/dropbox cloud storage.

Has desktop and mobile app.

Free and Open Source.

You can run your own sync server and not rely on cloud storage at all (there's a docker image - very simple to set up). It also imports and exports a hierarchy of folders/markdown files, so on- and off-boarding are simple.

For many years I used plain old markdown files and either git or syncthing to ship them around, but the editing and viewing experience was never great, and sync on iOS wasn't exactly seamless.

The other big benefit is cross-note search. Previously I had to rely on the editor I was using - which was fine on a desktop with VSCode, but nonexistent on mobile.

I was looking at setting up a wiki and considered Dokuwiki and Bookstack. I ended up using Tiddlywiki, which is by default a single user wiki that is actually just a single HTML file that defines the whole app and the wiki contents. This means that all you need to run it is a browser that can read HTML and run JS.

I since migrated from running it as a single HTML file to a Node.js server to enable better version tracking with Git and to make saving updates less cumbersome. It's a little wonky to save updates to the single-file version without a custom browser plugin or app.

Anyways, at some point I might try migrating to a more traditional wiki solution as I like the idea of being able to share parts of my wiki with others. But for now Tiddlywiki works nicely for me!

But I also landed on bookstack. Weird how it turned out that formatting my stuff like a book would be the best format as opposed to all the super cool different ways of thinking that are possible with new-gen apps. I'm not sure if books are just superior or if I just personally am really wired to books, but I landed on it after evernote, onenote, obsidian, joplin, and Notion.

Basically I am using tiddly as a zettelkastan where appropriate and bookstack for things that are more finalized.

I really wish my team would switch to BS instead of the unorganized knowledgebase soup with inconsistent tagging, zero curation, and bad search engine (servicenow knowledge). omg what if we had an actual procedure manual instead of just hoping people will enter the right search terms to land on KBs they dont even know to search for. now THAT would be revolutionary.

BookStack dev here. When originally building BookStack, I did initially built it with infinitely nestable pages since it seemed like the "technically better" approach that didn't limit user content, but in use it just made UX and discovery a pain, especially for the mixed-technical-skill workplace environment I was targeting, which is when I landed on the book > [chapter >] page setup (With shelves being a late awkward addition based upon demand). Good to hear that works for you. Is often the love-it-or-hate-it factor of the platform.