RFC: Split out bindings into un-opinionated core

[3noch]

This library does two distinct things:

• Provides bindings to Semantic UI JS API
• Provides a very specific type-driven API for interacting with Semantic UI's styles and JS

I'd like to propose that these be split into two libraries. I found the API for styles is abstracting along the wrong axis for my use case so I don't use them (e.g. styles and colors are implementations of larger goals that often change depending on the application, so the abstractions will need to be per-app to make the most sense). However, the bindings are still useful, but many of them don't work well.

I pulled much of the binding out to here: https://github.com/3noch/reflex-dom-semantic-ui-core

[mightybyte]

This sounds like a reasonable idea to me. Any ideas on repo names, etc? I'm thinking we should leave this library as-is for people who are using it and set up the other two independently as you're describing.