[href]

We are still using Confluence on-prem (behind VPN). To switch, we need the following:

- An export function (PDFs).

- An integrated diagram editor like Gliffy.

- History / diffs.

Outline is the closest to this so far, but we are in no rush, so we'll watch the development of this as well. Thanks for sharing!

[jraph]

Hi!

I'm working at XWiki SAS [1] on tools to migrate from Confluence to XWiki [2], an open source and powerful wiki software that was born at about the same time as Confluence.

We have all this. We offer support and consulting, including for handling your migration. Our migration tools try to keep as much of the content and its feature as possible, and we work on compatibility macros for this.

Feel free to reach us, or me.

[1] https://xwiki.com

[2] http://xwiki.org

[Terretta]

Comprehensive site!

Noticed this example from your store embeds French flavor for me:

https://store.xwiki.com/xwiki/bin/view/Extension/Office365In...

[jraph]

Very possible, most of us are French and Romanian :-)

[eastbound]

Please, get a designer and redesign that logo in a more trendy way. That logo may have hurt your chances since 2008.

[Terretta]

I think this misses the biggest need (which one might not consider if coming from Confluence):

- consolidation of wiki together with your code's READMEs and generated docs (e.g. sphinx, mkdocs, swagger, etc., anything that outputs documentation from your codebase)

Note on the "integrated diagram editor", this brings up another feature (though less critical than above):

- by standardizing on a docs-as-code abstraction like mermaid or kroki, you can then leverage (a) diffable diagrams as code, and (b) quite a few relevant OSS editors.

See VSCode extensions for a few different implementations, but that said, if you pick mermaid, then the same diagrams work in the wiki tool as on GitHub, as well as local-first open content format tools like Foam, Dendron, or Obsidian.md, which is nice.

[viraptor]

The diagrams as code is not a one size fit all. I'd use mermaid for some technical things, but it's failing for communication/presentation purposes. You need to have the ability for arbitrary placement, annotations, flow. Mermaid is all fun until you want to connect two previously distant boxes and everything explodes - for long-term documentation purposes it may not even matter, but if I'm about to show it to anyone, I'm going to Excalidraw.

[dominicdewalt]

I work on the Mermaid Chart product team and your comment here is extremely relevant to a big project I'm working on that will solve a lot of the problems you mentioned! Would you be willing to tell me more and give your thoughts on our plan for solutions?

If you're open to it, please send me an email at [e-mail]!

I'd be happy to exchange an Amazon gift card for your time too!

[someone4958923]

We use Bookstack[0] for this and I can recommend it. Free and open source.

- PDF Export - Oauth2 - Revisions - History - Permissions - WYSIWYG/Markdown/Diagrams etc.

[0] https://www.bookstackapp.com/

[lf-non]

Bookstack is quite nice but last I saw it doesn't support multi user collaboration which this tool seems to include as a core feature. That can be a big differentiator for a lot of people.

[Pi9h]

1. PDF export will come.

2. Diagrams will come too. MermaidJs is next on the line. Other diagram providers like Draw.io and Excalidraw will come once I figure out an efficient way to handle storing and retrieving their raw data.

3. There is support for page history. No diff comparison yet though.

[itomato]

Mermaid is cool, but you need to land a Draw.io or Gliffy or Lucid.

[mirzap]

It would be better to provide a plugin system so the community can contribute to the project.

[itomato]

Or they could set us free from that pattern

[gcanyon]

I haven't tried it in Confluence, but https://www.tldraw.com/ can be embedded in Notion at least, and works very well as a diagram editor.