feat: init i10n ko-KR

src/ko/README.md

@@ -0,0 +1,85 @@
+---
+layout: Landing
+
+description: "Misskey는 오픈 소스인 탈중앙화된 소셜 미디어 플랫폼이며, 언제든 무료입니다!"
+gettingStarted: "시작하기!"
+learnMore: "더 알아보기"
+keyFeatures:
+  open:
+    title: "공개"
+    description: "Misskey는 누구든 기여할 수 있고 모두가 언제 어디에서나 사용할 수 있는 오픈 소스 소프트웨어입니다."
+  federated:
+    title: "연합"
+    description: "Misskey는 탈중앙화된 플랫폼으로, 서로 다른 인스턴스의 커뮤니티가 서로 연결될 수 있습니다."
+  multifunction:
+    title: "강력함"
+    description: "Misskey는 초보자들이 알기 쉽고 고급 사용자들을 위한 강력한 기능도 가지고 있습니다."
+  customizable:
+    title: "커스텀"
+    description: "Misskey를 당신의 것으로! 테마, 위젯, 레이아웃 등등으로, 여러분은 Misskey를 원하는 그대로 만들 수 있습니다."
+sections:
+  federatedSoftware:
+    title: "Misskey는 <b data-marker>탈중앙화된</b> 플랫폼입니다."
+    description: "Misskey는 자신의 인스턴스를 만드는 서버 운영자의 플랫폼일 뿐이며, 그 안에서 모두 서로 대화할 수 있습니다! 거대한 커뮤니티를 위한 인스턴스부터 그룹, 팬덤, 서브컬처, 심지어 개인과 친구들만을 위한 인스턴스도 있습니다. 더 많은 걸 조정하고 싶으신가요? 여러분을 염탐하거나 개인 정보를 팔려는 대기업과의 관계를 끊어내고 손쉽게 자신만의 인스턴스를 만들 수 있습니다. Misskey는 커뮤니티와 공유에 대한 것이지 대기업과 빅테크 기업을 위한 게 아니니까요. Misskey에 없는 친구가 있다고요? 걱정 마세요! Misskey는 연합 우주 (ActivityPub 기반) 위에 있어서, 마스토돈, PixelFed, PeerTube 등의 사람들과도 교류할 수 있습니다."
+  features:
+    title: "Features"
+    description: "Misskey has a wide variety of unique features!"
+    list:
+      note:
+        title: "Note"
+        description: 'On Misskey, posts from users are called "notes". Reply, quote, add custom emojis, animated text, content warnings, attach multiple images, videos, GIFs, audio clips, or anything else!'
+      reaction:
+        title: "Reactions"
+        description: "You can add emoji reactions to any post! No longer are you bound by a like button, show everyone exactly how you feel with the tap of a button."
+      theme:
+        title: "Theme"
+        description: "Why be limited by just a Light or Dark theme when you can change all the colors? Use Misskey's intuitive theming functions to make Misskey just how you like it."
+      charts:
+        title: "Charts"
+        description: "For those who need to see everything, Misskey has powerful charts for both users and admins to see what exactly is going on in your instance in real time."
+      federation:
+        title: "Federation"
+        description: "Not on Misskey? No problem! Not only can Misskey instances talk to each other, but you can make friends with people on other networks like Mastodon and Pixelfed!"
+      drive:
+        title: "Drive"
+        description: "Hate not being able to find something you uploaded? With Drive, you get managed and powerful cloud storage right in your social media!"
+      thread:
+        title: "Threads"
+        description: "Have a lot on your mind? Make a thread! Each post can have up to 3,000 characters by default, and you can keep the conversation going for hours."
+      widgets:
+        title: "Widgets"
+        description: "Have everything at your fingertips with over a dozen customizable widgets!"
+  gettingStarted:
+    title: "Join Misskey today!"
+    find:
+      title: "Find an instance!"
+      list: "List of instances"
+    create:
+      title: "Make your own instance"
+      guide: "Setup guide"
+    docs:
+      title: "Learn more"
+      docs: "See docs"
+  donation:
+    title: "Donation"
+    description: "Because Misskey is a non-profit, we rely on your donations to fund our development. If you like Misskey, please consider donating so that we can continue to make Misskey awesome for years to come!"
+  sponsors:
+    title: "Sponsors"
+---
+
+<!--
+<style>
+	.ai {
+		display: none;
+	}
+	.screenshot.desktop {
+		content: url("/screenshot-desktop-en.png");
+	}
+	.screenshot.mobile {
+		content: url("/screenshot-mobile-en.png");
+	}
+	.widgets {
+		content: url("/top-features-widgets-en.png");
+	}
+</style>
+-->

