-
-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing non-English subdomains #472
Comments
Possibly via some cunning usage of https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions ? |
I looked in to this in #448. If you want subdomains on GH Pages then you do have to have a repository for each one. I would instead recommend refactoring the whole site so everything is served from subdirectories instead. Then set up the subdomains to send 301 Permanently Moved. That will need to be hosted off github. DNS providers usually have a way to set it up for free. |
Subdirectories makes a lot of sense, I'll have to look into that. Would definitely prefer the whole thing to be automatic and uncomplicated. |
You can always use the BASE HREF trick to make the usage of subdirectories easier. |
As per pinout-xyz/pinout-2024#1 and unless we figure out otherwise, translations will not be a going concern of Pinout in future. |
I had to do an emergency migration from AWS to GitHub pages a while back, and decided to stick with pages since it drastically simplifies my stack and workflow.
However, all of the non-English subdomains have been broken.
I'm not really sure how to fix this in GitHub pages, but I think in practice the only solution is to have individual GitHub (pages content only) repositories for each language which can be populated by the CI in #462 ... somehow.
The text was updated successfully, but these errors were encountered: