I thought about it.

For example, the sidebar page tree supports keyboard navigation.

The UI library I am using, Mantine, follows accessibility best practices and has full keyboard support.

There is still a lot to do in this regard. As the project progresses, more support will come.

In the past, I built a Twitter bot (@threadvoice) to help people listen to Twitter threads in audio format ( https://twitter.com/Philipofficial9/status/11899711858004869... ). I had accessibility as one of my motivations while building it.

I have plans for OIDC integration.

Please make it trivial to use a designated "remote user" header so upstream reverse proxy could handle auth.

The software itself is very easy to install, even without Docker. You are set with just three commands: pnpm install, pnpm build and pnpm start.

Docker is not a hard dependency but it was the easiest way to document it and hope it works for everyone, given the Postgres and Redis requirements.

With time, I will create documentation for other platforms.

Thank you.

Thank you. It was my first time doing react things. The great Mantine UI (https://mantine.dev/) react library helped a lot.

Yes, I have. I have tried the Affine demo, but not SiYuan. I think they are both great and promising.

Synced blocks are interesting. It might come in the future.

1. You can use Markdown shortcuts.

2. Collaborative editing makes updating content outside the editor tricky. It will work, but not very well. I will consider supporting content updates via the API in a future release.

1. You can use markdown shortcuts on the editor. It works.

2. Mermaid support is coming.

> 1. You can use markdown shortcuts on the editor. It works.

Do fenced code blocks work as well?

draw.io is excellent; it stores source code as comments in the PNG/SVG

Perhaps equivalently, use Markdown and store directly in the rendered HTML?

I guess the best way will be to store the PNG/SVG in the storage driver with a reference to it in the editor. The same PNG/SVG will get updated/replaced whenever the code is updated. I need to do more study on this.

Storing the raw data in the editor will bloat the Prosemirror JSON and Yjs state (real-time collaboration) which I want to avoid.

Yep, I think you should store the source file (the .drawio file for drawio) as an attachment of the edited document and call the dedicated editor whenever someone wants to edit it with it, but also save the rendered file to be used to display the result when displaying the document or during regular document edition.

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.

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

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

Or they could set us free from that pattern

I have future plans for a cloud version. For now, my focus now is on building a solid software.

Outline is a great software, I have tried it.

That sounds great. Outline only has SSO in the per-user paid version. If you decide on providing additional functionality in a non-free "enterprise" version, please don't use the per usermonth model for people running it on prem.

Outline has SSO in all editions, not just paid