i18n(de): translate index.mdx

[trueberryless]

Description

• Initial translation of en/index.mdx into German language

Summary by CodeRabbit

• Documentation
  • Introduced a German documentation page for StudioCMS. It provides quick start instructions for setting up and developing projects, including organized sections with resource links covering SDKs, REST API details, plugin information, and environment configuration guides. The page also features a video introduction and invites community engagement via a Discord channel for support and collaboration.

[coderabbitai]

Walkthrough

A new German documentation file for StudioCMS has been added. The file provides relevant metadata and structures the content using various UI components. It features a hero section with attributes like a tagline and image links, a welcome card with a YouTube video component, and a CardGrid layout that organizes content into SplitCard and ListCard elements. These components include quick start instructions, shell commands for creating an Astro project, links to further documentation, and a community engagement section.

Changes

File	Change Summary
src/.../de/index.mdx	New documentation file for StudioCMS in German. Contains metadata, a hero section, a welcome card with an embedded YouTube video, and a CardGrid layout with SplitCard and ListCard components for commands, resource links, and community engagement.

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

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 plan to trigger planning for file edits and PR creation.
• @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
de/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: 0

🧹 Nitpick comments (1)

src/content/docs/de/index.mdx (1)

74-88: Center Component Highlights Community Engagement
The <Center> component wraps a flex container that centers the call-to-action button for joining the StudioCMS Discord community. While the inline styles achieve the desired layout, consider extracting them into a CSS class in the future for better reusability and maintainability.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 807b02e and c24c86a.

📒 Files selected for processing (1)

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

🔇 Additional comments (7)

src/content/docs/de/index.mdx (7)

1-22: YAML Front Matter is Well-Structured
The metadata block is clearly defined and includes all the necessary keys (such as i18nReady, title, description, etc.). The relative asset paths and boolean values (e.g., editUrl: false, lastUpdated: false) appear intentional and correct.

---

24-30: Import Statements are Clear and Consistent
The import statements properly bring in UI components from both the package (@astrojs/starlight/components) and local modules. The use of the module alias (studiocms:ui/components) is consistent with the project’s configuration.

---

31-33: Card Component with YouTube Integration Looks Good
The <Card> component is used appropriately to encapsulate the welcome message along with the embedded YouTube video. The usage of properties (like title and icon) is clear and aligns with expected UI component conventions.

---

35-55: SplitCard Section Provides a Clear Quick-Start Guide
The <SplitCard> component effectively presents a shell code snippet with proper syntax highlighting (```sh). The inline HTML <div> for additional instructions is neatly integrated. This section delivers concise and actionable quick-start instructions.

---

56-62: First ListCard Section is Well Organized
The use of the {/* prettier-ignore */} comment along with the <ListCard> component renders the list of Markdown links (e.g., [Erste Schritte], [Umgebungsvariablen]) clearly. This section aids in navigating to further resources seamlessly.

---

64-70: Second ListCard Section Effectively Presents Customization Options
This block, similar to the first ListCard, cleanly presents documentation links related to customizing StudioCMS via Markdown links. The formatting and structure are consistent and easy to follow.

---

90-100: Markdown Link Definitions are Correct and Consistent
The final section of the file defines Markdown links for navigation. The URLs appear consistent with the localized routing (using /de/ paths) and ensure that internal documentation links will resolve correctly.

[louisescher]

LGTM! Just going to let the workflows finish, then this can be merged 🚢