Skip to content

i18n(ko-KR): update getting-started.mdx#98

Merged
Adammatthiesen merged 1 commit into
withstudiocms:mainfrom
jsparkdev:gs
Apr 20, 2025
Merged

i18n(ko-KR): update getting-started.mdx#98
Adammatthiesen merged 1 commit into
withstudiocms:mainfrom
jsparkdev:gs

Conversation

@jsparkdev
Copy link
Copy Markdown
Contributor

@jsparkdev jsparkdev commented Apr 20, 2025

Description

Summary by CodeRabbit

  • Documentation
    • Added a prominent link card to the StudioCMS upgrade guide.
    • Updated references to the self-hosted libSQL server to use consistent markdown links.
    • Changed example site URL to use studiocms.dev.
    • Added a new link reference for the self-hosted libSQL server guide.

@jsparkdev jsparkdev requested a review from a team as a code owner April 20, 2025 07:33
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 20, 2025

Walkthrough

The changes update the Korean "Getting Started" documentation by adding a prominent LinkCard at the top, which directs users to a StudioCMS upgrade guide. References to the self-hosted libSQL server are converted into markdown links, and the example URL for the astro.config.mjs configuration is updated. Additionally, a new markdown link reference is appended at the bottom of the document. No application logic or control flow is affected; all modifications are limited to documentation content and hyperlink formatting.

Changes

File(s) Change Summary
src/content/docs/ko/start-here/getting-started.mdx Added a LinkCard at the top linking to an upgrade guide; converted self-hosted libSQL references to markdown links; updated example URL; added link reference at document end.

Possibly related PRs

Suggested labels

i18n

Suggested reviewers

  • Adammatthiesen

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ec5e028 and 4ef01a8.

📒 Files selected for processing (1)
  • src/content/docs/ko/start-here/getting-started.mdx (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run Starlight Link Check
🔇 Additional comments (7)
src/content/docs/ko/start-here/getting-started.mdx (7)

11-11: Approve: Import LinkCard for new upgrade guide card
The addition of LinkCard to the component imports aligns with the new usage at the top of the doc.


15-15: Approve: Add upgrade guide LinkCard
The new LinkCard provides clear guidance to users on upgrading StudioCMS; the Korean text reads naturally and matches other locale styles.


23-23: Approve: Convert libSQL reference to markdown link
Replacing the plain-text “자체 호스팅 libSQL 서버” with a referenced link improves consistency and navigability.


28-28: Approve: Update second libSQL mention to use markdown link
The pattern is now consistent: every mention of 자체 호스팅 libSQL 서버 uses the [self-hosted-libsql] reference.


213-213: Approve: Clarify site option guidance
The parenthetical example including https://demo.studiocms.dev/ or http://localhost:4321/ accurately reflects the updated domain and local setup.


95-110:

Details

❓ Verification inconclusive

Verify: Consistency and correctness of updated demo domain
The site URL was updated from https://demo.studiocms.xyz/ to https://demo.studiocms.dev/ in three code snippets. Please confirm this new domain is correct, aligned with English docs, and reachable in all environments (e.g., staging, production).

Also applies to: 142-158, 191-207


🏁 Script executed:

#!/usr/bin/env bash
# Search for demo domain occurrences in docs
rg --color=always "https://demo.studiocms.dev" -n src/content/docs

Length of output: 5000


Verify demo domain correctness and consistency
Ripgrep confirms that https://demo.studiocms.dev/ has replaced the old .xyz URL across all language variants under src/content/docs (including getting-started.mdx, configuration.mdx, and web-vitals.mdx in EN, FR, ES, DE, and KO). Please ensure:

  • The .dev domain is the intended demo endpoint.
  • Your staging and production demo sites are updated to use this domain.
  • It’s publicly reachable (e.g., curl -I https://demo.studiocms.dev).

368-369: ⚠️ Potential issue

Fix: Remove duplicate link reference and validate new mapping
There are two identical [auth-config-ref] entries; the first should be retained, and the duplicate deleted. Also ensure the newly added [self-hosted-libsql] mapping is correct.

Suggested diff:

- [auth-config-ref]: /ko/config-reference/dashboard/#authconfig
  [self-hosted-libsql]: /ko/guides/database/sqld-server/

Likely an incorrect or invalid review comment.


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
🪧 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
Copy link
Copy Markdown
Member

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/getting-started.mdx Localization changed, 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.

@Adammatthiesen Adammatthiesen merged commit 31d1d80 into withstudiocms:main Apr 20, 2025
8 checks passed
@jsparkdev jsparkdev deleted the gs branch April 20, 2025 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants