-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Materializecss is no longer supported #6615
Comments
Yeah, wow, it's awfully quiet around here. Sad too. I've used this in the past and liked it. Any comments or updates on project status, @Dogfalo , please? |
Seriously this very dead for a large repo :( |
If anybody is interested - some long term contributors have forked the repo and are working their way through the major issues with a view to a new release very soon. https://github.com/materializecss/materialize Looks like they set up a new Gitter support channel too: |
Hi everyone, I would love to help get this moving again. I'm using Materialize extensively. Love working with it ... but it obviously has numerous flaws. I'm not great with the whole Github setup (just never had it forced on me) and haven't been involved in Open Source previously. If someone can get in touch and let me know how we get things moving - if we can get things moving, I'd be very keen. |
We've now got nightly builds setup on the active fork, you can find them here https://nightly.link/materializecss/materialize/workflows/nightly/dev/build.zip |
After years using materializecss, I give up :(. Now I'm a contributor of another project called beercss.com. Maybe you like it. I'm trying to spread it now and some feedbacks are welcome too. |
❤️🙋♂️ |
Looks Great would love to use and Contribute!🎉 |
We'd welcome a PR over on the new fork to fix this 😄 Speaking of, we released 1.1.0-alpha recently and would love feedback on it. |
only remove scaleX and scaleY part from "AnimateIn" sort out my problem, anyway thanks |
Don't waste your time.
They really should put a notice on materializecss.com to be upfront with users.
The text was updated successfully, but these errors were encountered: