This issue should discuss how we want to handle "community adders", so adders that are not made by the original author.

Example in this case is the bulma adder.

As of the current layout of the project, there is the organization svelte-add which has all of it's adders in separate repositories.
@babichjacob proposed that if the adders match his quality standards he would be happy to add those to the org and give the initial authors write access to this special repo.

What's the goal of this ticket?
To discuss what should be the best way to handle all of this with at least overhead for the maintainer(s) as possible, while keeping usability for the users in mind

My opinion
I could imagine that community will create a bunch of those adders, as I think they are really helpful. Managing all those repositories the way @babichjacob proposed might cause a big overhead in my opinion.
Although normally i am against monorepos, I think that could make sense here. Let me explain:

Pros:

• We only have on repo that needs to be maintained
• We don't need to manage user access for a bunch of different repos, everything could go with PR's
• Those adders could share some common code, if they have to (cannot image which code at the moment)
• We already have svelte-add which could handle the abstraction on top of use preset / apply (use-preset docs for monorepos)
• If Sveltekit is breaking something in the future, it would be easy to adapt all adders, because they are all in the same place

Cons:

• Well, monorepo
• Probably a bunch of issues will come together here

The list above is probably not complete, so feel free to add thinks