Aymeric Pineau

@auscaster

Declare your content in .content files anywhere in your codebase If of course works for server rebdered pages and islands You can duplicate keys, intlayer will merge the content, and remove unused content a build time

Thanks @sayedtanzeel5121472

@hussamsi Its exacly the purpose

I see many stack using classic i18n lib + headless CMS + Fumadoc etc. It becomes quickly a mess to administrate

• Remote / locale content
• json / markdown

All managed in one place, typed as it should, and editable visually

Multilingual content -> Intlayer

Thanks @myroslavrepin Feel free too share the win regarding your page size and reactivity!

@ts6056085 You can structure your content by component like for a navbar that will be nutualized across all pages But as well by secion of your page, by page or be used in a centralized way if you have an existing app using older solution, intlayer will purge and log unused keys for all pages to keep your page as light as possible

thanks @chillscanapp

@feedminus47 sure everythink is hardly typed thanks to autogenerated types

No need manual module augmentation like used to require next-intl, i18next etc

@theexonexo plurialisation is of course supported, I invite you to check out the doc. Same for locale fallback, its deduced at build time to avoid content leakage from your base locale

@nanoairun sure intlayer support centralized json supporting ICU / PO / i18next / vue-i18n formats

Awesome. Does it work for indexing the markdown files of a documentation? how can it be plugged in a github repo ?

Always great for social proof and seo ranking, I will try it out

I seems a really great tool for blog management too. Can we pick the agent to plug ?