i18n and translations using only one file per page #695

<!-- Please don't delete this template or we'll close your issue -->

<!-- Before creating an issue please make sure you are using the latest version of Saber. -->

Feature request

<!-- Please ask questions via following several ways. -->

<!-- https://chat.saber.land/ -->

<!-- https://stackoverflow.com/questions/ask?tags=saberjs -->

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!