feat: CI link validation for MDX content

.github/workflows/validate.yml

@@ -4,6 +4,9 @@ on:
   pull_request:
     branches: [main]
 
+permissions:
+  contents: read
+
 jobs:
   validate:
     name: Check for unsafe patterns
@@ -25,3 +28,23 @@ jobs:
             echo "::error::MDX files must not contain javascript: URLs."
             exit 1
           fi
+
+  validate-links:
+    name: Validate internal links
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+
+      - name: Install dependencies
+        working-directory: scripts
+        run: npm ci
+
+      - name: Validate links
+        working-directory: scripts
+        run: npx tsx validate-links.ts

.gitignore

@@ -0,0 +1 @@
+scripts/node_modules/

blog/en-US/plurals.mdx

@@ -99,7 +99,7 @@ Although developers often think that i18n libraries are only for multilingual in
 they can be very useful for plural and variable formatting even in single-language applications.
 Under the hood, most i18n libraries use JavaScript's built-in `Intl.PluralRules` API to determine the correct plural form for any language.
 
-There are plenty of React i18n libraries, including ours, [gt-react](/docs) (or [gt-next](/docs) if you're using Next.js).
+There are plenty of React i18n libraries, including ours, [gt-react](/docs/react) (or [gt-next](/docs/next) if you're using Next.js).
 Displaying an English plural using gt-react is simple:
 
 ```jsx

docs-templates/api/helpers/use-default-locale.mdx

@@ -13,9 +13,8 @@ This locale represents the fallback language for your app and is typically used
     Ensure your app is wrapped in a [`<GTProvider>`](__DOCS_PATH__/api/components/gtprovider).
 </Callout>
 
-See [`withGTConfig`](__DOCS_PATH__/api/config/with-gt-config) for configuration.
-If no default locale is specified in [`withGTConfig`](__DOCS_PATH__/api/config/with-gt-config), it defaults to `'en-US'`.
-For server-side, see [`getDefaultLocale`](__DOCS_PATH__/api/helpers/get-default-locale).
+See [`gt.config.json`](__DOCS_PATH__/api/config/gt-config-json) for configuration.
+If no default locale is specified, it defaults to `'en-US'`.
 
 ## Reference
 

docs-templates/api/helpers/use-locale-direction.mdx

@@ -12,7 +12,6 @@ The `useLocaleDirection` hook retrieves the text direction (`'ltr'` or `'rtl'`)
     Ensure your app is wrapped in a [`<GTProvider>`](__DOCS_PATH__/api/components/gtprovider).
 </Callout>
 
-For server-side usage, see [`getLocaleDirection`](__DOCS_PATH__/api/helpers/get-locale-direction).
 
 ## Reference
 
@@ -58,10 +57,8 @@ export default function SpecificDirection() {
 
 ## Notes
 
-- Unlike the server-side [`getLocaleDirection`](__DOCS_PATH__/api/helpers/get-locale-direction), this hook is always synchronous.
+- This hook is always synchronous.
 - Useful for setting the `dir` attribute on elements for RTL support.
 
 ## Next steps
 
-- Learn about RTL support in the [right-to-left guide](__DOCS_PATH__/guides/rtl).
-- See [`getLocaleDirection`](__DOCS_PATH__/api/helpers/get-locale-direction) for the server-side equivalent.

docs-templates/api/helpers/use-locale-properties.mdx

@@ -12,7 +12,6 @@ The `useLocaleProperties` hook returns metadata about a given locale, including
     Ensure your app is wrapped in a [`<GTProvider>`](__DOCS_PATH__/api/components/gtprovider).
 </Callout>
 
-For server-side usage, see [`getLocaleProperties`](__DOCS_PATH__/api/helpers/get-locale-properties).
 
 ## Reference
 
@@ -77,5 +76,4 @@ export default function LocaleInfo() {
 
 ## Next steps
 
-- See [`getLocaleProperties`](__DOCS_PATH__/api/helpers/get-locale-properties) for the server-side equivalent.
 - Learn more about [locale codes](/docs/core/locales).

docs-templates/api/helpers/use-locales.mdx

@@ -12,7 +12,6 @@ The `useLocales` hook retrieves the list of supported locales from the [`<GTProv
     Ensure your app is wrapped in a [`<GTProvider>`](__DOCS_PATH__/api/components/gtprovider).
 </Callout>
 
-For server-side usage, see [`getLocales`](__DOCS_PATH__/api/helpers/get-locales).
 
 ## Reference
 
@@ -47,9 +46,8 @@ export default function LocaleList() {
 ## Notes
 
 - The `useLocales` hook relies on the [`<GTProvider>`](__DOCS_PATH__/api/components/gtprovider) to access the context. Ensure your app is wrapped with a provider at the root level.
-- `useLocales` is client-side only. For server components, use [`getLocales`](__DOCS_PATH__/api/helpers/get-locales).
+- `useLocales` is client-side only. 
 
 ## Next steps
 
 - Learn how to configure supported locales in [`gt.config.json`](__DOCS_PATH__/api/config/gt-config-json).
-- See [`getLocales`](__DOCS_PATH__/api/helpers/get-locales) for the server-side equivalent.

docs-templates/api/helpers/use-region.mdx

@@ -12,7 +12,6 @@ The `useRegion` hook retrieves the user's currently selected region from the [`<
     Ensure your app is wrapped in a [`<GTProvider>`](__DOCS_PATH__/api/components/gtprovider).
 </Callout>
 
-For server-side usage, see [`getRegion`](__DOCS_PATH__/api/helpers/get-region).
 
 ## Reference
 
@@ -45,6 +44,5 @@ export default function RegionDisplay() {
 
 ## Next steps
 
-- See [`getRegion`](__DOCS_PATH__/api/helpers/get-region) for the server-side equivalent.
 - Use [`<RegionSelector>`](__DOCS_PATH__/api/components/region-selector) to let users choose their region.
 - Use [`useRegionSelector`](__DOCS_PATH__/api/helpers/use-region-selector) to build a custom region selector.

docs-templates/api/strings/msg.mdx

@@ -11,7 +11,7 @@ The `msg` function is a function that marks and encodes strings for translation.
 const encodedString = msg('Hello, world!');
 ```
 
-The encoded string should be passed to the [`useMessages`](__DOCS_PATH__/api/strings/use-messages) hook or [`getMessages`](__DOCS_PATH__/api/strings/get-messages) function to retrieve translations.
+The encoded string should be passed to the [`useMessages`](__DOCS_PATH__/api/strings/use-messages) hook to retrieve translations.
 
 <Callout>
 **Encoding:**
@@ -149,4 +149,3 @@ export default function TranslateGreeting() {
 
 ## Next steps
  * See [`useMessages`](__DOCS_PATH__/api/strings/use-messages) for translating strings.
- * See [`getMessages`](__DOCS_PATH__/api/strings/get-messages) for translating strings in async server-side components.

docs-templates/guides/shared-strings.mdx

@@ -112,7 +112,7 @@ function MyComponent() {
 
 ## Getting original strings with decodeMsg
 
-Sometimes you need to access the original string without translation, such as for logging, debugging, or comparisons. Use [`decodeMsg`](__DOCS_PATH__/api/strings/msg#decodemsg) to extract the original text:
+Sometimes you need to access the original string without translation, such as for logging, debugging, or comparisons. Use [`decodeMsg`](__DOCS_PATH__/api/strings/msg) to extract the original text:
 
 ```tsx
 import { decodeMsg } from '__PACKAGE_NAME__';