i18n(es): update more docs

[dreyfus92]

Description

• What does this PR change? Give us a brief description.
  Updates more outdated docs in spanish

Summary by CodeRabbit

• Documentation

  • Spanish docs updated for wording ("plugin" → "complemento"), clearer installation guidance, added informational asides and UI badges, and minor formatting/clarity improvements.

• Features

  • Plugin system redesigned to a hooks-based architecture, moving configuration to lifecycle hooks for integration, dashboard, frontend and rendering.

• Chores

  • Minimum StudioCMS version requirement raised to v0.1.0.

[htg-1-studiocms-cloud]

Dokploy Preview Deployment

Name	Status	Preview	Updated (UTC)
StudioCMS Docs	✅ Done	Preview URL	2026-02-19T18:54:53.757Z

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Documentation for Spanish StudioCMS plugins was updated: installation pages add dependency notes and wording changes; plugin API docs were rewritten from a property-based plugin object to a hooks-based plugin surface, examples and SDK usage updated, and minimum StudioCMS version bumped to 0.1.0.

Changes

Cohort / File(s)	Summary
Package catalog / installation pages src/content/docs/es/package-catalog/studiocms-plugins/studiocms-markdoc.mdx, src/content/docs/es/package-catalog/studiocms-plugins/studiocms-mdx.mdx, src/content/docs/es/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx	Added Aside import and dependency notes (mentioning @studiocms/md), adjusted Spanish wording ("plugin" → "complemento"), and clarified installation/configuration guidance and code snippets.
Plugin API and examples src/content/docs/es/plugins/index.mdx, src/content/docs/es/plugins/extended.mdx, src/dashboard-grid-items/MyPluginGridItem.astro	Replaced property-based plugin definition with a hooks-based API (studiocms:astro-config, studiocms:dashboard, studiocms:frontend, studiocms:rendering, etc.), updated examples to register integrations via hooks, bumped minimum version to 0.1.0, and migrated SDK usage to SDKCoreJs/runSDK and Astro.locals.routeMap.

Sequence Diagram(s)

mermaid
sequenceDiagram
participant Plugin as "Plugin\n(defines hooks)"
participant Core as "StudioCMS Core\n(hook dispatcher)"
participant Astro as "Astro\n(integration registration)"
participant Dashboard as "Dashboard\n(config)"
participant Frontend as "Frontend\n(config)"
participant Rendering as "Rendering\n(page types)"

Plugin->>Core: register 'studiocms:astro-config' hook
Core->>Astro: call hook -> addIntegrations(...)
Plugin->>Core: register 'studiocms:dashboard' hook
Core->>Dashboard: call hook -> set/augment dashboard
Plugin->>Core: register 'studiocms:frontend' hook
Core->>Frontend: call hook -> set frontend navigation
Plugin->>Core: register 'studiocms:rendering' hook
Core->>Rendering: call hook -> set page types / renderers

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• Update docs for Beta.19 update #139 — Implements hooks-based plugin API and updates SDK usage patterns (closely matches hooks migration).
• beta 18 docs #133 — Refactors plugin docs to the hooks model and updates examples (same code-level change).
• i18n(es): translate studiocms-markdoc, studiocms-mdx , and rendering.mdx documentation files #28 — Edits the same Spanish package-catalog plugin pages (installation and dependency notes).

Suggested reviewers

• Adimmatthiesen
• RATIU5
• louisescher

Poem

🐰
Un complemento salta y dice hola,
de props a hooks la senda desbroza,
en español brilla la documentación,
versión 0.1.0, nueva dirección,
¡brinco de alegría y mucha celebración! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'i18n(es): update more docs' is vague and overly broad. It does not clearly convey the specific nature of the significant structural changes to the plugin documentation (hooks-based API redesign), though it is broadly related to documentation updates in Spanish.	Consider a more specific title that reflects the substantial API changes, such as 'i18n(es): migrate plugin docs to hooks-based API' or similar, to better communicate the scope of changes to reviewers.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch es/update-005

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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
es/package-catalog/studiocms-plugins/studiocms-markdoc.mdx	Localization changed, will be marked as complete.
es/package-catalog/studiocms-plugins/studiocms-mdx.mdx	Localization changed, will be marked as complete.
es/package-catalog/studiocms-plugins/studiocms-wysiwyg.mdx	Localization changed, will be marked as complete.
es/plugins/extended.mdx	Localization changed, will be marked as complete.
es/plugins/index.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.

[coderabbitai]

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/package-catalog/studiocms-plugins/studiocms-markdoc.mdx`:
- Line 26: Update the wording to match sibling docs by changing the phrase "La
configuración debería incluir `@studiocms/markdoc`" to "La configuración de
StudioCMS debería incluir `@studiocms/markdoc`"; locate the exact string in this
file (studiocms-markdoc.mdx) and replace it so it mirrors the phrasing used in
studiocms-mdx.mdx and studiocms-wysiwyg.mdx for consistency.

In `@src/content/docs/es/plugins/extended.mdx`:
- Line 105: ReadMore copy contains the English word "Guide" at the end of the
Spanish sentence; update the ReadMore block text to use the Spanish translation
"Guía" (e.g., change "consulta el [Haciendo complementos
útiles][extended-plugins] Guide" to use "Guía") so the whole sentence is in
Spanish; look for the ReadMore element and the link identifier
[extended-plugins] in the file and replace the trailing "Guide" with "Guía".

In `@src/content/docs/es/plugins/index.mdx`:
- Around line 105-108: The ReadMore component text contains an untranslated
English word "Guide"; update the ReadMore string in this file so the trailing
"Guide" is translated to Spanish (e.g., "Guía") to read "Haciendo complementos
útiles | Guía" or similar; ensure the link reference [extended-plugins] remains
unchanged and that the ReadMore content uses the translated term.
- Line 28: The type definition currently uses the hook name string
'studiocms:astro:config' which mismatches the canonical hook used elsewhere;
update the type key in the declaration to 'studiocms:astro-config' so it matches
examples in index.mdx and extended.mdx and the rest of the docs (replace the
colon form with the hyphen form in the type definition).