This repository has been archived by the owner on Dec 12, 2024. It is now read-only.
fix[CI]: Added a new workflow and temporarily disabled i18n #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The main issue is still the same — Next.js (the underlying thing our doc theme uses) is very tough then it comes to combining i18n with static export as we do it now. That was the primary reason it took me whole 2 days to make it semi-right, but this time the fix is going to be very tough, because of this incompatibility. I'll try to look into it more, but at the moment I have a bold suggestion to move the docs to https://starlight.astro.build, as it's way easier to manage (I've tried already).
There's next-intl package, which may be nice with our setup, but will still require a ton of bike-shredding. In any case, I'll figure out a solution for keeping i18n and static exports.