novel VS nanostores

novel editor based on TipTap

The difference is I am gonna let users write notion like documents and then share it, unlike pastebin which only lets us share text. For writing documents, I'm gonna use Novel.sh. It is a WYSIWYG editor which provides interface and features similar to Notion. It also lets us use OpenAI API to integrate AI into it.

Probably tiptap.dev, here's a notion-like editor built with it: https://github.com/steven-tey/novel

I love the simplicity of it tbh, the homepage with it's builtin demo is just superb.

https://novel.sh/

Write ++ after the npm install or whatever, the homepage is an editable demo of the editor.

Tiptap is incredible! Built https://novel.sh/ with it and the extensiveness & API is chefs kiss! So proud of you guys and the YC funding is truly well-deserved! Congrats again!

Great guide. One thing that seems to be missing is something I see in a lot of README's: a list of the core tech stack being used in the repo. Good examples here https://github.com/undb-xyz/undb#-tech-stack and here https://github.com/steven-tey/novel#tech-stack. Did you already consider adding this as part of the guide and decide against it, or was it just not something you thought to add?

I'm trying to customize https://github.com/steven-tey/novel 's amazing template. but currently output stream comes in plain text. and even it gives markdown or HTML code the text editor doesn't render them accordingly.

In its docs, Astro recommends nanostores, but I’ve used effector in the past. And LOVED IT. So I’ve used it for this project as well.

Nanostores explanation

vidstack is very light on technical details but starts with a concise intro and a screenshot, as well as relevant links: https://github.com/vidstack/player

payload is well-structured in general: https://github.com/payloadcms/payload

nanostores starts out with an intro and telling code examples, followed by lots of technical details: https://github.com/nanostores/nanostores

Nanostores and Reatom are also great, fast atomic libs

Astro handles multi-framework components (React, Vue, etc) and they recommend using the nanostores library for shared state.

Checkout Nanostore it's what Astro.build recommends for sharing state across different ui libraries.

All of these are valid ways of fixing the state management issue, but it's clear that we need to find a common solution that works for all the UI libraries. This is where nanostores comes into play! The description they provide on their GitHub page is simply perfect:

Jotai and Valtio are both also really good. Recently looked at Nanostore as well and has some similarity to Jotai and Recoil.

Just to chime in on framework agnostic stores, Astro.build recommends using Nano Stores to handle reactivity, as the base library is very small and they have adapters for most relevant frameworks. I definitely agree that avoiding framework lock-in is the smart thing to do.