i18n(ko-KR): create why-studioCMS.mdx

[jsparkdev]

Description

create why-studioCMS.mdx

Summary by CodeRabbit

• Documentation
  • Added a new Korean-language page introducing StudioCMS, highlighting its features, integration with Astro, and benefits for both developers and non-technical users.

[coderabbitai]

Walkthrough

A new Korean-language documentation page, "왜 StudioCMS인가?" (Why StudioCMS?), has been added. This page introduces StudioCMS, outlines its features, and explains its advantages over Astro's default content management approach. The content includes an overview of StudioCMS's integration with Astro, its user-friendly features, and its ongoing development status. The page is structured with frontmatter metadata for localization and documentation organization.

Changes

File(s)	Change Summary
src/content/docs/ko/start-here/why-studioCMS.mdx	Added a new Korean documentation page describing the purpose, features, and advantages of StudioCMS.

Possibly related PRs

• i18n(ko-KR): update overrides.mdx #44: Updates Korean documentation for StudioCMS configuration overrides; both PRs focus on Korean documentation for StudioCMS but cover different topics.

Suggested labels

i18n

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/start-here/why-studioCMS.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/start-here/why-studioCMS.mdx (2)

9-13: Improve readability by splitting long sentences
The introduction paragraph contains very long, complex sentences which can be hard to follow—especially for non-technical readers. Consider breaking it into shorter sentences or adding line breaks for clarity.

---

17-29: Unify list punctuation and enhance link usage
The feature list mixes terminal punctuation (periods vs. exclamation marks). For consistency, standardize all items to end with a period (or exclamation, if that’s the chosen style).
Additionally, consider turning key terms like @astrojs/db and “WordPress 가져오기” into hyperlinks pointing to their official docs or relevant guides for quicker navigation.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a41ad1c and e9cdf2d.

📒 Files selected for processing (1)

• src/content/docs/ko/start-here/why-studioCMS.mdx (1 hunks)

🔇 Additional comments (1)

src/content/docs/ko/start-here/why-studioCMS.mdx (1)

15-15: Section header is well‑formatted
The ## 주요 기능 header correctly follows the markdown hierarchy and is clear to readers.