Skip to content
This repository has been archived by the owner on May 19, 2023. It is now read-only.

Using _episodes_es and _episodes in different repositories #11

Closed
rgaiacs opened this issue Nov 16, 2017 · 3 comments
Closed

Using _episodes_es and _episodes in different repositories #11

rgaiacs opened this issue Nov 16, 2017 · 3 comments

Comments

@rgaiacs
Copy link

rgaiacs commented Nov 16, 2017

This is a alternative to #10.

Replace _episodes with _episodes_es

In _config.yml, change

# Specify that things in the episodes collection should be output.
collections:
  episodes:
    output: true
    permalink: /:path/
  extras:
    output: true

# Set the default layout for things in the episodes collection.
defaults:
  - values:
      root: ..
  - scope:
      path: ""
      type: episodes
    values:
      layout: episode

to

# Specify that things in the episodes collection should be output.
collections:
  episodes_es:
    output: true
    permalink: /:path/
  extras:
    output: true

# Set the default layout for things in the episodes collection.
defaults:
  - values:
      root: ..
  - scope:
      path: ""
      type: episodes_es
    values:
      layout: episode

Translate _layouts and _includes

You need to replace episodes with episodes_es in all for-loops.

@jmbarrios
Copy link

@rgaiacs Do you propose to have more than a one _config.yml file?

It is possible: new command on Makefile to build the translated site

@rgaiacs
Copy link
Author

rgaiacs commented Nov 19, 2017

Do you propose to have more than a one _config.yml file?

No. You should have only one _config.yml.

It is possible: new command on Makefile to build the translated site

You won't need a new command.

@rgaiacs
Copy link
Author

rgaiacs commented Feb 23, 2018

I'm closing this because for now we will be doing the translation on their own repository.

@rgaiacs rgaiacs closed this as completed Feb 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants