Open 1zun4secondary opened 1 year ago
I sugest the name "Repository" community marketplace sounds better
Why not add payment feature? I think it can promote more devs participate in and make the community more active. Many open source projects also works this way. The paid scripts/configs must appears as the custom community become big enough, so why not make it official?
Why not add payment feature? I think it can promote more devs participate in and make the community more active. Many open source projects also works this way. The paid scripts/configs must appears as the custom community become big enough, so why not make it official?
no payment i am broke
Why not add payment feature? I think it can promote more devs participate in and make the community more active. Many open source projects also works this way. The paid scripts/configs must appears as the custom community become big enough, so why not make it official?
no payment i am broke
why not make a button "donate to developer"
Why not add payment feature? I think it can promote more devs participate in and make the community more active. Many open source projects also works this way. The paid scripts/configs must appears as the custom community become big enough, so why not make it official?
Because it requires additional legal work. I cannot tell if this is possible to handle for us as well.
liquidbounce is not free anymore, so can update hvh config in marketplace pls?
I want to know if it will let the frontend get more complicated. It looks like deploying a forum into client. Will it require all custom themes to implement?
A custom theme could change the look and feel of the marketplace, but we are likely to force it to be standardised by our default to ensure no one "breaks" it. All official themes will not be allowed to include a custom marketplace look.
A stable HTML and JS SPA for marketplace, and users are able to edit CSS or use other DSL to customize it?
No. The way it works at the moment with any of the other pages. We write it using Svelte and provide the ability to interact with it through our Client Rest API.
We write it using Svelte.
Client Rest API.
Describe your feature request.
Nextgen is going to feature support for custom scripts, themes and configs. This means we have to create a place where you can share and find these user created resources.
Our scripts page would be the perfect use case for this if we would extend it further. It currently has no real use because the login does not work and there is no integration into the clients itself, but this will change with this issue.
A lot of API implmentation is required which has to be done by myself and also a design needs to be done for the integration into nextgen.
It is a idea for now, but one of my top priority for myself.
Legacy might feature something similiar, which I already introduced with my work on a settings GUI.
Additional context
You might also be wondering. Marketplace? Do I have to buy scripts etc? No, this will not mean that we will introduce payments into our client. All resources will be free like our client. It is just the best name that came into my mind.