Conversation
Dokploy Preview Deployment
|
Contributor
📝 WalkthroughWalkthroughUpdates Spanish docs: adds a "Guías de Frontend Personalizado" subsection, adjusts frontmatter/sidebar visibility on upgrade guides, restructures CLI docs to use a PackageManagers component and adds a migrate command, and reorganizes how-it-works module and route listings. No executable code changes. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
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. Comment |
Member
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/es/guides/index.mdx`:
- Around line 18-21: The link "Renderizando Contenido" in
src/content/docs/es/guides/index.mdx points to a non-existent page
/es/guides/custom-frontend/rendering/; either remove this list item or add a
Spanish translation by creating the directory guides/custom-frontend and a
rendering.mdx translated from
src/content/docs/en/guides/custom-frontend/rendering.mdx (ensure frontmatter,
slug, and internal links match the /es path), then update the index entry to
point to the new file.
In `@src/content/docs/es/how-it-works/cli.mdx`:
- Around line 263-275: The package.json script name in step 2
("migrate-studiocms") does not match the PackageManagers component's pkg prop in
step 3 (currently "studiocms-migrator"), causing a "script not found" error; fix
by aligning them—either rename the script in the JSON to "studiocms-migrator" or
update the PackageManagers component's pkg prop to "migrate-studiocms" so the
script name and the PackageManagers pkg value match (refer to the package.json
"migrate-studiocms" script and the <PackageManagers pkg="..."> prop).
- Around line 259-278: Add the missing Steps import and remove the unused Tabs
and TabItem imports so the ES file's imports match the English version (update
the import statement that currently references Tabs/TabItem to only import
Steps); then fix the script name mismatch between the package.json example and
the PackageManagers run call by making them consistent—either change the script
key "migrate-studiocms" to "studiocms-migrator" or change the PackageManagers
call pkg="studiocms-migrator" to pkg="migrate-studiocms" (ensure PackageManagers
and the package.json script name refer to the same token), and apply the same
alignment to the English file if it has the same discrepancy.
In `@src/content/docs/es/how-it-works/index.mdx`:
- Around line 109-110: Replace the English abbreviation "e.g." with the Spanish
idiom "p. ej." in the two endpoint descriptions for
**`/studiocms_api/auth/[provider]`** and
**`/studiocms_api/auth/[provider]/callback`** so the Spanish translation uses
"p. ej." (por ejemplo) instead of "e.g." in both parenthetical examples.
Contributor
There was a problem hiding this comment.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@src/content/docs/es/how-it-works/cli.mdx`:
- Around line 12-13: Import the missing Steps component and remove the unused
Tabs and TabItem imports to match the English source and restore build parity:
add an import for Steps (the component used at lines where <Steps> appears)
alongside the existing PackageManagers import, delete the Tabs and TabItem
import from '@astrojs/starlight/components' since they are unused, and add the
missing trailing semicolon after the PackageManagers import to satisfy static
analysis.
- Around line 277-290: The guide has a script-name mismatch: the package.json
script is added as "migrate-studiocms" but the PackageManagers component renders
pkg="studiocms-migrator", causing a "script not found" error; fix it by updating
the PackageManagers prop (pkg) to "migrate-studiocms" so it matches the script
name (or alternatively rename the script in the JSON to
"studiocms-migrator")—locate the PackageManagers usage in this doc and align its
pkg attribute with the "migrate-studiocms" script declared in the JSON block.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/es/how-it-works/index.mdx`:
- Around line 109-110: Replace the informal Spanish abbreviation "ej." with the
standard "p. ej." in the two documentation lines that mention the authentication
endpoints (the lines containing "/studiocms_api/auth/[provider]" and
"/studiocms_api/auth/[provider]/callback"), ensuring both occurrences are
updated to "p. ej." to match canonical Spanish technical style.
Adammatthiesen
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
What does this PR change? Give us a brief description.
Updates the following spanish docs with upstream:
Summary by CodeRabbit