Korean translation to 00-introduction.md

[donghhan]

This is the first draft of Korean translation of Sapper's "00-introduction.md" part. Briefly introducing myself, I am junior frontend developer who just started off learning Sapper and felt love in using Svelte these days! I have experience in translating many English development online tutorials into Korean.

Although there is not yet skyrocketing interest in Svelte, I can see some couple of companies in South Korea are adopting Svelte for their service. As a Svelte lover, I would like to contribute to Korean translation so that I could help Svelte and Sapper could be more beloved by more and more Korean people.

I wanted to contribute to Svelte at first, but it seems there were no slot for me to leave my work for you to review, and that's why I am starting off with Sapper. If this is not the right way for me to contribute to Korean translation, then please give me comments via apensia914@gmail.com.

Hope you could see my message.

NOTE: All development is currently focused on Sapper's successor, SvelteKit: https://kit.svelte.dev/ We are not adding new features to Sapper. While we might fix some particularly pressing or easy to address bugs, it's highly unlikely that most PRs will be reviewed.

Before submitting the PR, please make sure you do the following

• [ ] This message body should clearly illustrate what problems it solves.
• [ ] Ideally, include a test that fails without this PR but passes with it.
• [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs

Tests

• [ ] Run the tests with npm test and lint the project with npm run lint

[benmccann]

Thanks. I really appreciate the effort you've put into this. Unfortunately we don't have any infrastructure setup to handle translations. E.g. there's no way to let people know if the translated documentation is out-of-date so that they might be seeing an old version or we need additional contributions to update it. We'd have to figure out that tooling issue first before accepting any translations and it would make more sense to do that in SvelteKit than in Sapper which is no longer being worked on.