Skip to content

fix: replace Weblate with Crowdin in contributing/translations#27

Merged
dreyfus92 merged 2 commits into
withstudiocms:mainfrom
ArmandPhilippot:fix/contributing/translations
Mar 30, 2025
Merged

fix: replace Weblate with Crowdin in contributing/translations#27
dreyfus92 merged 2 commits into
withstudiocms:mainfrom
ArmandPhilippot:fix/contributing/translations

Conversation

@ArmandPhilippot
Copy link
Copy Markdown
Member

@ArmandPhilippot ArmandPhilippot commented Mar 29, 2025

Description

Since Crowdin is the new service used to manage translations, I replaced Weblate with Crowdin in contributing/translations (status, guide link and Weblate mentions).

Summary by CodeRabbit

  • Documentation
    • Updated translation documentation with a new status image reflecting the current platform.
    • Modified text to reference Crowdin while providing an updated guide link for translators.

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

coderabbitai Bot commented Mar 29, 2025

Walkthrough

The pull request updates the translation documentation. The translation status image has been replaced with one from Crowdin, and the text now references Crowdin instead of Weblate. An updated link to the Crowdin translator guide has been provided while the overall document structure remains unchanged.

Changes

File(s) Change Summary
src/content/docs/en/contributing/translations.mdx Replaced the translation status image source from StudioCMS i18n dashboard with one from Crowdin; updated text from "Weblate" to "Crowdin" and refreshed the translator guide link.

Suggested reviewers

  • Adammatthiesen
  • dreyfus92

Poem

I hopped along the docs with glee,
Changing images so bright to see.
From Weblate's name to Crowdin's call,
A little update for one and all.
With every line, my hops stand tall! 🐇


🪧 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

studiocms-no-reply commented Mar 29, 2025

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
en/contributing/translations.mdx Source changed, localizations will be marked as outdated.
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: 1

🧹 Nitpick comments (1)
src/content/docs/en/contributing/translations.mdx (1)

24-24: Stylistic Suggestion: Improve Clarity
Consider removing the word “would” for a more concise phrasing. For example, changing the sentence to “If you prefer to contribute translations directly to the repository…” makes it more direct.

Apply this diff:

-If you would prefer to contribute translations directly to the repository,
+If you prefer to contribute translations directly to the repository,
🧰 Tools
🪛 LanguageTool

[grammar] ~24-~24: Consider removing ‘would’. (Usually, ‘would’ does not occur in a conditional clause, unless to make a request or give a polite order.)
Context: ...an add it within the dashboard. If you would prefer to contribute translations directly to ...

(CONDITIONAL_CLAUSE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between df23f72 and ac893d3.

📒 Files selected for processing (1)
  • src/content/docs/en/contributing/translations.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/en/contributing/translations.mdx

[grammar] ~24-~24: Consider removing ‘would’. (Usually, ‘would’ does not occur in a conditional clause, unless to make a request or give a polite order.)
Context: ...an add it within the dashboard. If you would prefer to contribute translations directly to ...

(CONDITIONAL_CLAUSE)

🔇 Additional comments (1)
src/content/docs/en/contributing/translations.mdx (1)

20-21: Crowdin Status Badge Update Approved
The updated badge image URL reflects the new Crowdin translation status correctly.

Comment thread src/content/docs/en/contributing/translations.mdx Outdated
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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/en/contributing/translations.mdx (1)

34-34: Documentation Translation Status Message
The addition of the "Coming soon!" note along with the Discord link provides clarity on the upcoming translation efforts for the documentation. If possible, consider including an estimated timeline or next steps to inform contributors further.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ac893d3 and 3dce599.

📒 Files selected for processing (1)
  • src/content/docs/en/contributing/translations.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/en/contributing/translations.mdx

[grammar] ~24-~24: Consider removing ‘would’. (Usually, ‘would’ does not occur in a conditional clause, unless to make a request or give a polite order.)
Context: ...an add it within the dashboard. If you would prefer to contribute translations directly to ...

(CONDITIONAL_CLAUSE)

🔇 Additional comments (2)
src/content/docs/en/contributing/translations.mdx (2)

20-21: Crowdin Translation Badge Update
The updated badge image now correctly reflects the move to Crowdin by using the new Crowdin badge URL. This change aligns with the PR objective of replacing Weblate references.


26-28: Updated Translation Management Reference
The documentation now correctly states that StudioCMS uses Crowdin for managing translations, and the link to Crowdin’s "For Translators guide" (https://support.crowdin.com/for-translators/) is accurate. This update fulfills the intent of transitioning away from Weblate.

Copy link
Copy Markdown
Member

@Adammatthiesen Adammatthiesen left a comment

Choose a reason for hiding this comment

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

Thanks @ArmandPhilippot the image is fine for now, might look into seeing if i can do something custom using github or something in the future...

Copy link
Copy Markdown
Member

@dreyfus92 dreyfus92 left a comment

Choose a reason for hiding this comment

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

let's keep moving docs bois, gj 🫡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants