Is there a plan to support internationalization? Or how to implement with the current version.

[noobnooc]

I want to implement internationalization for my website. The content layer of my website is using Velite. I want to know the best practice to implement internationalization with Velite. Or is there a plan to integrate the feature in Velite?

[zce]

Velite is just a content to data converter, it does not determine the structure of your content.

You can achieve this by either defining separate collections for different languages or adding a language field within a single content collection.

for example

const posts = defineCollection({
  name: 'Post',
  pattern: 'posts/**/*.md',
  schema: s
    .object({
      title: s.string(),
      lang: s.enum(['en', 'zh', 'fr']),  // <-----
      content: s.markdown()
    })
})

[noobnooc]

Thanks for the reply ❤️.

I added a language field for my posts, then the new problem is that I want keep the same slug for different language posts. Such as /en/posts/hello-world for English, and /zh/posts/hello-world for Chinese translation. My elite configuration is like the following:

const posts = defineCollection({
  name: "Post",
  pattern: "posts/**/*.md",
  schema: s
    .object({
      title: s.string().max(99),
      slug: s.slug("post"),
      lang,
    })
});

When both different languages using the same slug with this config, Velite will occur a warning information because the slug field treat all posts equally. Is there a way to use the lang field to distinguish the slug verification?

Thanks again for the work on this powerful tool.

[zce]

Then don't use s.slug() schema. You can see if s.path() can solve your needs,
or just s.string()

[IsmailJunior]

I want to implement internationalization for my website. The content layer of my website is using Velite. I want to know the best practice to implement internationalization with Velite. Or is there a plan to integrate the feature in Velite?

I have the same issue, Can you drop the full implementation please.

[noobnooc]

You can check the source code of my home page at https://github.com/noobnooc/nooc.me what with blog system that implemented internationalization. You can check the result in https://nooc.me with /en or /zh suffix.