Skip to content

Commit a425c61

Browse files
committed
Sun Aug 13 20:00:21 JST 2017
0 parents  commit a425c61

File tree

1 file changed

+59
-0
lines changed

1 file changed

+59
-0
lines changed

locale/en/index.md

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
layout: post
3+
title: Introducing GitLocalize, a continuous localization platform for GitHub repository
4+
languages:
5+
- ja
6+
image: gitlocalize.png
7+
---
8+
9+
We are excited to announce the beta launch of our new localization platform, [GitLocalize](https://gitlocalize.com)!
10+
11+
GitLocalize is a continuous localization platform for GitHub repositories and automates the process for developers. Because of the ever-changing nature of Internet-related product, keeping localizing them has been really challenging. GitLocalize solves this by connecting to your GitHub repository and naturally integrating with your development workflow in just a few clicks.
12+
13+
We started supporting from Markdown files. Try GitLocalize in a minute if you have a documentation project that you want to localize.
14+
15+
<a class="btn btn-hero" href="https://gitlocalize.com/auth/github">
16+
<i class="fa fa-github"></i><span style="margin-left: 6px;">Get started now with GitHub</span>
17+
</a>
18+
19+
# How it works
20+
21+
You can immediately get started with your GitHub account, choose your repository to integrate with GitLocalize and localize your files. Here are the key features of the platform:
22+
23+
### GitHub based workflow
24+
25+
![GitHub based workflow](/img/flow.png)
26+
27+
Once you integrate your repo with GitLocalize, it starts pulling all the localization related files into its platform and watching the changes.
28+
29+
When you finish translating a file, you then make a review request and ask the team to review the changes, like what you do with a pull request.
30+
31+
After the review process, you can send a pull request back to your repo. It makes each contribution on GitLocalize each user's commit on the repository.
32+
33+
With GitLocalize, your team no longer need to do anything extra to localize your project and developers only need to look at those pull request coming.
34+
35+
### Diff management on translations
36+
37+
![Diff management](/img/diff_management.png)
38+
39+
Since it automatically links a translation with its original sentence, it can show you which part needs to be translated when the original one is updated.
40+
41+
No need to manually check which parts are affected due to the original updated. You just need to look at GitLocalize editor and fill in the missing translations.
42+
43+
And of course, more features are lined up and will be shipped soon!
44+
45+
# More details
46+
47+
Check out the video below to see how it works in more depth!
48+
49+
<iframe src="https://www.youtube.com/embed/b09LDukIJiU" frameborder="0" allowfullscreen style="width: 100%; height: 500px"></iframe>
50+
51+
# Happy localizing!
52+
53+
We need your feedback to improve and bring the product to create the better future for localization. Please feel free to give us any feedbacks [here](https://gitlocalize.com/inquiries/new). We will respond within a day.
54+
55+
Also, we have [a Gitter channel](https://gitter.im/gitlocalize/Lobby?utm_source=share-link&utm_medium=link&utm_campaign=share-link) to chat. Feel free to join and jump into the conversation.
56+
57+
And of course, this blog is localized into [Japanese](http://blog.gitlocalize.com/ja/posts/introducing-gitlocalize.html) with GitLocalize, make a suggestion for the translation from [here](https://gitlocalize.com/repo/80).
58+
59+
We hope to make your localization far easier and smoother and support your product's global success! Happy localizing!

0 commit comments

Comments
 (0)