Skip to content
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.

Sign up for GitHub

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

fix(blog): multilingual sites: reformat #22928

Closed
wants to merge 1 commit into from
Closed

fix(blog): multilingual sites: reformat #22928

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions docs/blog/2020-02-19-how-to-build-multilingual-sites-with-gatsby/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,8 +189,14 @@ createPage({

Apart from dynamic pages, there are always some static pages. They include `index.js` and `employees.js` that handle the homepage and employees page respectively. The `gatsby-plugin-i18n` will place them on the right language-specific URLs if you follow the defined language convention-the filename suffix needs to contain the language code.

- index.js -> index.en.js, index.cs.js
- employees.js -> employees.en.js, employees.cs.js
- `index.js` ->

- `index.en.js`
- `index.cs.js`

- `employees.js` ->
- `employees.en.js`
- `employees.cs.js`

It's also necessary to adjust the content of each of the new files to reflect its new language. That includes component properties. Take a look at this part of my index.js:

Expand Down