RichTextKit VS SwiftCurrent

Previously I used RichTextKit. Note how they’ve organized the code, all to prevent dangling references of TextViews. I’ve since moved on to implementing the editor as a native webview since I was starting to not see much benefit to implementing text editing natively.

Also, when we have mixed the two, in general the results haven’t been impressive from a dev and user perspective. For example, we’re leveraging a `UITextView` for the text control on the back of cards. Although it addressed some of the limitations/issues with a `TextEditor`, it comes with issues of its own. Personally find having the ability to bridge the experience using both frameworks extremely convenient but on the flip side inelegant. So we’re considering replacing it with a rich text control developed by someone who has focused on the problem themselves: [Daniel Saidi and his RichTextKit](https://github.com/danielsaidi/RichTextKit).

Going to see if I can get data-driven workflows into https://github.com/wwt/SwiftCurrent so that you can define an order of things dynamically from a server. Already having some successes with SwiftUI, so I'm hopeful it'll land (or at least beta) by the end of the month.

If you want to look under the hood to see how we set up all our CI/CD code, you can look here: https://github.com/wwt/SwiftCurrent/tree/main/.github

I'm not sure if you're still looking into this, but this library might help: https://github.com/wwt/SwiftCurrent specifically that it helps you manage workflows through your app. It sounds like you're in UIKit, which there's support for managing at the view controller level. You might want to take a look to see if it gives you any ideas.

Repo: https://github.com/wwt/SwiftCurrent

Working on https://github.com/wwt/SwiftCurrent with a focus on getting SwiftUI support out of beta. I also need to do better in the readme to more convincingly portrait the library's value for managing complicated workflows in your swift apps.