A library that does half of the stuff that notion does and manages to create some sort of consistent markdown output would be amazing. Notion's UI is one of the few editors I enjoy more than simply writing markdown on vscode.<p>This is amazing work and I think the main thing I see missing is navigation.<p>Thank you for working on this.
For people who are interested in another open-source alternative to Notion; Trilium[0] seems very strong in its features and its customizability. It supports markdown formatting which is a common request in this thread.<p>[0] <a href="https://github.com/zadam/trilium" rel="nofollow">https://github.com/zadam/trilium</a>
Thanks for sharing my project! :)<p>To be clear, it is indeed a demo project only. I just like Notion, so I thought it would be fun to recreate some of its functionality.<p>If anyone wants to dive deeper into how the clone works, I wrote a Medium article about that: <a href="https://medium.com/swlh/how-to-build-a-text-editor-like-notion-c510aedfdfcc" rel="nofollow">https://medium.com/swlh/how-to-build-a-text-editor-like-noti...</a>
Is there something sketchy about Notion? I'm unable to access it from our companies network, it's been blocked as malicious. Could it just be the .so?
I want Notion + Custom JS components, written inline. You could build a database with a Notion table, write some code that edits it in a little inline code snippet, similar to Observable.io, then publish it on the web as an instant low-code app. Very useful.
Hopefully this works decently in Firefox.<p>Unlike Notion, which <i>still</i> gets confused by a mouse middle click, and instead of opening a new tab inserts your clipboard contents wherever it feels you clicked on the page. Likely in the middle of the URL you clicked on.<p>But it only happens about 1/2 the time. The other half of the time it works properly, opening a new tab.<p>This is pretty much a complete blocker for using Notion, as randomly adding your clipboard contents (can be passwords, sensitive conversation pieces, etc) is a security nightmare. :(
congrats! i see you are storing images on the server itself. where are you hosting your backend? did you consider splitting out image hosting to s3? why or why not?