Menú
Localized Markdown and MDX content guide for Better Translate projects.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Extract source strings, generate locale files, and remove unused keys for Better Translate projects.
Expo and React Native integration guide using Better Translate React support.
React and Expo integration guide for Better Translate providers, hooks, and typed translation access.
Package map and reading order for Better Translate product skills.
Guide for combining Better Translate packages without duplicating translation ownership.
Smallest Better Translate setup for plain TypeScript, Node.js, Bun, APIs, and shared libraries.
Basado en la clasificación ocupacional SOC
| name | md |
| description | Localized Markdown and MDX content guide for Better Translate projects. |
Use this guide when localized content lives in .md or .mdx files.
@better-translate/core@better-translate/mdThe core translator owns the locales.
@better-translate/md uses that same locale setup to find the right content file.
@better-translate/corecreateMarkdownHelpers()content/docs/
en/
getting-started.mdx
es/
getting-started.mdx
import { createMarkdownHelpers } from "@better-translate/md";
import { translator } from "./i18n";
export const docs = createMarkdownHelpers(translator, {
rootDir: "./content/docs",
});
const document = await docs.getDocument("getting-started", {
locale: "es",
});
Keep markdown helpers connected to the shared exported translator so locale inference stays aligned with the rest of the app.
Use @better-translate/md/server when the app already resolves locale per request and you want markdown loading to follow that request locale automatically.