TinyMCE
turbo
TinyMCE | turbo | |
---|---|---|
41 | 145 | |
14,383 | 6,424 | |
1.2% | 0.8% | |
9.7 | 8.7 | |
about 3 hours ago | 9 days ago | |
TypeScript | JavaScript | |
GNU General Public License v3.0 or later | 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.
TinyMCE
-
TinyMCE (also) moving from MIT to GPL
TinyMCE provided a bit more information about this change in a GitHub discussion thread here: https://github.com/tinymce/tinymce/discussions/9496
As I posted there, this directly affects my open source project which is heavily tied to TinyMCE so I may end up forking, and reducing down to what my project needs to reduce maintenance scope & burden.
TinyMCE have been jumping around with their licensing. They were under LGPL, with some (what I believe were) misleading guidance into meeting the LGPL (they specified rules about keeping specific branding elements). They then jumped to MIT, and since moved some of the open plugins to their commercial offering. Now they're making this change.
-
TinyMCE 7 - Revision History, Document Converters, Markdown and more!
TinyMCE 7 includes fixes for 17 bug fixes reported by the community. See the changelog for details.
- TinyMCE Dumping MIT for GPL
-
A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
TinyMCE - rich text editing API. Core features are free for unlimited usage.
-
Join the TinyMCE Challenge at the online API World + AI DevWorld Hackathon 2023
Website
-
Wordpress updating old classic editor version
Any idea how i could replace the current classic editor with the newest tinymce wyswig editor: https://www.tiny.cloud/ it looks so modern and clean and i would love to use it but the default wordpress classic editor is so old and is some really old version of tinymce and I'm unsure of how to change it, any plugins or scripts to do this?
Any idea how i could disable the default crappy wordpres ugtenbergs block and instead replace it with the newest tinymce wyswig editor: https://www.tiny.cloud/ it looks so modern and clean and i would love to use it but the default wordpress classic editor is so old and honestly makes me sick, any plugins or scripts to do this?
-
Creating a Rich Text Editor with TinyMCE and React
Luckily, implementing a basic text editor in your React application is a fairly straightforward process. In this article I will show you how to implement a rich text editor using TinyMCE.
-
DraftJS
Check https://www.tiny.cloud/
-
Laravel for Beginners #4 - Create a Dashboard
I'm using TinyMCE as the rich text editor, you can replace it with something else, or simply use a if you wish.
turbo
-
Turbo Streaming Modals in Ruby on Rails
I also recommend checking out the docs for Stimulus and Turbo to familiarise yourself with all their features and the APIs used in this series.
-
Htmx vs. React: A Complete Comparison – Semaphore
https://github.com/hotwired/turbo
- Turbo 8 has been released
-
What is JSDoc and why you may not need typescript for your next project?
Turbo 8 remove typescript without using JSDOC
-
Coming to grips with JS: a Rubyist's deep dive
Experiment using Turbo to drive front-end behavior: "Turbo 7.2.0 (currently in beta) allows you to define your own Stream actions which can be any JS code you want. By combining a custom Stream action or two with web components, you can essentially drive reactive frontend behavior from the backend stupidly easily. Loooove it! 😍 […] For a turnkey example, you could check out https://github.com/hopsoft/turbo_ready " —Jared White on The Spicy Web Discord
-
Improving a web component, one step at a time
This handles disconnection (as could be done by any destructive change to the DOM, like navigating with Turbo or htmx, I'm not even talking about using the element in a JavaScript-heavy web app) but not reconnection though, and we've exited early from the connectedCallback to avoid initializing the element twice, so this change actually broke our component in these situations where it's moved around, or stashed and then reinserted. To fix that, we need to always call addSparkles in connectedCallback, so move all the rest into an if, that's actually as simple as that… except that when the user prefers reduced motion, sparkles are never removed, so they keep piling in each time the element is connected again. One way to handle that, without introducing our housekeeping of individual timers, is to just remove all sparkles on disconnection. Either that or conditionally add them in connectedCallback if either we're initializing the element (including attaching the shadow DOM) or the user doesn't prefer reduced motion. The difference between both approaches is in whether we want the small animation when the sparkles appear (and appearing at new random locations). I went with the latter.
-
Mastering Rails Web Navigation with link_to and button_to Helpers - Part 2
If you think you have seen enough Rails magic, you are mistaken my friend. Rails have a new trick up its sleeve: Hotwire. And with the magical Turbo tool that comes with it, you can create modern, interactive web applications with minimal, or sometimes no JavaScript at all, providing users with an incredibly smooth experience.
-
Why you should choose HTMX for your next project
There is also Turbo and the frameworks who adopt them, Ruby on Rails, PHP Symphony and possibly others that solves the same issue in the same manner as HTMX. And the choice for HTMX is only a personal taste in this, but you should definitely learn about this, this is as cool as HTMX!
-
JavaScript First, Then TypeScript
Most controversially, the Turbo framework dropped TypeScript support altogether after assessing that strong typing was the culprit behind poor developer experience.
-
Rack Attack – Rails Tricks
Turbo[0] has been solving this for years. Quite the contrary, front-end frameworks have started to think "sending JSON is good, but actually sending HTML could be great!".
DHH's presentation[1] during Rails World 2023 is quite interesting in that regard, I recommend you give it a go (start around minute 16). I am actually very excited with his vision of the web.
[0] https://turbo.hotwired.dev/
What are some alternatives?
quill - Quill is a modern WYSIWYG editor built for compatibility and extensibility.
htmx - </> htmx - high power tools for HTML
Draft.js - A React framework for building text editors.
Turbolinks - Turbolinks makes navigating your web application faster
CodeMirror - In-browser code editor (version 5, legacy)
hotwire-rails - Use Hotwire in your Ruby on Rails app
ProseMirror - The ProseMirror WYSIWYM editor
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
trix - A rich text editor for everyday writing
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)
Froala Editor - The next generation Javascript WYSIWYG HTML Editor.
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.