Repository navigation
Replies: 2 comments 3 replies
|
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()
})
}) |
2 replies
I have the same issue, Can you drop the full implementation please. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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?
All reactions