contentlayerdev / contentlayerdev/contentlayer

Support for localization (e.g. for Contentful)

Abierto
#14 12 comentarios 1 reacción 0 asignados Ver en GitHub
feature pkg/source-contentful
Lenguaje dominante
TypeScript
Estrellas
3.5k
Forks
192
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

While I guess that it is currently possible to localize MDX based on frontmatter tags, doing this would mean that the filenames would need to be different, resulting in different slugs which would certainly not be ideal. I guess there are other ways to achieve it, but none of them seem ideal, that's why it would be great to support l10n (and also just because Contentlayers goal is to be the abstraction layer between data and code).

I assume that there could be several ways for structuring the MDX files, but what comes to my mind first is either via file name eg. `/pages/about.mdx` `/pages/about.de.mdx` or via subfolders eg. `/pages/en/about.mdx` `/pages/de/about.mdx`.

Edit: the following structure seems pretty nice, but would depend on #11
```bash
├── data
│ ├── pages
│ │ ├── about
│ │ │ ├── index.mdx
│ │ │ ├── index.de.mdx
│ │ │ ├── picture.jpeg
│ │ ├── privacy
│ │ │ ├── index.mdx
│ │ │ ├── index.de.mdx
│ │ │ ├── cover.jpeg
```

For Contentful one just needs to add `&locale=` https://www.contentful.com/developers/docs/references/content-delivery-api/#/reference/localization

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.