Dokuwiki VS api-scripts

Dokuwiki for Documentation

I have used DokuWiki in few personal and work (non-gamedev) projects. Seems to work well. https://www.dokuwiki.org/

While considering alternatives, I thought about DokuWiki, which looks like an unlikely solution, and Nextcloud, which I've already used in the past. Both seem a good option in their own right, though I favor Nextcloud because it's a more direct approach. However, I'm inclined towards a solution that's leaner and less bloated. Nevertheless, if any of those is the one that is most likely to solve my dilemma, I'm open towards using any of those two. I'm also investigating Anytype.io, which seems like the best option, but it seems it works with an invitation.

FYI, the PR is https://github.com/dokuwiki/dokuwiki/pull/3798 if you want to read about it

The oldest and still supported software that will cover all your list - is: DokuWiKi It is web based, but there on site you can even find portable installation on flash drive. No database, plain files as backend.

I already have a Dokuwiki set up on my home server, which would make it easy to attach notes and datasheets to the various items. But I wonder if there are some purpose made solutions for this. Not too complicated or it won't be updated very often...

joplin or DokuWiKi

DocuWiKi - one of the oldest one, no need for database and it even has thumbdrive version

www.dokuwiki.org

Also, a release candidate has been tagged, so a new version should be coming "soon".

Not really specific tools for that purpose, but our api-scripts repo has a collection of examples that use the API, which could be used as a basis for building something more specific. Within the readme there is also a variety of more extensive community project, some of which may also be useful here.

You could run a script that uses the API to export all content to PDF/HTML. I have a basic example of this here in our API scripts repo.

Their Script

To add to this, some people script and cron regular exports via the API. I have a basic example script here.

Also, if it helps, we have API script examples here and there is an existing bash cli build here.

If you wanted accessible non-DB copies of your content, this is possible via a couple of options. Some users script exports of all their books. I have an example of this here in our API script examples repo. Alternatively you could write out raw content to plain files on the system via hooking into events using our logical theme system. I have an basic example of doing this for HTML format content within this blog post.

I found this this evening

Can't give too much advice in regards to Confluence, but in regards to BookStack import the REST API is probably the best best. API docs can be seen on our demo instance here. API usage examples, and community projects/scripts, can be found here if it helps. You might be able to find existing confluence to bookstack scripts. Came across this in a search but not sure how feature complete or up-to-date it is.