Is the project active?

[webJose]

Hello! First and foremost, thanks for the library. Us, the artistic-impaired, appreciate it very much.

Second: I ask if the project is currently maintained. I fear the amount of open issues and the issues that have gone unanswered.

The reason I ask is that I was thinking about creating a Svelte component library for Bulma, since current projects haven't updated and I really liked it when I did this live demo of my router in Sveltekit.

To create a component library takes time and effort, so I figured I should first ask so as to not potentially waste said time and effort which can be focused on something else.

Thank you!

[guest20]

This is discussed in #4024.

[webJose]

Thanks for the pointer. It is an interesting discussion, but without input from the actual owner, is just opinions thrown around. The question is not answered.

I do agree with the other poster that issues without replies are a bad signal, and I also agree that Bulma is probably far from completed. On top of that, I think that leaving PR's from contributors unattended is very rude. After all, people have come here with their time spent, for free, for the benefit of everyone, to contribute and they are simply ignored. I feel this behavior is a virtual spit in the face.

Of course, all this is my opinion. Maybe I'm overreacting. I guess it isn't important.

What's important here is an official statement from a core maintainer. Would love to get one. In the meantime, I'll put my library idea on hold.

Thanks again for the link.

[guest20]

You forgot to click "Close issue".

[webJose]

I did not. I want the issue open. Look at what happened with the issue you linked. Because it was closed I did not see it, and then I opened this one. I'll leave this one open until a maintainer closes it for the benefit of others wanting to know the answer to the question.

[guest20]

Your leaving it open... So other people can see that you're worried about there being so many tickets open.

Exceptional.

[ScottAwesome]

Thanks for the pointer. It is an interesting discussion, but without input from the actual owner, is just opinions thrown around. The question is not answered.

I do agree with the other poster that issues without replies are a bad signal, and I also agree that Bulma is probably far from completed. On top of that, I think that leaving PR's from contributors unattended is very rude. After all, people have come here with their time spent, for free, for the benefit of everyone, to contribute and they are simply ignored. I feel this behavior is a virtual spit in the face.

Of course, all this is my opinion. Maybe I'm overreacting. I guess it isn't important.

What's important here is an official statement from a core maintainer. Would love to get one. In the meantime, I'll put my library idea on hold.

Thanks again for the link.

If you're creating a component library you should own your code anyway. Fork the repo and move on.

[webJose]

If you're creating a component library you should own your code anyway. Fork the repo and move on.

Apologies, but I'll call this as I see it. This is an absurd proposal. Who says my skillset covers CSS? I surely do front-end, but that's far from creating a beautiful thing like Bulma.

[guest20]

I think what @ScottAwesome is saying is that your js library is more likely to break if you don't bundle bulma with your releases...

Something similar happened to bulma's docs recentrly-ish when with a bunch of extensions disappeared off the internet #3976

[webJose]

Thanks for the link. I haven't heard of the Wikiki issue until now. If I understood correctly, a GH user named Wikiki had created a bunch of components that extended Bulma, and one day everything was gone.

Well, if that happened to Bulma itself, the more reason not to do my library. Like I said, my CSS skills are not in par to what a project like Bulma requires. Me forking/copying the code is of no use regardless. The suggestion still doesn't work for a CSS noob like me.

[guest20]

They were examples and some extra components that the docs mention, they're not core components...

[ScottAwesome]

Thanks for the link. I haven't heard of the Wikiki issue until now. If I understood correctly, a GH user named Wikiki had created a bunch of components that extended Bulma, and one day everything was gone.

Well, if that happened to Bulma itself, the more reason not to do my library. Like I said, my CSS skills are not in par to what a project like Bulma requires. Me forking/copying the code is of no use regardless. The suggestion still doesn't work for a CSS noob like me.

To be honest if you aren't willing to put in the work learning CSS, noob or not, I would hesitate to be building out an entire component library.

On the other hand, if you wanted to learn and build at the same time, forking this code base and building on it would not be a bad way to go about it. It's clean and understandable enough that it wouldn't be the hardest thing in the world. I did it for work at one point a few years ago due to the lack of updates.

You're either discouraged to learn or embrace it. Knowledge comes from trying and stretching one's self

[webJose]

Maybe I don't have enough interest, correct. I know it is necessary (CSS), but I'd rather do other things. I'm currently knee-deep in a Vite plug-in that can auto-externalize import map entries for my micro-frontends library. No time for CSS.

[guest20]

Maybe rename to jsjose?

[Orel-A]

Yeah, I noticed it's not actively maintained. There are few bugs in RTL support. There are also questional claims of not styling checkbox and radio button components. I copied the style of Bootstrap from there.
I think it this repository needs a heads up, a warning of some sort that this is not actively maintained project.

[madis]

If it's well designed and written and works, what is there to maintain? When I see a library that uses modern standards and works and is well documented, I am happy that there are no frequent changes because it shows that the thing is solid and stable. Evaluating project's health and suitability based on the frequency recent changes is not a good metric. Bulma is stable and works. Besides it's open source so if you see something missing, you already know what to do.