Materialize Moving Forward

[ryanrapini]

Hey all,

I'm coming here from the discussion here.

I am happy to start providing pull requests. There are several minor issues that I would love to be fixed in the short term, as I have been using materialize in a very mature Laravel/Vue project in production for the last 4+ years. If there's a confirmation that this is in fact the place to put pull requests and that they will be accepted here instead of stagnating, I'd like to help.

Let me know if there is some sort of organization/trello/work board that i can see.

[createdbyken]

HI, I was reading that conversation. I'm really excited to see materialize going forward. I'm available too to support this project. I've been a huge fan of Materialize since the beginning. Is there's something I can help with please let me know. I can maintain any other tasks or create pull request in order to support Materialize.
Best Regards!

[DanielRuf]

Let me know if there is some sort of organization/trello/work board that i can see.

So far we have no such board but the project at https://github.com/materializecss/materialize/projects/1

We can probably use the free version of ZenHub.
I have invited you to the org. We will create different teams later when we have enoug people so we can create a good structure with different permissions.

[DanielRuf]

For existing pull requests like Dogfalo#6521 I did the following:

# clone the new fork, best is you fork it you clone it to your personal account and use your username instead of materializecss
git clone git@github.com:materializecss/materialize.git
# go into the new folder
cd materialize
# add the original upstream repo as remote
git remote add upstream git@github.com:Dogfalo/materialize.git
# fetch all references from the upstream
git fetch upstream
# checkout the original PR and branch using the GitHub CLI
# alternatively see https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally and use upstream instead of origin
gh pr checkout 6521
# now push the branch to your own fork or the materializecss one
# create new PR from the branch and submit it to materializecss/materialize

[DanielRuf]

@mau5ken I sent you also an invite to the new org.

[createdbyken]

All right!!! Very excited. Let's make MaterializeCss great again! <3

[Chrisx84]

Let me know if there is some sort of organization/trello/work board that i can see.

So far we have no such board but the project at https://github.com/materializecss/materialize/projects/1

We can probably use the free version of ZenHub.
I have invited you to the org. We will create different teams later when we have enoug people so we can create a good structure with different permissions.

i just use trello as a roadmap https://trello.com/b/V8PvCLz1/gridplay-roadmap

[DanielRuf]

We want to keep development in one place and not clutter it with many different tools and logins.

So far it works for the projects where I am collaborator.

[Chrisx84]

ah ya good idea, kinda does look like a trello board. well good luck with this project, cant wait to use it again on my websites. YES plural, i got many all using bootstrap right now

[ChildishGiant]

I have multiple projects that are reliant on materialize so would happily lend a hand.

[DanielRuf]

@ChildishGiant awesome =) We could need some help to triage the open PRs from the upstream repo and to decide which we should merge here in the fork.

[ChildishGiant]

Dogfalo#6078 (Add new i18n option 'headerFormat' to datepicker)
Dogfalo#2490 (Add input suffix)

These both seem like targets. I'm having troubles with my git though, so can't test them rn :/

[DanielRuf]

I've added both to #7

[createdbyken]

@DanielRuf is there need to be a new site for a the new changes the whole community is doing? I think it would be nice, I can go over a complete new UX/UI design page in order to bring attention to this project.

Also I'm coming as a 100% supporter. I want to spend more time in Open source project's now, so @DanielRuf feel free to discuss anything priority with me.

Thanks! <3

[DanielRuf]

@DanielRuf is there need to be a new site for a the new changes the whole community is doing? I think it would be nice, I can go over a complete new UX/UI design page in order to bring attention to this project.

At least the website is a live demo of the framework and its capabilities (eat your own dog food). A distinction and a different design could be useful to make clear that this is a fork with improvements and major changes in the future after the biggest bugs are fixed.

