feat: add links-validator and fix all broken links

[trueberryless]

Description

What title says

Summary by CodeRabbit

• New Features

  • Added a link validation plugin to improve internal link consistency and error detection.

• Documentation

  • Standardized internal documentation links to consistently use trailing slashes across Spanish pages.
  • Removed outdated or incorrect links and sections in Spanish documentation.
  • Corrected anchor text in the French documentation for improved accuracy.

• Chores

  • Added a new dependency for link validation to enhance project configuration.

[coderabbitai]

Walkthrough

This update introduces the starlightLinksValidator plugin into the Astro configuration with specific options and an exclusion pattern. Internal documentation links throughout the Spanish content are standardized to include trailing slashes, and some markdown link references are reformatted for consistency. A section referencing rendererConfig is removed from the Spanish configuration reference. Additionally, a hyperlink anchor text is corrected in the French documentation. The package.json is updated to add the new dependency starlight-links-validator without other dependency changes.

Changes

File(s)	Change Summary
astro.config.mts	Added import and configuration for starlightLinksValidator plugin with options and exclusions; updated sidebar topic links with trailing slashes.
package.json	Added new dependency "starlight-links-validator": "^0.16.0"; no other changes to dependencies.
src/content/docs/es/config-reference/index.mdx	Standardized internal links to include trailing slashes; removed the rendererConfig section.
src/content/docs/es/index.mdx	Updated internal links to include trailing slashes; removed a plugin-related link from a list.
src/content/docs/es/start-here/configuration.mdx	Removed parentheses from markdown link reference for [reference-page]; updated link target to /es/config-reference/.
src/content/docs/es/start-here/environment-variables.mdx	Removed parentheses from markdown link reference for [config-oauth]; updated link syntax accordingly.
src/content/docs/es/start-here/getting-started.mdx	Standardized internal link references by adding trailing slashes; updated OAuth-related link references and authentication configuration link.
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-devapps.mdx	Corrected hyperlink anchor text to match the actual anchor ID in the French documentation.

Sequence Diagram(s)

sequenceDiagram
    participant AstroConfig
    participant StarlightLinksValidator
    participant DocsContent

    AstroConfig->>StarlightLinksValidator: Initialize with options (errorOnFallbackPages, errorOnInconsistentLocale, exclude)
    AstroConfig->>DocsContent: Provide updated sidebar links with trailing slashes
    DocsContent-->>AstroConfig: Use standardized links in documentation

Loading

Possibly related PRs

• fix: broken link #54: Updates the [reference-page] link target in the same Spanish configuration markdown file, directly related to link reference changes.
• i18n(es): multiple updates pt.3 #31: Modifies markdown link references and trailing slashes in Spanish "start-here" documentation, overlapping with this PR's documentation link formatting changes.

Suggested reviewers

• dreyfus92
• Adammatthiesen

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 81fd28b and 0ca6341.

📒 Files selected for processing (2)

• astro.config.mts (4 hunks)
• package.json (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• package.json
• astro.config.mts

---

🪧 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 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 not trigger status changes.

Learn more

Lunaria automatically ignores changes on specific PRs by adding a ignored keyword in its title. Found: broken link.

You can change this by either removing the keyword above from the PR's title, or modifying the ignoreKeywords property in your Lunaria configuration file.

Tracked Files

Note

The notes below indicate what would happen if the pull request is merged when triggering status changes. Since a ignored keyword was found in the PR's title, the status changes indicated below won't be applied.

File	Note
es/config-reference/index.mdx	Localization changed, will be marked as complete.
es/index.mdx	Localization changed, will be marked as complete.
es/start-here/configuration.mdx	Localization changed, will be marked as complete.
es/start-here/environment-variables.mdx	Localization changed, will be marked as complete.
es/start-here/getting-started.mdx	Localization changed, will be marked as complete.
fr/package-catalog/studiocms-plugins/studiocms-devapps.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.

[Adammatthiesen]

Hey and the Coolify server didn't even throw a fit this time around!