Feature: use-case example for a standard multilingual site

[ain]

Pushing another idea for a documentation feature.

Currently the rough example case puts files into the distribution folders as per tasks defined in Gruntfile.

In real-life scenario though, it's often desirable to have a single template-base and publish it to different langauges automatically. Also given, that it'd be nice to have it automatically populated based on i18n.json, in the circumstances. So the distribution structure would be:

dist
  |
  – en
    |
    –– index.html
    |
    –– about.html
    |
    –– contact.html
  |
  – de
    |
    –– index.html
    |
    –– about.html
    |
    –– contact.html

and so on.

I think it would make a whole lot of sense to produce an example based on this scenario.

[davidyezsetz]

+ 1

[LaurentGoderre]

In a real scenario though, in the German section would not necessarily have English names.

I agree though that we should have an option between separate folders or file suffix

[ain]

I'd combine it with the permalinks plugin. Should be doable and smarter.

[LaurentGoderre]

Fair enough. We'll add it in

[jonschlinkert]

I'd combine it with the permalinks plugin. Should be doable and smarter.

Indeed, the permalinks plugin would make this easy I think. Especially since you can use lodash templates for variables in the front-matter, then use those variables to build the destination paths dynamically. e.g

In the front-matter:

---
foo: <%= bar %>
---

and in the config:

assemble: {
  site: {
    options: {
      permalinks: {
        structure: ':foo/:basename:ext'
      }
    },
    files: []
  }
}

[ain]

@jonschlinkert great stuff, thanks for the comment! I'll play around and probably come back with some additional ideas/reports.

[jonschlinkert]

👍

[LaurentGoderre]

I'm really impressed by the collective effort! @doowb what is the plan for this? There's a strong push in my project to adopt this ASAP

[kristoferjoseph]

🍻 This is the exact output structure I am looking for as well.
One template
Many language JSON files
One output directory for each language

[LaurentGoderre]

I think we can close this since it is covered by permalinks?

[jonschlinkert]

Agreed, I'll close. Please reopen if it seems this isn't resolved.

[ain]

Note: we should still create reasonable README with this in mind so devs can pick up the permalinks reference from there. It'll save a few tickets in the long run, I'm sure.

[jonschlinkert]

yeah I think a good readme will be important.