Skip to content

Commit

Permalink
Point to new translation guide
Browse files Browse the repository at this point in the history
  • Loading branch information
agektmr committed Jul 6, 2016
1 parent bc455c0 commit 205156c
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 67 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ To access the staging site for a pull request:
1. Open the pull request on `github.com`.
2. Click **Show All Checks**.
3. Click **Details** next to the **Builder** check. The staging site opens
up in a new tab.
up in a new tab.

You can also access each staging site directly, using the following URL:

Expand All @@ -93,13 +93,13 @@ Staged branches are also available at:

<branch>-dot-weasel-dot-web-central.appspot.com

Where `<branch>` is the name of the branch.
Where `<branch>` is the name of the branch.

**The URL pattern for pull requests and branches may change without notice.**

# Translations

See [our translations guide](TRANSLATION.md)
See [our translations guide](https://developers.google.com/web/resources/translations/)

# Building Shows

Expand Down
65 changes: 1 addition & 64 deletions TRANSLATION.md
Original file line number Diff line number Diff line change
@@ -1,64 +1 @@
Translations
============

All article sources are in `src/content`. The base content is in English under the "en" directory. Add translations by following the same structure with either a two letter or composite language code: e.g. "es", "pt-br".

Update the build to include the language code in the `langs_available` variable in config/common.yml. For example, to add French:
```
langs_available: ["fr"]
```

Adding a translation
--------------------

1. Find the article in the original source language
2. Create the root language code in `src/content` if it does not exist for the language you
are translating. For example create `src/content/es` for Spanish.
3. Create the article in the same directory hierarchy but under this new directory.
4. Translate the article
5. Translate the article YAML metadata
1. Localize the title
2. Localize the description
3. Localize the introduction
4. Localize the notes (if present)
5. Localize the key-takeaways (the TLDR's if present).
6. Give yourself some credit by adding your details to the contributors file and add your
name to the "translators:" property.


Licence
-------

All of our content is Creative Commons 3.0. Contributions and translations are very much appreciated, however you must sign our [Contributor License Agreement](CONTRIBUTING.md) for the code to be pulled back in to the repository.

Credit
------

We want to make sure that you get the credit for the articles that you translate.

Add your details to `/src/content/_contributors.yaml` and add `- translator` to the `role` attriute. We use this information to populate our [contributors page](http://developers.google.com/web/fundamentals/resources/contributors) and also to attach your name to each article. For example:

paulkinlan:
name:
given: Paul
family: Kinlan
org:
name: Google
unit: Developer Relations
country: UK
role:
- author
- engineer
- translator
homepage: http://paul.kinlan.me
google: +PaulKinlan
twitter: paul_kinlan
email: [email protected]
description:
en: "Paul is a Developer Advocate"

For each article that you translate add your id to `translators:` property. For example

translators:
- paulkinlan
- petelepage
See [Translation guide](https://developers.google.com/web/resources/translations/) page.

0 comments on commit 205156c

Please sign in to comment.