Skip to content

i18n(fr): add config-reference/dashboard.mdx#25

Merged
dreyfus92 merged 1 commit into
withstudiocms:mainfrom
ArmandPhilippot:i18n/fr-add-config-reference/dashboard.mdx
Mar 29, 2025
Merged

i18n(fr): add config-reference/dashboard.mdx#25
dreyfus92 merged 1 commit into
withstudiocms:mainfrom
ArmandPhilippot:i18n/fr-add-config-reference/dashboard.mdx

Conversation

@ArmandPhilippot
Copy link
Copy Markdown
Member

@ArmandPhilippot ArmandPhilippot commented Mar 28, 2025

Description

Adds the French translation of config-reference/dashboard.

Summary by CodeRabbit

  • Documentation
    • Introduced a comprehensive reference guide covering StudioCMS dashboard configuration options.
    • The guide details various settings including toggling the dashboard, custom routing, developer-specific adjustments, favicon setup, error route injection, version checks, and authentication configurations with usage examples.

@ArmandPhilippot ArmandPhilippot requested a review from a team as a code owner March 28, 2025 22:19
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 28, 2025

Walkthrough

A new documentation file has been added to the French documentation for StudioCMS. This file details the configuration options available for the dashboard, including settings for enabling the dashboard, route overrides, developer-specific configurations, favicon settings, 404 route injection, version checking, and authentication. The document employs YAML front matter to provide metadata such as title, description, and sidebar order.

Changes

File(s) Change Summary
src/content/docs/fr/.../dashboard.mdx Added documentation for the StudioCMS dashboard configuration options: dashboardEnabled, dashboardRouteOverride, developerConfig, faviconURL, inject404Route, versionCheck, and AuthConfig with sub-options (providers and usernameAndPasswordConfig).

Suggested labels

i18n

Suggested reviewers

  • Adammatthiesen

Poem

Oh, what a hop, what a joyful spree,
I, a little rabbit, code merrily.
Configurations bloom as I dart with cheer,
New docs for Dashboard, let’s give a cheer!
With booleans and strings, we dance in light,
Celebrating the changes with delight!
🐇✨


🪧 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
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
fr/config-reference/dashboard.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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/content/docs/fr/config-reference/dashboard.mdx (1)

9-9: Import Statement & Typographic Consistency
The import statement on line 9 is correct. Note that the static analysis hint mentioned a potential issue with French typographic spacing (une espace fine insécable) before the semicolon. Verify that your code style guidelines either allow or require adjusting the spacing in this context.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~9-9: Le point-virgule est précédé d’une espace fine insécable.
Context: ...adMore from '
/components/ReadMore.astro'; Référence du schéma des options de con...

(FRENCH_WHITESPACE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8d64a0f and f634fde.

📒 Files selected for processing (1)
  • src/content/docs/fr/config-reference/dashboard.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/fr/config-reference/dashboard.mdx

[uncategorized] ~9-9: Le point-virgule est précédé d’une espace fine insécable.
Context: ...adMore from '
/components/ReadMore.astro'; Référence du schéma des options de con...

(FRENCH_WHITESPACE)

🔇 Additional comments (13)
src/content/docs/fr/config-reference/dashboard.mdx (13)

1-7: YAML Front Matter is Well-Structured
The YAML section (lines 1–7) is properly formatted and clearly defines metadata (language readiness, title, description, sidebar order).


13-27: Configuration Code Block is Clear and Comprehensive
The embedded code example (lines 13–27) effectively shows how to use defineStudioCMSConfig with the dashboardConfig options. The snippet is well-formatted and demonstrates all the default settings clearly.


29-35: dashboardEnabled Section Provides Clear Documentation
The section (lines 29–35) clearly explains the purpose, type, and default value of dashboardEnabled. The explanation is precise and matches the example usage provided.


38-46: Usage Example for dashboardEnabled is Well-Illustrated
The usage snippet (lines 38–46) effectively demonstrates how to configure dashboardEnabled in the StudioCMS configuration. Using an inline comment for the default value is helpful.


48-65: DashboardRouteOverride Section is Clear and Consistent
The explanatory text (lines 48–54) along with the usage example (lines 55–65) correctly document the dashboardRouteOverride option. The clarity helps users understand how to override the default route.


67-83: Documentation for developerConfig is Informative
The developerConfig section (lines 67–83) clearly describes the configuration and provides a practical code example that shows additional developer settings (e.g., demoMode).


85-102: faviconURL Details are Clear and Consistent
The section for faviconURL (lines 85–102) accurately presents the type, default value, and example usage, making it easy for users to understand how to customize the favicon path.


104-121: inject404Route Section is Properly Documented
The description and usage example for inject404Route (lines 104–121) are clear, and the inline comment reinforces its default behavior.


123-140: versionCheck is Well-Explained
The versionCheck section (lines 123–140) contains a straightforward explanation and usage example that helps users understand its role in the configuration.


142-158: AuthConfig Initial Section is Clear
The section (lines 142–158) that introduces AuthConfig provides a concise explanation along with a usage example that clearly indicates how to enable authentication for the dashboard.


160-186: providers Configuration is Detailed and Helpful
The subsection on providers (lines 160–186) is detailed and includes multiple authentication provider options. The example effectively demonstrates the object structure required for configuring providers.


188-212: usernameAndPasswordConfig Section is Informative
This part (lines 188–212) clearly explains the settings for username and password configuration, and the usage example is easy for users to follow.


214-228: AuthProviders Type Definition is Clear and Accurate
The type definition for AuthProviders (lines 214–228) is well-documented. It accurately represents the expected properties for different authentication providers.

Comment thread src/content/docs/fr/config-reference/dashboard.mdx
@ArmandPhilippot
Copy link
Copy Markdown
Member Author

The import statement on line 9 is correct. Note that the static analysis hint mentioned a potential issue with French typographic spacing (une espace fine insécable) before the semicolon.

Oh, the addition of coderabbitai is nice! Well, here it's a false positive because it's an import but I'm glad to see that non-breaking spaces are taken into account!

@Adammatthiesen
Copy link
Copy Markdown
Member

The import statement on line 9 is correct. Note that the static analysis hint mentioned a potential issue with French typographic spacing (une espace fine insécable) before the semicolon.

Oh, the addition of coderabbitai is nice! Well, here it's a false positive because it's an import but I'm glad to see that non-breaking spaces are taken into account!

@ArmandPhilippot We are hoping to get onto their OSS free Pro plan once our 14 days expire, otherwise we will be sticking with their free version till we are able to get the OSS plan, definitely been fun to play with though!

@dreyfus92 dreyfus92 merged commit bf41481 into withstudiocms:main Mar 29, 2025
@ArmandPhilippot ArmandPhilippot deleted the i18n/fr-add-config-reference/dashboard.mdx branch March 29, 2025 10:55
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.

4 participants