I think we could need more examples, a better search and better getting started guide with some example projects for those who are not that experienced with JS (but would find code blocks useful that contain the needed code). A bit like the coding blocks for Foundation Sites (I'm a maintainer of Foundation Sites): https://get.foundation/building-blocks/ (just an idea). And this would probably help more people to get started with materialize.

[DanielRuf]

npmjs org created and original 1.0.0 release uploaded to npmjs: https://www.npmjs.com/package/@materializecss/materialize

[doughballs]

@mau5ken this is a great idea. Also, an opportunity to change the default theme colour - lighthouse downgrades the current default colours for poor contrast, if you pay any attention to that sort of thing.

@DanielRuf also great idea - I use materialize exclusively in Wordpress, and am working on a theme at the minute, thinking about how I can help the user with blocks in the same way. Everything is moving in this direction.

I have never worked collaboratively before, so not sure how to contribute beyond my opinion in here.

[DanielRuf]

I think we can prepare the next release in the next days / weeks.
I'll go through the current changes then, check if it's a minor or patch release and start preparing some changelogs if I find the time. Help is very welcome.

After this we'll setup semantic-releases probably to automate this, migrate the CI setup (maybe before the release?) and so on.

[createdbyken]

How can I contribute to acquire the .org extension for materializeCSS? I would like to make this donation in order to start uploading some new improvements. Plus, I can't download the repo to make some improvements is there a protocol for this @DanielRuf ?

Thanks for your kind reply.

[DanielRuf]

To provide a PR you have to do the following steps:

Fork the repo to your own account:

Then clone and checkout your branch.

git clone git@github.com:mau5ken/materialize.git
cd materialize
git checkout -b your-new-branch-name

Then apply your changes, commit and push them to your fork.
From there you can open a PR to materializecss/materialize.

There are also some guides like https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request and https://opensource.com/article/19/7/create-pull-request-github

[DanielRuf]

How can I contribute to acquire the .org extension for materializeCSS?

I'm not sure if it makes sense to buy the org version when the original project has the com version. This could lead to some confusion when they land on the wrong website / fork.

I might still have a few domains for free in my hosting plan so you may not have to buy one.
Also when someone donates a domain we would need to have control over it (DNS and so on) just in case something happens.

For now it's best when I order some domain, enter the needed registration details and create a separate account in my hosting which contains only the domain and I elect someone or some of us who should also have access to it.

We should discuss and decide together what the best solution is, also regarding the situation that there is still the com version which is used by many.

[doughballs]

@DanielRuf one question re PR - now that I’ve created my first one, what about if I need to create a second one? Do I have to do the whole process again? Or a new branch? Or just a new commit to the same branch?!

And re the domain/name/new brand - I realise we may not have the forward movement for materialize2 just yet, but it would be a good idea to really differentiate us from .com (to avoid confusion) and I think a number 2 is a solid way to do it. Or some other clear marker that this is a new path.

[wuda-io]

Materializecss2.com sounds good

[DanielRuf]

@doughballs in this case you create a new branch for the new PR.

[blackjyn]

Damn, I'm at the progress on making Materialize CSS course on Udemy.
I'll probably help on making the docs even friendlier cos current docs sucks

[DanielRuf]

Damn, I'm at the progress on making Materialize CSS course on Udemy.
I'll probably help on making the docs even friendlier cos current docs sucks

That sounds great. Looking forward to your first PR here =)

[blackjyn]

@DanielRuf not pretty soon, but I do have collected several bugs and possible enhancements on Forms and JS Comps.
For instance, the Accordion comps does NOT support <dl><dt><dd> construct, while other FW like Bootstrap supports it.
Also, incomplete aka partial support on Form's component validation.
etc. etc..
lot of things.

[khashashin]

If you guys need help of the community, I would recommend you to create new release asap and show people that this fork started to make releases and push new features. Then, I believe, people will switch to this fork.

[DanielRuf]

If you guys need help of the community, I would recommend you to create new release asap and show people that this fork started to make releases and push new features. Then, I believe, people will switch to this fork.

This is planned for this or next month (a new release) =)

[wuda-io]

The beauty of Materialize is it's neutrality , I mean it is independent from other frameworks. But nowadays let's admit we are using JS frameworks extensively to build websites. However since Materialize is at the "critical condition", here's the alternative you might consider if you were really wish for "moving forward" from Materialize:

• Svelte : Svelte Material UI
• React : MUI
• Vue : Vuetify

I had assembled Materialize paid course material some 1-2 years ago , but given the project is abandoned so I got no more interest to publish it , hell not even interested to finish it.

Please dont speak for others, if you cant finish your project, then it is not the fault of Materialize. Not everyone wants to depend on some short living Frameworks which change every now and then so thats fine. Some projects want to use some light, nice independent CSS and JS which can simply be exchanged and be flexible without needing to refactor the whole system. I think that should also be the target of the whole project.

[wuda-io]

Maybe we should seek some funding for the project, I would be glad to help out as developer if my work is funded so I can invest time in it. Who would be interested in such a solution too an can provide some fixed amount of time developing it? Then we could set up some funding and project plan.

[mxdpeep]

I am moving to Beer.css for the server-side Mustache templating (PHP 8.1), and v3 of my CMS system will be powered by Vue.js and Vuetify - I need to learn some modern JavaScript shit :))) *Filip Oščádal* *https://mxd.cz <https://mxd.cz>*

…

On Sat, Mar 26, 2022 at 9:17 AM Daniel Wurzer ***@***.***> wrote: Maybe we should seek some funding for the project, I would be glad to help out as developer if my work is funded so I can invest time in it. Who would be interested in such a solution too an can provide some fixed amount of time developing it? Then we could set up some funding and project plan. — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAASMXSHXLFK6ICTM6NEOQDVB3BYDANCNFSM4OWEBJ7A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[wuda-io]

So you have to depend on 3 things rather than using 1 thing properly? Sounds not very efficient but good luck. Fortunately you got matetialize to work. What made you use beercss? And why on the Server?

[mxdpeep]

