Move non-integration stuff into a new repo

Question

Move non-integration stuff into a new repo

Rich-Harris opened this issue 6 years ago · 12 comments

As discussed in sveltejs/svelte#2436, we're retiring this repo in favour of sveltejs/integrations (in fact I've renamed the repo so that it redirects).

Some of the things listed in the current README don't really belong in an integrations list, so will eventually need a new home. README snapshot right now (since I'm about to wipe it): sveltejs/svelte#2436

Answer 1 · 2019-09-20T20:22:33.000Z

Something like awesome-svelte?

It's not as maintained as I'd like, but I think it can do the job.

Answer 2 · 2019-09-21T17:46:46.000Z

I've been maintaining a list of resources similar to CalvinWalzel/awesome-svelte. I've been trying to avoid duplicating this official list and link to it in multiple places, but there's overlap where the official list is incomplete, like preprocessors. I plan to deprecate it once there's an official replacement and welcome any feedback.

Answer 3 · 2019-10-05T19:59:36.000Z

@ryanatkn @CalvinWalzel @Wolfr

How would you feel about helping to maintain an official 'resources' list like the ones you already have but under the Svelte banner? It shouldn't be too much work and we don't know what that will look like or how it would work right now, but having a single canonical list of community resources or an at-a-glance view of the Svelte ecosystem that we can link to from the docs (or it could even be a page on the site) would probably help a lot of folks out.

Answer 4 · 2019-10-05T20:01:21.000Z

Okay, I've just seen the conversation with @sw-yx in this issue, we'll have to think about whether or not a resource list should live with the community stuff.

Answer 5 · 2019-10-05T23:53:44.000Z

I'm interested in helping. I'll start by converting what I have to JSON and displaying it in a fork of sveltejs/community. From there it could be merged back or kept as a separate site, whichever gets chosen.

Answer 6 · 2019-10-06T00:00:45.000Z

A true legend.

Answer 7 · 2019-10-06T01:17:06.000Z

@ryanatkn fwiw i think json is annoying to write and maintain. i prefer keeping it in markdown or keeping in yml. up to you tho

Answer 8 · 2019-10-06T02:03:41.000Z

@sw-yx Yeah I agree about JSON. My plan is to get my markdown file into JSON, and then we can convert it to yml or something else, and also settle on a good data structure and merge with the other 2 lists. Authoring in yml sounds good to me unless someone else has a suggestion. Gatsby uses yml for this purpose - https://github.com/gatsbyjs/gatsby/blob/master/docs/starters.yml

Answer 9 · 2019-10-06T02:21:07.000Z

yeah. someone just PR'ed a new event and it's already invalid JSON lol (cos of trailing comma)

i'm setting up netlifycms for this here https://github.com/sveltejs/community/pull/5 and it should be able to consume and output and edit yml with a nice UI with no running server. can convert yml to json at runtime easily.

Answer 10 · 2019-10-06T11:37:34.000Z

@pngwn I would feel totally fine if my list (here) was re-used under an official community banner.

At the moment I can't promise much involvement but don't want to be a blocker, so feel free to just take it, edit it, re-use it.

Answer 11 · 2019-10-06T11:40:05.000Z

That’s great, thanks! It is an excellent resource.

Answer 12 · 2020-05-22T08:15:54.000Z

Closing this with a view to consolidate a proper component marketplace / browser under community in the near future.