Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Status #7

Open
jlukic opened this issue Jun 23, 2015 · 7 comments
Open

Project Status #7

jlukic opened this issue Jun 23, 2015 · 7 comments

Comments

@jlukic
Copy link

jlukic commented Jun 23, 2015

What's the status of this project? Is it being actively maintained?

I'd like to include some react examples out of the gate with the 2.0 release next week. I would love your input.

@jhudson8
Copy link
Owner

I'm not actively maintaining this project (I love semantic-ui though and think you've done a great job with it).

@tomitrescak
Copy link

Is there any good alternative? thanks

@bradparks
Copy link

Haven't tried it, but this

https://github.com/jessy1092/react-semantify

appears to be an alternative....

@empz
Copy link

empz commented Jul 2, 2016

@tomitrescak This one is supposed to be the official Semantic-UI/React library. They still haven't got to 1.0.0 but it's looking promising.

@tomitrescak
Copy link

@emzero Meanwhile I have created a library of my own (I know .. the worst solution). It is completely lacking tests and HTML documentation, but it is using Storybook to showcase and test all components (will be made more robust).

https://github.com/tomitrescak/semanticui-react

I currently cover most of the components and have nice perks such as support for i18n or more robust components. While I think that stardust should be your choice num 1, this is a viable alternative.

@levithomason
Copy link

There's now an official Semantic-UI-React project, currently called Stardust. It will be ported to Semantic-Org soon.

@fibo
Copy link

fibo commented Nov 22, 2016

can you please deprecated this project, since it is not maintained? Write deprecated in the readme and remove it from npm, or at least make it do not install nothing and advice user it is deprecated on install. It is confusing, since there is an official package now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants