mkdocs-material VS api-scripts

Material Mk-Docs by Martin Donath works well if you prefer python.

https://squidfunk.github.io/mkdocs-material/

I'm an 'outsider', but from from the outside the Material For MkDocs Project looks like a very well managed open source project.

Martin Donath's project uses a 'sponsorware' release strategy to generate donations.

From my vantage point it seems to be working pretty well.

I just recently went through this decision process. My aim is to write code and math oriented posts so I need good support for nice syntax highlighting (at least colored) and mathjax (preferable) or katex. Substack is the most popular newsletter platform but fails at these two criteria. I love how math and syntax highlighting (plus numerous other features) work in MkDocs Material, which recently added a Blog plugin.

I wanted to combine the best of both: Substack as an amazing email social network, and MkDocs Material’s awesome look. So I’ve gone with using Substack as the core platform which I use to manage subscribers, and use it to post either math/code-free posts or a short teasers pointing to my main blog site on MkDocs Material when I need to show math/code

https://squidfunk.github.io/mkdocs-material/

I've been migrating content to MKDocs (Material) over the last few months, so feel fairly qualified on this subject. It's somewhat limited in terms of navigation, but can probably handle 400-500 pages; you can see how navigation works in the link. Otherwise, it can handle most, if not all, the tasks you've listed.

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.