1) Vue and Vuetify are both in active and rapid development, I don't like React 2) server-side rendering is still a good option for Progressive Web Apps 3) Beer.css is also actively developed 4) I have no funds to invest into Materialize myself Filip Oščádal 🍀📱

…

On Sat, Mar 26, 2022, 12:01 Daniel Wurzer ***@***.***> wrote: So you have to depend on 3 things rather than using 1 thing properly? Sounds not very efficient but good luck. Fortunately you got matetialize to work. What made you use beercss? And why on the Server? — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAASMXQ6LNVVPI3JCACYMX3VB3U7JANCNFSM4OWEBJ7A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mxdpeep]

BTW Beer.css is 70 kB only Filip Oščádal 🍀📱

…

On Sat, Mar 26, 2022, 12:21 Filip Oščádal ***@***.***> wrote: 1) Vue and Vuetify are both in active and rapid development, I don't like React 2) server-side rendering is still a good option for Progressive Web Apps 3) Beer.css is also actively developed 4) I have no funds to invest into Materialize myself Filip Oščádal 🍀📱 On Sat, Mar 26, 2022, 12:01 Daniel Wurzer ***@***.***> wrote: > So you have to depend on 3 things rather than using 1 thing properly? > Sounds not very efficient but good luck. Fortunately you got matetialize to > work. What made you use beercss? And why on the Server? > > — > Reply to this email directly, view it on GitHub > <#2 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAASMXQ6LNVVPI3JCACYMX3VB3U7JANCNFSM4OWEBJ7A> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[wuda-io]

Yes beer is cool, but i would miss all the components, like multiselect etc. so i can not use it.
I think this project is awesome, so i will contribute here and push this forward. I think only the design needs some facelift, and some improvements, but the rest looks good 👍

[DanielRuf]

For any task there is a fitting tool, or multiple. You can all use what is best and fits your requirements, stack, team knowledge and so on.

I am only aware of one big customer on our side where we have an old Materialize v1 version (not the one from the fork). Other projects are mostly built in React and use Tailwindcss and custom components.

Maintaining opensource software is still a hard job and in most cases you get not paid for it. If you want to start some funding @wuda-io then it should be probably done with https://opencollective.com/.

[blackjyn]

Please dont speak for others, if you cant finish your project, then it is not the fault of Materialize.

I never blame anyone.
The reason I stop making it, is that why should I selling a course about a framework when the FW itself has no clear progress, no clear maintenance and no clear future?
I won't selling "fraud" course about FW that even the original creators are no longer care about.

Materialize has clearly been abandoned and if that's hurt you, its all on you whether you accept it or not.

[mxdpeep]

I feel you, bro. 🍀❤️ Moving forward with a different toolset is my only option. 😂 Yes, making open source is hard... Filip Oščádal 🍀📱

…

On Sun, Mar 27, 2022, 06:52 Igzo Valka Byzantine ***@***.***> wrote: Please dont speak for others, if you cant finish your project, then it is not the fault of Materialize. I never blame anyone. The reason I stop making it, is that why should I selling a course about a framework when the FW itself has no clear progress, no clear maintenance and no clear future? I won't selling "fraud" course about FW that even the original creators are no longer care about. *Materialize has clearly been abandoned and if that's hurt you, its all on you whether you accept it or not.* — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAASMXWY2XAOUVCLECGC223VB7SRPANCNFSM4OWEBJ7A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[TomFreudenberg]

@blackjyn - nothing to add

[wuda-io]

Yeah you can leave and use other tools.
But if it has no future then why are you looking up this project, come here and tell people what you think?
If you dont have anything to contribute thats fine but you should have some respect for other projects. I dont even know what you want... Would you be using Materialize when there is a fixed release plan or what are your concerns?

[DanielRuf]

@wuda-io please let's stay calm. I see no problems with recommendations for actively maintained solutions =)

I already had this case more than once, especially when I stopped maintaining and contributing to Foundation Sites after the original team wasn't working on it anymore.

Frontend is an area where things move fast and it is helpful when others tell us what solutions they use to know their needs. As maintainer you often do not see or want to see how things are changing. That's ok.

I see no disrespectul behavior. Please change your tone and let's move on together. If this does not help I will have to lock and moderate this issue here.

[DanielRuf]

Guys please refrain from fighting - otherwise I will lock this here. @blackjyn no further comments are needed, this is currently not helpful.

This and other things are reasons why I stopped contributing my free time to opensource projects and especially maintaining. Until today I thought that we could bring this project forward together. But if everyone is just fighting, then I will completely stop the project and archive it. I have no energy to argument in such a heated discussion.

As both of you probably won't stop I'm closing this one here.
I hope you are ok in these hard times, because I'm not.

[DanielRuf]

Going to archive this repo since you won't see any future contributions as I will focus on more important things in life.
Any stress is currently very toxic to me, my health and body.

I wish you all a great time with whatever you want to do, create and use.

[DanielRuf]

If any of the current @materializecss/maintainers want to bring this project forward, please contact me on LinkedIn.