i18n(ko-KR): create included-integrations.mdx

[jsparkdev]

Description

create included-integrations.mdx

Summary by CodeRabbit

• Documentation
  • Added a new Korean documentation page explaining the configuration and usage of the robots.txt integration option, including detailed examples and available settings.

[coderabbitai]

Walkthrough

A new Korean-language documentation page has been added to the StudioCMS configuration reference. The page explains the includedIntegrations configuration option, with a focus on the robotsTXT property. It details how to enable or customize the robots.txt file generation using boolean values or a configuration object, provides example configurations, and documents the structure and options available for robotsTXT, including the RobotsConfig interface and its properties.

Changes

File(s)	Change Summary
src/content/docs/ko/config-reference/included-integrations.mdx	Added a new Korean documentation page detailing the includedIntegrations option, specifically the robotsTXT property, with examples and interface documentation.

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/config-reference/included-integrations.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: 0

🧹 Nitpick comments (3)

src/content/docs/ko/config-reference/included-integrations.mdx (3)

9-10: Remove unused ReadMore import or integrate its usage
The ReadMore component is imported but never rendered in this file. To clean up warnings, either remove the import:

-import ReadMore from '~/components/ReadMore.astro';

or add a <ReadMore> call (e.g. linking back to the English docs) if you intended to use it.

---

11-11: Convert standalone text into a proper heading
Line 11 reads as a paragraph but functions like a section title. Consider changing to a markdown heading, for example:

-StudioCMS 통합 구성 옵션 스키마 참조
+## StudioCMS 통합 구성 옵션 스키마 참조

This will improve navigability and styling consistency.

---

42-42: Align heading depth for RobotsConfig
Under “Usage” (###) you’re introducing a sub-section; H4 (####) may be more appropriate than H5 (#####). For example:

-##### `RobotsConfig`
+#### `RobotsConfig`

This keeps the hierarchy consistent.

📜 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 a6550bd.

📒 Files selected for processing (1)

• src/content/docs/ko/config-reference/included-integrations.mdx (1 hunks)

🔇 Additional comments (5)

src/content/docs/ko/config-reference/included-integrations.mdx (5)

1-7: Add explicit locale front matter for i18n consistency
Currently only i18nReady: true is set. Some other Korean MDX pages also include an explicit i18n: 'ko-KR' field in the front matter. Please verify against existing i18n docs and align to ensure the page is picked up correctly.

---

13-21: Code example matches English reference — looks good
The first ts twoslash snippet correctly demonstrates the minimal setup for includedIntegrations.robotsTXT. No issues found here.

---

23-28: Property description is clear and accurate
The translation of type (부울), default value, and link to RobotsConfig is precise and matches the English docs.

---

32-40: Usage snippet is accurate
The example with {3} slicing is consistent with the pattern in other pages and clearly shows the default robotsTXT: true usage.

---

44-56: Interface definition is correct — no changes needed
The RobotsConfig interface fields and types correctly mirror the API and English docs.