vitesse-modular-naiveui
modern-editor
| vitesse-modular-naiveui | modern-editor | |
|---|---|---|
| 1 | 1 | |
| 12 | 14 | |
| - | - | |
| 10.0 | 10.0 | |
| over 1 year ago | over 7 years ago | |
| TypeScript | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vitesse-modular-naiveui
-
Ask HN: Help me pick a front-end framework
+1. I also recommend this template[1] based on Vitesse, a starter project created by one member of Vue core team. It includes the NaiveUI library with many advanced components ready.
[1] https://github.com/arijs/vitesse-modular-naiveui
modern-editor
-
Ask HN: Help me pick a front-end framework
> "building a text-annotation based app"
I'm going to assume that you are talking about a desktop-based webapp that is also responsive, and not a native app. I also believe you when you say that you do not know where you are getting into.
I have 10+ years of experience doing front-end, with probably over a dozen React packages self-published in npm, and also tried making a rich text editor ~6 years back[1]. I actually recommend starting with no framework at all (please read on).
Creating a rich text editor might be the hardest thing you can do in "normal" front-end (excluding some more advanced "frontend" fields like 3D or games). You can either manipulate raw cursors, which will be very tricky because I'm not even sure you have access to all the right APIs (specially on mobile), or you can attempt to use Contenteditable, which is a hell of its own[2].
"All problems start with caret placing and multi browser support" [3]
That said, I believe 90% of the complexity of your app will be here, around the actual interaction with the or <div contenteditable> that you will be using. For that, no framework will really help you, at all. So my recommendation is to first get that working, which will take weeks/months and hundreds or thousands of lines of code, and then worry about placing the little hovering boxes in their place (the "UI"), which is like 10 lines of JS/CSS[4].<p>[1] <a href="https://github.com/franciscop/modern-editor" rel="nofollow">https://github.com/franciscop/modern-editor</a><p>[2] <a href="https://answerly.io/blog/my-pain-developing-a-wysiwyg-editor-with-contenteditable/" rel="nofollow">https://answerly.io/blog/my-pain-developing-a-wysiwyg-editor...</a><p>[3] <a href="https://news.ycombinator.com/item?id=27938702" rel="nofollow">https://news.ycombinator.com/item?id=27938702</a><p>[4] <a href="https://stackoverflow.com/q/4495626/938236" rel="nofollow">https://stackoverflow.com/q/4495626/938236</a>
What are some alternatives?
structured-text
htmx - </> htmx - high power tools for HTML
TOAST UI Editor - 🍞📝 Markdown WYSIWYG Editor. GFM Standard + Chart & UML Extensible.
Mithril.js - A JavaScript Framework for Building Brilliant Applications
Svelte - Cybernetically enhanced web apps
DefinitelyTyped - The repository for high quality TypeScript type definitions.
Elm - Compiler for Elm, a functional language for reliable webapps.
lexical - Lexical is an extensible text editor framework that provides excellent reliability, accessibility and performance.
create-t3-app - The best way to start a full-stack, typesafe Next.js app