diff --git a/docs/site/translation/miscellaneous-person-name-formats.md b/docs/site/translation/miscellaneous-person-name-formats.md
new file mode 100644
index 00000000000..6dc3d96daa6
--- /dev/null
+++ b/docs/site/translation/miscellaneous-person-name-formats.md
@@ -0,0 +1,21 @@
+---
+title: Person Name Guide
+---
+
+# Person Name Guide
+
+Please read through the [Person Names Guide](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit) while you are working on [/ Miscellaneous / Person Name Formats](https://st.unicode.org/cldr-apps/v#/USER/PersonNameFormats/).
+
+That guide is embedded below, but it may be easier just to open up the [Person Names Guide](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit) in a separate window, because the embedded window requires scrolling, and we can't link directly to sections in the document within this page.
+
+The main topics are:
+
+- [Version 44 Changes](https://cldr.unicode.org/translation/miscellaneous-person-name-formats) — *this section is important; please read carefully.*
+- [Why do we need formatting for people’s names?](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.wqpdugycqnvg)
+- [Starting out](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.q7f5rnykj886)
+- [Name Order For Locales](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.xquzeu24o1qf)
+- [AuxiliaryItems](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.b6xr0arybp08)
+- [Sample Name Fields For X](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.qr8y56vvjgr8)
+- [Name Patterns](https://docs.google.com/document/d/1mjxIHsb97Og8ub6BKWxOihcHz7zjU4GdFkIxWHGAtes/edit#heading=h.3me9x0ulvxtz)
+
+
\ No newline at end of file
diff --git a/docs/site/translation/time-zones-and-city-names.md b/docs/site/translation/time-zones-and-city-names.md
new file mode 100644
index 00000000000..5c80103d9ac
--- /dev/null
+++ b/docs/site/translation/time-zones-and-city-names.md
@@ -0,0 +1,79 @@
+---
+title: Time Zones and City names
+---
+
+# Time Zones and City names
+
+## Time Zone Names
+
+Time zones (such as "Pacific Time" or "France Time") can be formatted in different ways:
+
+- "metazone" names, such as "Pacific Time" or "Pacific Standard Time", that can apply to segments of a country or groups of countries.
+- location (country or city) based names, such as "Paris Time" or "Japan Standard Time"
+ - These are constructed using patterns (see below), plus [Country/Region Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names) and City Names.
+ - When a "metazone" name is absent, a location based name is used as a fallback.
+- raw offsets, like "GMT+10:00"
+ - These are constructed using patterns (see below).
+
+**Tips:**
+
+- When translating time zone names, include the Region information if the name can be ambiguous. For example, “Central time” would be ambiguous without the America\_Central region context.
+- When the English name can be ambiguous in your language, use the name that's most commonly used. For example, the English America\_Mountain "Mountain time" can be ambiguous and including "Rocky" may be most commonly understood in your language; thus the translation would be for "Rocky Mountain time".
+
+For each of the first two, there are three choices:
+
+- Winter (standard) time, such as "Atlantic Standard Time"
+- Summer (daylight) time, such as "Atlantic Daylight Time"
+- Generic time, such as "Atlantic Time". This is used for recurring times (such as in a Calendar program) that change between summer and winter.
+
+## Time Zone Patterns
+
+The following special patterns are used in formatting timezones.
+
+| Name | English Pattern | English_Example | Meaning | |
+|---|---|---|---|---|
+| gmtFormat | GMT{0}
*or*
GMT{ HOURS_FROM_GMT } | GMT -2:00 | **GMT Pattern.** Modify this field if the format for GMT time uses different letters, such as HUA+0200 for GMT+02:00 , or if the letters GMT occur after the time. Make sure you include the {0} ; that is where the actual time value will go! | |
+| gmtZeroFormat | GMT | GMT | **GMT Zero Pattern.** *This field must be consistent with the GMT Pattern.* | |
+| hourFormat | +HH:mm;-HH:mm | GMT -02:00 | **GMT Hours Pattern.** This field controls the format for the time used with the GMT Pattern. It contains two patterns separated by a ";". The first controls positive time values (and zero), and the second controls the negative values. So to get *GMT+02.00* for positive values, and *GMT-02.00* for negative values, you'd use *+HH.mm;-HH.mm*. | |
+| regionFormat | {0} Time
*or*
{ COUNTRY } Time / { CITY } Time | Bolivia Time | **Location-Based Time Zone Pattern.** For generic references to time zones, the country is used if possible, composed with a pattern that in English appears as "{0} **Time** ". Thus a time zone may appear as "Malaysia **Time** " or " **Hora de** Malasia". If the country has multiple time zones, then a city is used to distinguish which one, thus "Argentina (La Rioja) **Time** ".
Some languages would normally have grammatical adjustments depending on what the name of the city is. For example, one might need "12:43 pm **Tempo d'** Australia" but "12:43 pm **Tempo de** Paris". In that case, there are two approaches:
1. Use "{0}", which will give results like "12:43 pm Australia" and "12:43 pm Paris", or
2. Use a "form-style" phrasing such as " **Tempo de:** {0}", which will give results like "12:43 pm **Tempo de:** Australia" and "12:43 pm **Tempo de:** Paris". | |
+| regionFormat-standard | {0} Standard Time
*or*
{ COUNTRY } Standard Time / { CITY } Standard Time | Bolivia Standard Time | | |
+| regionFormat-daylight | {0} Daylight Time
*or*
{ COUNTRY } Daylight Time / { CITY } Daylight Time | Bolivia Daylight Time | | |
+| fallbackFormat | {1} ({0})
*or*
{ METAZONE_NAME } ({ CITY }) | Central Time ( Cancun ) | **Metazone Name with Location Pattern.** This field is usually not translated. This field to control the formatting of ambiguous metazone name name. When a set of metazone's generic names are shared by multiple different zones and GMT offset at the given time in a zone is different from other zones using the same metazone, this format pattern is used to distinguish the zone from others. In the pattern, {0} will be replaced by location name (either country or city) and {1} will be replaced with the metazone's name. | |
+
+## City Names
+
+Please choose the most neutral grammatical form of the city name. The city name will typically be used to indicate a timezone, either in a menu, or in formatting a time.
+
+In a few cases, what is included in the list of cities for translation is actually a country name, such as the following. In those cases, use the name of the country instead.
+
+- Costa Rica
+- Cape Verde
+- Faeroe (for the Faroe Islands)
+
+**Usage**
+
+A city may be used in a menu of timezone names, such as:
+
+- ...
+- United States Time (Los Angeles)
+- United States Time (New York)
+- United Kingdom Time (London)
+- ...
+
+Timezones may also have a simpler format, depending on the language, such as:
+
+- ...
+- United States (Los Angeles)
+- United States (New York)
+- United Kingdom (London)
+- ...
+
+The city name may also be used in formatted times, such as:
+
+- 12:51 AM France Time (Paris)
+
+**Unique Names**
+
+City names must be unique. See [Country/Region Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names) for techniques.
+
+
\ No newline at end of file
diff --git a/docs/site/translation/transforms.md b/docs/site/translation/transforms.md
new file mode 100644
index 00000000000..3bbd0f3f21d
--- /dev/null
+++ b/docs/site/translation/transforms.md
@@ -0,0 +1,37 @@
+---
+title: Transforms
+---
+
+# Transforms
+
+Transforms describe ways of converting text. Most often these are transliterations, converting one script to another, such as:
+
+| Source | Transliteration |
+|---|---|
+| キャンパス | kyanpasu |
+| Αλφαβητικός Κατάλογος | Alphabētikós Katálogos |
+| биологический | biologicheskij |
+
+For those, the name of the language or script is used.
+
+There are a few others that have special purposes, listed below. Note that whatever translation is used, it should be short (a few words at most).
+
+For the specialized acronyms (marked with \*):
+
+- If your language uses Latin letters, you probably want to leave this alone unless there is a well-known name in your language.
+- For non-Latin, you should transcribe this into your alphabet, and if the name is not commonly understood, add the English in parentheses, such as "XXX (BGN)" or "XXX (UNGEGN)".
+
+| Code | Description |
+|---|---|
+| BGN* | Transliterations according to the [US BGN](https://www.usgs.gov/us-board-on-geographic-names). |
+| UNGEGN* | Transliterations according to the [UN Group of Experts on Geographical Names](https://unstats.un.org/unsd/ungegn/). |
+| Numeric | Numeric conversions. |
+| Tone | Linguistic [tone](https://en.wikipedia.org/wiki/Tone_(linguistics)) such as used in Chinese. |
+| Accents | Accents, such as in ö or é. |
+| Publishing | Forms of characters more appropriate for publishing. Examples:
‘ or ’ or …
rather than generic ASCII characters like:
' or ... (three periods). |
+| Jamo | The name for the [units of the Korean alphabet](https://en.wikipedia.org/wiki/Jamo#Jamo). |
+| Pinyin | The name for the [standard romanization](https://en.wikipedia.org/wiki/Pinyin) (transliteration into Latin letters) for the Chinese language. |
+| Fullwidth | Full-width or "wide" characters, such as Ａ and ォ |
+| Halfwidth | Half-width or "narrow" characters, such as A and ｫ |
+
+
\ No newline at end of file
diff --git a/docs/site/translation/unique-translations.md b/docs/site/translation/unique-translations.md
new file mode 100644
index 00000000000..1ccb954f78d
--- /dev/null
+++ b/docs/site/translation/unique-translations.md
@@ -0,0 +1,13 @@
+---
+title: Unique Translations
+---
+
+# Unique Translations
+
+See the following based on the type of translation
+
+- [Points dots and pixels](https://cldr.unicode.org/translation/units/unit-names-and-patterns)
+- [Unique Emoji and Symbol Names](https://cldr.unicode.org/translation/characters/short-names-and-keywords)
+ - [Unique Names](https://cldr.unicode.org/translation/displaynames/countryregion-territory-names#h.xkmg2o42dw29) (This is on the Country/Region page, but is the most general discussion).
+
+
\ No newline at end of file