-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
i18n and translations using only one file per page #695
Comments
I'm rewriting Saber, so no new features for now, but I'll take this into consideration while working on the new version. |
Thanks for let me know! I would love to help, if possible.
…On Tue, Apr 13, 2021, 13:40 Kevin Hazy ***@***.***> wrote:
I'm rewriting Saber, so no new features for now, but I'll take this into
consideration while working on the new version.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#695 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM3I3ON3E3JSS6VZTNZNAUDTIRXYXANCNFSM423V2V5Q>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
What problem does this feature solve?
It will avoid duplication in the page structure, a much cleaner source and streamlined workflow
What does the proposed API look like?
How should this be implemented in your opinion?
I think the way NetlifyCMS deal with translations extremely clever: it allow for three different strategies - a folder structure for each language (as Saber currently offer), a file for each language inside the same folder (as Hugo page bundles) and just one file, with content separated by language level, under a i18n top-level tag.
I propose to follow the same direction, cause for websites with lots of languages and much content, it will be extremely cumbersome to replicate the very same structure for each locale.
Are you willing to work on this yourself?
Absolutely!
The text was updated successfully, but these errors were encountered: