To make the blog work with i18n features, I had to jump through a few hoops. One of the side effects were the addition of permalink and mappingKey fields for the blog entries.
Permalink allows for localized slugs (they get computed at build time), and mappingKey allows the LanguageSwitcher to find its translated counterpart.
It works, but it adds friction to the blog editing experience.
One constraint: even with the permalink field, Decap will always create identical file names, based on the default locale. No way around that.
Objectives: I think the permalink field is unavoidable, but the mappingKey one can probably be derived automatically from the title or the filename somehow. If we can avoid having it in the Decap admin UI, while preserving the functionality, that'd be great.
Open for PRs!
To make the blog work with i18n features, I had to jump through a few hoops. One of the side effects were the addition of permalink and mappingKey fields for the blog entries.
Permalink allows for localized slugs (they get computed at build time), and mappingKey allows the LanguageSwitcher to find its translated counterpart.
It works, but it adds friction to the blog editing experience.
One constraint: even with the permalink field, Decap will always create identical file names, based on the default locale. No way around that.
Objectives: I think the permalink field is unavoidable, but the mappingKey one can probably be derived automatically from the title or the filename somehow. If we can avoid having it in the Decap admin UI, while preserving the functionality, that'd be great.
Open for PRs!