Vision for SUIR?

[PaulAtST]

Hi, long story short I stared with a google searching how to update the font awesome icon set in Semantic UI React, and came across the issues talking about how Semantic UI React might move forwards since the Semantic UI repo is no longer updated.

This got me wondering is there a vision for how Semantic UI React will eventually move forward? Such as fork the Semantic UI project, support the Fomantic UI, make a Fomantic UI React project, or maybe another path I haven't found people talking about?

This is a great UI toolkit, and I feel like creating a vision for it would help people contribute.

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you've completed all the fields in the issue template so we can best help.

We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[sysrage]

I would also love to know what's going on with this project. It seems that SUIR v3 efforts have been stalled for awhile (#4233). Do we all need to move on? 😢

[sunech]

Agree. This is a really great project and the work that has been put in to this is really impressive. Despite looking at newer and more active alternatives, I haven't been able to find anything as overall appealing to me as SUIR.

Would be a great loss if it slowly dies.

[jkytomak]

Any news about this?
We have been using fomantic-ui with semantic-ui-react for 4 years now.
But looks like there is no future for semantic-ui project and owner of it has toxic attitude against fomantic:
Semantic-Org/Semantic-UI#7078 (comment)

We are missing all the new things from Fomantic and have to start planning shifting away from the framework to something else if this does not get sorted.

Fomantic-ui is still quite compatible with semantic-ui-react so forking it to fomantic-ui-react would be a straightforward thing and then could start slowly adding support for new features from fomantic.

ps. Thanks for maintaining this repo, too bad the base library is not maintained.

[layershifter]

@jkytomak it would be great to push SUIR to v3 (see #4409) and fork to be FUIR as FUI is not fully compatible with SUI anymore. However, at this point I personally don't have capacity and, let's be honest, enough motivation to push it forward 😢

[felixmosh]

@layershifter can you add me as a maintainer? I would like to contribute and try to push this project forward.
I think that the main issue is the coupling to the css... maybe we can fork it & move it forward... fix all the css issues that it has (In my project there is a file with all the fixes)

[layershifter]

@felixmosh The original intent of SUIR was to remain CSS-agnostic and rely entirely on CSS from Semantic UI. The issue with that approach is pretty clear - Semantic UI is no longer maintained 🪦

The Fomantic UI team seems to be doing a decent job, but they've introduced changes that make their version incompatible with SUI, see #4021. Having Semantic UI React no longer work with Semantic UI is a breaking change that defeats its purpose.

My initial plan was to bring SUIR to a better state by:

• Updating it for React 18 and Strict Mode support
• Releasing a v3 version to clean up legacy issues
• Migrating the documentation to a modern framework like Next.js or Remix

From there, the idea was to fork and create Fomantic UI React, as Fomantic UI resolves many of Semantic UI's existing problems. However, this comment complicates things 🥹.

While a fork seems inevitable, I'd like to ensure we stay true to SUIR’s original philosophy. Does it make sense?

[felixmosh]

Thank you for your explanation & vision....🙏🏽
Why the semantic-ui (css wise) is not passed to someone that whats to maintain it?

[layershifter]

Why the semantic-ui (css wise) is not passed to someone that whats to maintain it?

@felixmosh that's above my pay grade 😸 Jokes aside, these issues contain some information:

• Is Semantic UI development dead ? Semantic-UI#6109
• Pull requests and issues closed by the bot Semantic-UI#6413

P.S. To be clear, neither me of @levithomason ever had access to the main repo.