Replies: 1 comment 1 reply
-
Spina doesn’t use ActionText, Spina uses a custom implementation of Trix just for the Spina::Parts::Text model. There’s no tight coupling, it’s easy to support a different editor by adding a new Spina part (i.e. Spina::Parts::Quill). We welcome new gems that add support for other editors! For now, Trix will remain Spina’s default which we’ll include in the gem. But if something better comes along we’d be happy to change that default. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I think Spina is a really exciting project that I want to try on a project, but the dealbreaker for me is Trix. It's just a very bad editor, in my opinion, both for the lack of customisation and the terrible markup it provides.
Would you consider - at some point in the future - making the Trix integration a separate gem and let the community create their own integrations (with quill, tiptap, tiny or whatever)? This is the route RefineryCMS took, they decoupled the wymeditor integration from Refinery Core and made it a gem instead so the community could take care of the rest.
Or does Action Text and its tight coupling with Trix make this impossible?
Beta Was this translation helpful? Give feedback.
All reactions