i18n(ko-KR): create guides/index.mdx

[jsparkdev]

Description

• StudioCMS Beta.16 release docs #73

Summary by CodeRabbit

• Documentation
  • Added a new Korean index page for guides and tutorials, featuring sections for contribution guides, upgrade guides, and database instructions, with links to relevant resources. The page includes Korean metadata and is ready for internationalization.

[coderabbitai]

Walkthrough

A new documentation index page for Korean guides and tutorials has been introduced. This page organizes links to various StudioCMS resources, including contribution guides, upgrade guides, and database instructions. It features metadata for internationalization, providing Korean titles and descriptions. The page serves as a central hub for accessing different Korean-language guides and is structured to facilitate navigation to specific documentation topics.

Changes

File(s)	Change Summary
src/content/docs/ko/guides/index.mdx	Added a new Korean documentation index page with sections and links to contribution, upgrade, and database guides; includes i18n metadata.

Sequence Diagram(s)

sequenceDiagram
    User->>Korean Guides Index Page: Access page
    Korean Guides Index Page->>Contribution Guide: Link to contribution guides
    Korean Guides Index Page->>Upgrade Guide: Link to release notes
    Korean Guides Index Page->>Database Guide: Link to self-hosting instructions

Loading

Possibly related PRs

• i18n(ko-KR): create code-contributions.mdx #86: Adds the specific Korean code contributions guide referenced by the new index page.
• i18n(ko-KR): create contributing/getting-started.mdx #78: Adds the Korean "getting-started" contribution guide linked from the new index.
• i18n(ko-KR): create translations.mdx #90: Introduces the Korean translation contribution guide, which is also linked from the new index.

Suggested reviewers

• Adammatthiesen

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[studiocms-no-reply]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
ko/guides/index.mdx	Localization added, will be marked as complete.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

src/content/docs/ko/guides/index.mdx (2)

9-11: Consistent indentation for markdown lists

The list under ## 기여 가이드 is indented by two spaces before each dash, but lists in other sections are flush left. Aligning indentation improves readability:

-  - [시작하기](/ko/guides/contributing/getting-started/) - StudioCMS에 기여하는 기본적인 방법을 알아봅니다.
-  - [코드 기여](/ko/guides/contributing/code-contributions/) - StudioCMS에 코드를 기여하는 방법을 알아봅니다.
-  - [번역](/ko/guides/contributing/translations/) - StudioCMS에 번역을 기여하는 방법을 알아봅니다.
+ - [시작하기](/ko/guides/contributing/getting-started/) - StudioCMS에 기여하는 기본적인 방법을 알아봅니다.
+ - [코드 기여](/ko/guides/contributing/code-contributions/) - StudioCMS에 코드를 기여하는 방법을 알아봅니다.
+ - [번역](/ko/guides/contributing/translations/) - StudioCMS에 번역을 기여하는 방법을 알아봅니다.

---

21-21: Add a trailing newline to the file

Ensure the file ends with a newline character to comply with POSIX standards and prevent potential CI warnings.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 31d1d80 and de0bf0e.

📒 Files selected for processing (1)

• src/content/docs/ko/guides/index.mdx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Run Starlight Link Check

🔇 Additional comments (1)

src/content/docs/ko/guides/index.mdx (1)

20-20: Verify the database guide link path

Please confirm that the URL /ko/guides/database/sqld-server/ matches the actual directory and filename in the repository. If the slug is incorrect (e.g., typo in sqld-server vs. libsql-server), it will lead to broken links in the Korean docs.