Feature request: remove i18n script

[BuckyBuck135]

Originally planned for the v3 release, I lacked time to implement a working solution for a script that would remove the i18n system from the kit, allowing for single-language project. This would make this kit an all-rounder.

The issues I ran into were:

• conflicts with other scripts, especially as they might not be run, or run in a different order, leaving the codebase in an unpredictable state. The i18n set up is intricate with a lot of moving parts.
• functions like getLocalizedRoute() need a locale to work: the script must either 1. keep an array of locales, even if only 1 locale in it, or 2. remove all instances of getLocalizedRoute() for normal hrefs
• LanguageSelect component needs locales to work: the script must either 1.keep an array of locales, and conditionally render the component based on number of locales 2. remove all instances of the component

Objective: update the i18n config script so that it allows for the scaffolding of a single-language project.

If anyone wants to contribute, please be my guest!

[jeroenhabets]

My sites are always multi-lingual... Will a i18n version keep on being maintained?

If not, this is an anti-feature for me (N=1)

[BuckyBuck135]

Hi @jeroenhabets,
Yes, the i18n kit will keep being maintained. The objective of this additional script is to eventually make this kit the one-stop-shop for Astro CodeStitch. If this kit can manage multi and mono lingual sites, and have all the features of the other kits, I will be able to archive the beginner and intermediate kits. Less maintenance work.
Hope this answers your question.

[jeroenhabets]

Ah, so it is rather: "make i18n script optional"

[BuckyBuck135]

Ah, so it is rather: "make i18n script optional"

Not quite.
The kit will still be i18n with 2 languages by default. Those who want to use the kit for 1 language only will be able to run the remove-i18n script which will strip away all the i18n features from the fork.