# Multi-language content

**URL:** <https://forum.ghost.org/t/multi-language-content/13791>\
**Category:** Developer help\
**Created:** [April 23, 2020, 7:09pm UTC](https://forum.ghost.org/t/multi-language-content/13791 "2020-04-23T19:09:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![trisul](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/trisul/32/7501_2.png) [@trisul](https://forum.ghost.org/u/trisul)\
**Post date:** [April 23, 2020, 7:09pm UTC](https://forum.ghost.org/t/multi-language-content/13791/1 "2020-04-23T19:09:14Z")

</div>

I’m looking at the tutorial for creating multi-language content.

[https://ghost.org/tutorials/multi-language-content/](https://ghost.org/tutorials/multi-language-content/)

I understand how to configure collections and routes for each language. However, what about the navigation menu content, that will also need to be different for each language. Should I change the Navigation Helper or is there an elegant way to do it?

Many thanks.

---

<div class="post-metadata">

**Author:** ![trisul](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/trisul/32/7501_2.png) [@trisul](https://forum.ghost.org/u/trisul)\
**Post date:** [April 26, 2020, 10:49am UTC](https://forum.ghost.org/t/multi-language-content/13791/3 "2020-04-26T10:49:52Z")

</div>

It seems to me that writing a custom navigation.hbs seems to be the solution.

The more I think about it, the less that whole tutorial makes sense to me. Using collections to partition posts by language breaks all the rules Ghost has set up internally … on home, author, tags etc. It probably makes more sense to keep the Ghost structure, tag by language and filter on those tags.

The only use case I can think of that makes sense with the approach from the tutorial is building a site e.g. in English with links to pages in other languages in the navigation menu. That’s neither a frequent nor a useful use case.
