notabase VS slate

https://notabase.io - a note-taking app for networked thinking.

It supports page stacking, linked references, block references, a graph view, and all that good stuff. Think of it as similar to Roam Research / Obsidian.

It's also open source so you can self-host it. Here's the code: https://github.com/churichard/notabase

I'm hoping to add support for shareable links soon. Open to other ideas or feedback!

you can check out this page https://alternativeto.net/software/joplin/?platform=online but the best I could find are - https://www.taskade.com/ https://standardnotes.com/ https://notesnook.com/ https://bundlednotes.com/ https://diaroapp.com/ https://notabase.io/ https://boostnote.io/ etc.

When evaluating rich text editors for the note-taking app I started about a year ago (https://notabase.io), I ended up going with Slate because of its flexible schema and customizable plugin architecture.

I sort of regret that choice now. I ran into a lot of bugs when integrating it which I had to manually work around; issues go months without being addressed; and there still isn't good cross-platform support, especially for Android. With a more active contributor base, Slate could be a fantastic library, but I get the feeling that it's in maintenance mode now, with not many major changes in the past year and a v1.0 still far in the future.

Tiptap looks like it might be a good choice now, but I find it off-putting that I can't insert links in the demo editor on Tiptap's website (https://tiptap.dev), especially for my use case (a note-taking app whose core concept revolves around links).

I'm working on an open source note-taking app called Notabase [1]. It's built primarily for my use - I just never liked most existing note-taking apps and wanted to make one that fit the way that I think. I made it open source [2] so other people can build on top of my ideas, and released a hosted version so that other people can use it if they like it. It would be nice if other people found it helpful, but regardless it's something that I intrinsically enjoy working on.

[1]: https://notabase.io

You can try Notabase https://notabase.io/, which is better for self-hosting.

if you prefer mdSilo, need to toggle the Offline mode false in code and use the third-part services: vercel and supabase

- it creates a layout based on rows and cells, so it support multi-column layout - each cell can contain a different "cell-plugin", - richt-text editor based on https://github.com/ianstormtaylor/slate is built in and comes with its own plugin system. It can do weight, italic, block-types, alignment and lists and can be extended as you want (even with elements storing data and interactive components) - you can create custom cell plugins based on a schema (or custom control ui) and a component that should be rendered - it stores an object tree that represent it, not html. It therefore can contain any react component, which is great if you want to allow your editors to add interactive components or components that you already built as part of the app - i carefully optimized for SSR and bundle size, so no editor ui is rendered nor loaded. editor ui is only loaded on the client if you disable readOnly. (lazy loading) - it mainly tested with nextjs, since i used it for content-heavy pages. - its not yet tested with react-server components, but it should actually work in read-only mode

Finally there's Slate and Lexical which are super powerful in terms of customizability and extensibility. They're great options for when the editing experience plays a major role in the product.

Slate, as per its documentation, is a completely customizable framework for building rich text editors. Therefore, it doesn't offer a feature-rich text editor but instead provides tools to build one. Let's create a component called Slate and see what the Slate editor looks like.

Link to Repo

Word of warning about Slate: I love the API and the design goals, but it appears to suffer from some fundamental issues. We were experiencing issues similar to this one and a team of multiple 10+ year experienced frontend devs couildn't figure out what was going on. I had to completely rip out a feature we had built with Slate and had to reimplement a new version from scratch with Lexical. So far we have no issues other than those inherent to rich text editing.

We're trying to choose between Lexical and Slate at work. Do you have any examples that would be similar to this? https://github.com/ianstormtaylor/slate/blob/main/site/examp...

If you are going to customise a ton of functionalities and/or implement new functionality I suggest using SlateJS. If not, have a look at Sun editor.

You definitely need to give Slate (https://github.com/ianstormtaylor/slate) a try - the best editor framework I've used.

Slate: Looks very promising, but it's for React. (Someone has floated the idea of making it framework-agnostic, but the maintainers haven't committed to that goal yet.)