src/ko/appendix/assets.md

@@ -0,0 +1,51 @@
+---
+description: 'collection of Misskey logos, icons, and other assets.'
+---
+
+# Assets collection
+This is a collection of Misskey logos, icons, and other assets.
+
+
+::: tip
+These assets are free to use under the **CC BY-NC-SA** license!🎉
+
+<a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><img alt="CC BY-NC-SA" src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png" /></a>
+:::
+
+::: tip
+All assets are managed in [misskey-dev/assets](https://github.com/misskey-dev/assets).
+:::
+
+## Logo
+<a class="asset" href="https://raw.githubusercontent.com/misskey-dev/assets/main/misskey.svg" target="_blank" download>
+<img src="https://raw.githubusercontent.com/misskey-dev/assets/main/misskey.svg">
+</a>
+
+## Icon
+<a class="asset" href="https://raw.githubusercontent.com/misskey-dev/assets/main/icon.png" target="_blank" download>
+<img src="https://raw.githubusercontent.com/misskey-dev/assets/main/icon.png">
+</a>
+
+<style>
+.asset {
+	display: block;
+	background-color: #777;
+	background-image:
+		linear-gradient(45deg, #999 25%, transparent 25%),
+		linear-gradient(135deg, #999 25%, transparent 25%),
+		linear-gradient(45deg, transparent 75%, #999 75%),
+		linear-gradient(135deg, transparent 75%, #999 75%);
+	background-size: 25px 25px; /* Must be a square */
+	background-position: 0 0, 12.5px 0, 12.5px -12.5px, 0px 12.5px; /* Must be half of one side of the square */
+	animation: asset-bg 0.5s linear infinite;
+
+	margin: 1em 0;
+	padding: 16px;
+	text-align: center;
+}
+
+@keyframes asset-bg {
+  0% {background-position: 0 0, 12.5px 0, 12.5px -12.5px, 0px 12.5px;}
+  100% {background-position: 12.5px 12.5px, 25px 12.5px, 25px 0px, 12.5px 25px;}
+}
+</style>

src/ko/docs/admin/cdn.md

@@ -0,0 +1,17 @@
+# Set up a CDN
+When publishing your Misskey instance, we strongly recommend using a CDN such as [Cloudflare](https://www.cloudflare.com/).
+
+Using a CDN has the following advantages
+- You can have static content cached, which reduces the load on your server
+- The IP address of the server is less exposed, which can mitigate DoS attacks etc.
+
+## Caching
+Misskey Web is completely static and does not require a server to run. Therefore the whole Misskey Web can be cached in a CDN.
+The Misskey API cannot be cached.
+
+You need to configure the following settings in your CDN
+- Cache all requests except `/api/*`.
+
+::: tip
+You don't need to clear the cache when you update Misskey.
+::::

src/ko/docs/admin/default-reaction.md

@@ -0,0 +1,2 @@
+# Changing the default Reaction
+You can change the default reaction that is used when an ActivityPub "Like" is received from '👍' to '⭐' by changing the boolean value `meta.useStarForReactionFallback` in the databse respectively.

src/ko/docs/admin/emoji.md

@@ -0,0 +1,111 @@
+# Managing Custom Emoji
+
+Custom emoji can be managed by administrators or moderators by going to the instance settings and then the custom emoji submenu.
+By default you will see a list of the current locally installed emoji.
+At the start this list will be empty, but you can add custom emoji in different ways.
+
+## Copying Emoji from another Instance
+
+Emoji can be easily copied from another instance.
+To do this, switch to the "remote" tab in the custom emoji settings.
+You can search emoji by name and/or host they are from.
+
+When you have found an emoji you want, click it to open a small menu which will allow you to import the emoji.
+
+Please note that Emoji may be subject to copyright and you are responsible for checking whether you may legally use another emoji.
+
+## Individual Emoji Import
+
+If you have an image file that you would like to turn into a custom emoji you can import the image as an emoji.
+This works just like attaching files to a note:
+You can choose to upload a new file, pick a file from your Misskey drive or upload a file from another URL.
+
+::: danger
+When you import emoji from your drive, the file will remain inside your drive.
+Misskey does not make a copy of this file so if you delete it, the emoji will be broken.
+:::
+
+The emoji will be added to the instance and you will then be able to edit or delete it as usual.
+
+## Bulk Emoji import
+
+Emojis can be imported in bulk as packed ZIP files with a special format.
+This ability can be found in the three dots menu in the top right corner of the custom emoji menu.
+
+::: warning
+Bulk emoji import may overwrite existing emoji or otherwise mess up your instance.
+Be sure to only import emoji from trusted sources, ideally only ones you exported yourself.
+:::
+
+### Packed emoji format
+
+At the top level is a file called `meta.json` which contains information about the emoji contained in the packed file.
+A type definition for this file would look like this, where `Meta` is the structure of the whole file.
+
+```typescript
+class Meta {
+	metaVersion: number;
+	host: string;
+	/**
+	 * Date and time representation returned by ECMAScript `Date.prototype.toString`.
+	 */
+	exportedAt: string;
+	emojis: Emoji[];
+}
+
+class Emoji {
+	downloaded: boolean;
+	fileName: string;
+	emoji: {
+		id: string;
+		updatedAt: string;
+		name: string;
+		host: null;
+		category: string;
+		originalUrl: string;
+		publicUrl: string;
+		uri: null;
+		type: string;
+		aliases: string[];
+	};
+}
+```
+
+The fields of `Meta` are currently not used or checked when importing emoji, except for the `emojis` field.
+
+For each `Emoji`:
+- `downloaded`: should always be true. If the field is missing or not truthy, the emoji will not be imported.
+- `fileName`: name of the image file inside the packed file.
+- `emoji`: data associated with the emoji as it was stored in the database. Currently most of these fields are
+  not even checked for existence. The following are currently used:
+  - `name`: name of the emoji for the user, e.g. `blobfox` if a user should type in `:blobfox:` to get the emoji.
+    If a previous emoji with the same name exists, it **will be overwritten**!
+  - `category`: category of the emoji
+  - `aliases`: list of strings that should be added as aliases. The admin UI calls these "tags".
+
+## Editing and Deleting Emoji
+
+The properties of an emoji can be edited by clicking it in the list of local emoji.
+When you click on a custom emoji, a dialog for editing the properties will open.
+This dialog will also allow you to delete an emoji.
+
+::: danger
+When you delete a custom emoji, old notes that contain it will still have the text name of the emoji in it.
+The emoji will no longer be rendered correctly.
+:::
+
+Note that remote emoji can not be edited or deleted.
+
+Each emoji can have a name and a category and several tags.
+The category is used for structuring the emoji picker.
+Meanwhile the tags can be used as alternate names by which the emoji can be found when searching in the emoji picker.
+
+When you are done editing, save your changes by clicking the check mark in the top right corner of the dialog.
+
+### Bulk Editing
+
+Emoji can be edited in bulk by checking the box below the search field.
+With this enabled, clicking on an emoji will select it instead of opening the editing dialog.
+
+The Editing options will be displayed as buttons below the checkbox.
+To return to the normal behaviour just uncheck the box again.

src/ko/docs/admin/nginx.md

@@ -0,0 +1,87 @@
+# Nginx configuration
+1. Create `/etc/nginx/conf.d/misskey.conf` or `/etc/nginx/sites-available/misskey.conf` and copy the following example to the file.\
+   (The file name does not have to be "misskey".)
+2. Edit as follows:
+   1. Replace example.tld with the domain you have prepared.\
+     `ssl_certificate` and `ssl_certificate_key` should be the path to the certificate obtained from Let's Encrypt.
+	 2. If using a CDN such as Cloudflare, remove 4 lines from "If it's behind another reverse proxy or CDN, remove the following."
+3. If you create `/etc/nginx/sites-available/misskey.conf`, create symlink as `/etc/nginx/sites-enabled/misskey.conf`.\
+   `sudo ln -s /etc/nginx/sites-available/misskey.conf /etc/nginx/sites-enabled/misskey.conf`
+4. Run `sudo nginx -t` to verify that the configuration file will be loaded successfully.
+5. Run `sudo systemctl restart nginx` to restart nginx.
+
+# Nginx config example
+
+```nginx
+# For WebSocket
+map $http_upgrade $connection_upgrade {
+    default upgrade;
+    ''      close;
+}
+
+proxy_cache_path /tmp/nginx_cache levels=1:2 keys_zone=cache1:16m max_size=1g inactive=720m use_temp_path=off;
+
+server {
+    listen 80;
+    listen [::]:80;
+    server_name example.tld;
+
+    # For SSL domain validation
+    root /var/www/html;
+    location /.well-known/acme-challenge/ { allow all; }
+    location /.well-known/pki-validation/ { allow all; }
+    location / { return 301 https://$server_name$request_uri; }
+}
+
+server {
+    listen 443 ssl http2;
+    listen [::]:443 ssl http2;
+    server_name example.tld;
+
+    ssl_session_timeout 1d;
+    ssl_session_cache shared:ssl_session_cache:10m;
+    ssl_session_tickets off;
+
+    # To use Let's Encrypt certificate
+    ssl_certificate     /etc/letsencrypt/live/example.tld/fullchain.pem;
+    ssl_certificate_key /etc/letsencrypt/live/example.tld/privkey.pem;
+
+    # To use Debian/Ubuntu's self-signed certificate (For testing or before issuing a certificate)
+    #ssl_certificate     /etc/ssl/certs/ssl-cert-snakeoil.pem;
+    #ssl_certificate_key /etc/ssl/private/ssl-cert-snakeoil.key;
+
+    # SSL protocol settings
+    ssl_protocols TLSv1.2 TLSv1.3;
+    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
+    ssl_prefer_server_ciphers off;
+    ssl_stapling on;
+    ssl_stapling_verify on;
+
+    # Change to your upload limit
+    client_max_body_size 80m;
+
+    # Proxy to Node
+    location / {
+        proxy_pass http://127.0.0.1:3000;
+        proxy_set_header Host $host;
+        proxy_http_version 1.1;
+        proxy_redirect off;
+
+        # If it's behind another reverse proxy or CDN, remove the following.
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto https;
+
+        # For WebSocket
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection $connection_upgrade;
+
+        # Cache settings
+        proxy_cache cache1;
+        proxy_cache_lock on;
+        proxy_cache_use_stale updating;
+        proxy_force_ranges on;
+        add_header X-Cache $upstream_cache_status;
+    }
+}
+```

src/ko/docs/admin/push-docker-hub.md

@@ -0,0 +1,6 @@
+# How to use GitHub Actions to push to Docker Hub
+::: warning
+Sorry, this page is not translated yet. If you can, please edit this page to translate the [Japanese version](/docs/admin/push-docker-hub.md).
+
+Until then, try using a machine translator.
+:::

src/ko/docs/admin/troubleshooting.md

@@ -0,0 +1,7 @@
+# Troubleshooting guide
+
+::: warning
+Sorry, this page is not translated yet. If you can, please edit this page to translate the [Japanese version](/docs/admin/troubleshooting.html).
+
+Until then, try using a machine translator.
+:::