# farmOS translation (i18n)

**URL:** <https://farmos.discourse.group/t/farmos-translation-i18n/91>\
**Category:** Development\
**Created:** [August 17, 2019, 5:36pm UTC](https://farmos.discourse.group/t/farmos-translation-i18n/91 "2019-08-17T17:36:33Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![jgaehring](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/jgaehring/32/927_2.png) [@jgaehring](https://farmos.discourse.group/u/jgaehring)\
**Post date:** [July 14, 2020, 9:29pm UTC](https://farmos.discourse.group/t/farmos-translation-i18n/91/29 "2020-07-14T21:29:36Z")

</div>

Great! I’ll whip up a branch with the beginnings for the i18n plugin tonight.

I assume you’re on GitHub? If you are, I think the best thing is for you to fork the `farmOS-client` repository, along with that branch (once its ready), and then as you make progress, we can merge your fork back into the official repo from time to time. I also think it would be great if we document this process in a GitHub issue for that repository, as a sort of guide for others who want to contribute translations.

And are you referring to this tutorial on developing farmOS?

> [@Video: Developing farmOS](https://farmos.discourse.group/t/video-developing-farmos/299):
>
> On the farmOS Monthly Call for April 2020, we recorded an overview of some of the ways that you can customize/modify farmOS. This is intended for advanced audiences and developers. This is “Part 1”, which covers a lot of the things that can be customized directly in the farmOS UI, without requiring code or custom module development. The intention is to cover those topics in “Part 2” on the May 2020 Monthly Call. Part 1: [https://youtu.be/V1oTO3QSSWY](https://youtu.be/V1oTO3QSSWY) Update Part 2: [https://youtu.be/iypN8X0Nf9k](https://youtu.be/iypN8X0Nf9k)

Just so you know, that will not be relevant to working in Field Kit, which is a separate codebase that merely connects to farmOS via API. It’s great stuff to dig into, as it gives you a sense of the overall architecture and how farmOS works, but probably won’t be of much help for providing Field Kit translations or working with the Vue plugin; that stuff will all be done in the Field Kit codebase.

I’m happy to do a walk-through of how Field Kit and Vue work. It’s all in JavaScript, but if you’ve had a some Python experience I think you should be able to pick up enough JS for what will be involved here. If you want to do that walk-through, just send me a direct message through the forum and we can coordinate a call.

---

_[View the full topic](https://farmos.discourse.group/t/farmos-translation-i18n/91)._