Turn off internationalization

[ebon gale]

I have an Astro site using the Starlight integration. Starlight causes the following error: "[WARN] [content] The i18n collection is defined but no content/i18n folder exists in the content directory. Create a new folder for the collection, or check your content configuration file for typos." What is the proper way too avoid this error? Should I comment out i18n: defineCollection({ type: 'data', schema: i18nSchema() }), in the config.ts file in the contents directory?

[visual wraith]

Hi @ebon gale. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

Based on the information provided in the extracts, it seems like the error you're encountering is due to the absence of a corresponding i18n folder in your content directory. This folder is expected because you have defined an i18n collection in your config.ts file.

If you're not using internationalization (i18n) features in your Astro project, you can indeed comment out or remove the i18n: defineCollection({ type: 'data', schema: i18nSchema() }) line in your config.ts file. This should prevent Astro from looking for an i18n folder and thus avoid the warning message.

However, please note that this is a general suggestion based on the information available in the extracts. Always ensure to test changes in a controlled environment before deploying them to your live site. If you encounter further issues, consider referring to the Astro documentation (https://docs.astro.build) or the Astro GitHub issues (https://github.com/withastro/astro/issues) for more specific guidance.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: