-
Notifications
You must be signed in to change notification settings - Fork 972
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
fallback to default page for i18n #2659
Comments
That's not true? Only the sections require multiple files if you want them, not the pages. As for fallback, I don't think we can do it? The slug in the url might be different |
yes my bad, for every section we will need a new page. but still I think a fallback would be very convenient. because maybe I don't want to change some sections based on language and maintain two copies of the same page. |
And for another example, checkout the gallery page in my website.link I want the posts in my gallery to also be loaded in other languages, without copying about a hundred I'm not sure if this has another workaround or not, but I think the point is valid. I think the fallback behavior should be in a way that you can include or exclude pages or sections to use fallback in for example, I want all my gallery posts to fallback to I think this is a reasonable behavior. |
bump? |
Bug Report
for every language your site supports, for every page you MUST create a separate file for that language (https://www.getzola.org/documentation/content/multilingual/)
This leads to many redundant pages in some cases.
I purpose if for a language there is no
index.{code}.md
zola should just fallback toindex.md
, and maybe show a warning instead of not creating your website at all.for example see duckquill and how many redundant pages it has to have in itslef for no reason.
Environment
Zola version:
v0.19.2
Expected Behavior
I purpose if for a language there is no
index.{code}.md
zola should just fallback toindex.md
, and maybe show a warning instead of not creating the website at all.The text was updated successfully, but these errors were encountered: