The latest updates on your projects. Learn more aboutVercel for Git ↗︎

Should we put this stuff inside a bigcontributing.md file?

Feels like this should go inapps/svelte.dev, no?

Are these instructions sufficient? Presumably you also need a GitHub app set up for auth, otherwise you can't save to the db anyway

Should we put this stuff inside a big contributing.md file?

Done

Feels like this should go in apps/svelte.dev, no?

Done

Are these instructions sufficient? Presumably you also need a GitHub app set up for auth, otherwise you can't save to the db anyway

No idea. There's at least less missing parts now than before. But I don't really have this stuff setup or know enough to document it fully

I don't think there's much point merging a PR until we've validated that it works

My main concern was trying to cleanup the sites repo without losing anything

would be possible to add the playground as an iframe from svelte.dev so the translation sites doesn't have to host their own db?
Since the playground (can i keep calling it repl?) need the github auth and a separate db I think that would fragmentate userbase. Would be nice to have all the users in the same db. Would that be very complicated?
https://sveltefr.dev/playground/hello-world?version=5.1.3

Stuff like this is why we'd prefer to internationalise svelte.dev than have a bunch of different sites with translations

I deleted all files from the sites repo except for the HN example, so these files only live here. It is impossible for me to do anything else in this PR because I don't know what the rest of the setup steps are, so I can't document them. I'd be happy if someone would like to complete this PR. Otherwise, I think this is still worth merging as some help is better than none and folks aren't going to know to look in the PR queue to find the files that are necessary to setup the DB