CLDR-17566 fix getting rid of accidental changes

docs/site/index/cldr-presentations.md

@@ -0,0 +1,14 @@
+---
+title: Talks about CLDR
+---
+
+# Talks about CLDR
+
+### Unicode Conference #45
+
+October 2021
+- [Does [Device X] support my language?](https://docs.google.com/presentation/d/e/2PACX-1vQReKIgX1JdAjg1ExafpRoQLcYti124jp1hT0Fas4dE1p7z1QlUUWQTrdR2OPcSeiSZOd0b9DGEpUQH/pub)
+- [Inflection Points](https://docs.google.com/presentation/d/e/2PACX-1vQLTz0yBlMi7FPBaNLRUiz0VZru5P1rkd3YQev2_VPqM-0ZNoHKQpuF9ll9bO1ynBCraBFQfH8OIfXP/pub?start=false&loop=false&delayms=3000)
+- [CLDR and Person Names](https://docs.google.com/presentation/d/e/2PACX-1vQ3t_4YIjPzLsKoZLuQjRhiK4QHoKLzjTif9Fabxc0l34chRt9ff7V_8gnvQdCJ1w/pub)
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)

docs/site/index/cldr-spec.md

@@ -0,0 +1,17 @@
+---
+title: CLDR Specifications
+---
+
+# CLDR Specifications
+
+- [UTS #35: Unicode Locale Data Markup Language (LDML)](http://www.google.com/url?q=http%3A%2F%2Fwww.unicode.org%2Freports%2Ftr35%2F&sa=D&sntz=1&usg=AOvVaw3nQVa5S_8phVZOG1xv85Ie) is the specification of the XML format used for CLDR data, including the interpretation of the CLDR data.
+- [Definitions](https://cldr.unicode.org/index/cldr-spec/definitions) - common definitions used in CLDR
+- [Unicode Locale Extension (‘u’) for BCP 47](https://cldr.unicode.org/index/bcp47-extension) - an overview of the -u- extension
+- [CLDR Survey Tool](https://cldr.unicode.org/index/survey-tool) - how to use the Survey Tool
+- [Coverage Levels](https://www.google.com/url?q=https%3A%2F%2Fcldr.unicode.org%2Findex%2Fcldr-spec%2Fcoverage-levels&sa=D&sntz=1&usg=AOvVaw0k_LrECnZYzNCWCazI9c3c) - Detailed descriptions of the data required for a language to be considered supported at a specific level
+- [Unicode Transliteration Guidelines](https://cldr.unicode.org/index/cldr-spec/transliteration-guidelines) - how to design and use Unicode transliterators
+- [Picking the Right Language Identifier](https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code) - how to pick the right language code
+- [Collation Guidelines](https://cldr.unicode.org/index/cldr-spec/collation-guidelines) - how to construct collation rules
+- [JSON Bindings for CLDR Data](https://cldr.unicode.org/index/cldr-spec/cldr-json-bindings)
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)

docs/site/index/corrigenda.md

@@ -0,0 +1,18 @@
+---
+title: CLDR Releases/Downloads
+---
+
+# Corrigenda and Errata
+
+The Corrigenda and Errata are found on the corresponding release pages. Issues that can cause significant problems are considered corrigenda, and are listed on the corresponding release page. Problems that do not rise to the level of a corrigendum are considered errata, and are listed on the corresponding release page without being listed here. For example, errata for CLDR 1.9 may be found on [CLDR Release 1.9, Errata](https://cldr.unicode.org/index/downloads/cldr-1-9-release-note).
+
+At this time, there is only one Corrigendum:
+
+|   |   |
+|---|---|
+| **Corrigendum** | **Release** |
+| 1 | [CLDR 1.3 Release Note](/index/downloads/cldr-1-3-release-note) |
+
+Each release of CLDR is a stable release and may be used as reference material or cited as a normative reference by other specifications. Each version, once published, is absolutely stable and will never change. However, implementations may - and are encouraged to - apply fixes for corrigenda and errata to their use of an appropriate version. For example, an implementation may claim conformance to "CLDR 1.3, as amended by Corrigendum 1".
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)

docs/site/index/draft-schedule.md

@@ -0,0 +1,39 @@
+---
+title: Draft Schedule
+---
+
+# Draft Schedule
+
+1.  We are planning on a different process for the future, with the following changes: A consistent release schedule each year.
+2.  Two releases per year: Spring and Fall
+3.  Making the survey tool open most of the year.
+
+|  | Q2-Q3 Phase |  |  |
+|---|---|---|---|
+| Apr | Submission |  |  |
+| May | Submission |  |  |
+| Jun | Vetting |  |  |
+| Jul | Resolution |  |  |
+| Aug | Production | 15 | Final candidate tagged |
+| Sep | Production | 15 | Release |
+|  |  | 30 | Survey Tool updated |
+
+|  | Q4-Q1 Phase |  |  |
+|---|---|---|---|
+| Oct | Submission |  |  |
+| Nov | Submission |  |  |
+| Dec | Vetting |  |  |
+| Jan | Resolution |  |  |
+| Feb | Production | 15 | Final candidate tagged |
+| Mar | Production | 15 | Release |
+|  |  | 30 | Survey Tool updated |
+        
+
+The Spring release is intended to be less data-intensive, with a shorter vetting period because of the December holidays. The 2013 Spring release has just a limited internal data phase, because it needs to be shortened to adjust to the new schedule.
+
+Rather than having the Survey tool unavailable except during the Main Submission and Vetting periods, it would be available most of the year: It would be taken down during the Resolution phase, and occasionally for a week for updates or structural changes before the Main Submission phase. The two important periods for translators would be:
+
+-   Submission: translators are asked to flesh out missing data, and check for consistency. 
+-   Vetting: translators are asked to review all changed or conflicted values, and reach consensus.
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)

docs/site/index/json-format-data.md

@@ -0,0 +1,21 @@
+---
+title: JSON Format Data
+---
+
+# JSON Format Data
+
+**This page is out of date, see** [**CLDR Releases/Downloads: JSON Data**](https://www.google.com/url?q=https%3A%2F%2Fcldr.unicode.org%2Findex%2Fdownloads%23h.nosb01ot1guy&sa=D&sntz=1&usg=AOvVaw3XYfzHnHlYw0KHy-Or9-bW) **for details of the JSON data.**
+
+The CLDR Technical Committee is pleased to announce a preliminary publishing of the CLDR 22.1 main and supplemental data in JSON format.
+
+In 2011, the committee approved a specification for a standardized JSON format that can used to represent LDML data. Our hope is that by standardizing the format, it will be much easier for Javascript based applications to share and interchange data in this format, rather than having to invent a JSON format that is known only to the specific application.
+
+In addition, we now have a conversion utility that can be used to convert LDML into the JSON format, and this utility ( Ldml2JsonConverter ) will be published as part of the standard CLDR tools collection in the next release. We intend to enhance this utility to provide consumers a way to produce small subsets ( based on XPaths ) that are likely more useful than the full data set.
+
+The CLDR committee welcomes comments on this specification and the data itself. Our hope is that as more people realize that there is a standard format for CLDR data in JSON, it will become the best practice way to use CLDR data in the Javascript environment.
+
+The JSON specification for CLDR data can be found [here](https://cldr.unicode.org/index/cldr-spec/cldr-json-bindings).
+
+To access the CLDR 22.1 data in the JSON format, click [HERE](http://www.google.com/url?q=http%3A%2F%2Fwww.unicode.org%2Frepos%2Fcldr-aux%2Fjson%2F22.1%2F&sa=D&sntz=1&usg=AOvVaw3a81SHdsJi_Nf1zWGhF3rs)
+
+![Unicode copyright](https://www.unicode.org/img/hb_notice.gif)