Merge pull request #4 from cltk/v1-chs

V1 chs

Author: kylepjohnson

.gitignore

@@ -1,2 +1,3 @@
+.idea
 _site
 .sass-cache

_config.yml

@@ -8,7 +8,7 @@ url: "http://cltk.org" # the base hostname & protocol for your site
 #twitter_username: kyle_p_johnson
 github_username: cltk
 github_cltk: cltk/cltk
-copyright: Ⓒ 2019 Kyle P. Johnson
+copyright: Ⓒ 2021 Kyle P. Johnson
 
 # Build settings
 highlighter: rouge

_posts/2015-05-10-new-lemmatizer-greek-latin.markdown

@@ -12,9 +12,9 @@ With any lemmatizer, choices must be made about which headword to select in the
 
 The logic I use in the above algorithms is sound, however of course this will not be without flaws. I believe that the best way to improve these lemma-headword lists is to manually write corrections, which will be run over the automatically built file. Any corrections should be submitted to the [CLTK's issues tracker](https://github.com/kylepjohnson/cltk/issues).
 
-Docs for use of the Greek lemmatizer: <http://docs.cltk.org/en/latest/greek.html#lemmatization>
+Docs for use of the Greek lemmatizer: <http://legacy.cltk.org/en/latest/greek.html#lemmatization>
 
-Docs for use of the Latin lemmatizer: <http://docs.cltk.org/en/latest/latin.html#lemmatization>
+Docs for use of the Latin lemmatizer: <http://legacy.cltk.org/en/latest/latin.html#lemmatization>
 
 Code repository for making Greek lemma-headword list: <https://github.com/cltk/greek_lexica_perseus>
 

_posts/2015-07-11-new-latin-prosody-scanner.markdown

@@ -26,7 +26,7 @@ joseph.kirby12@ncf.edu
 
 # CLTK Docs
 
-Docs for Latin prosody module: <http://docs.cltk.org/en/latest/latin.html#prosody-scanning>.
+Docs for Latin prosody module: <http://legacy.cltk.org/en/latest/latin.html#prosody-scanning>.
 
 Code for Latin prosody module: <https://github.com/kylepjohnson/cltk/blob/master/cltk/prosody/latin/scanner.py>.
 

_posts/2015-08-02-tokenizing-latin-text.markdown

@@ -45,6 +45,6 @@ Using the CLTK WordTokenizer for Latin we retain the punctuation and split the s
 More on tokenization:
 
 * [Processing Raw Text in the NLTK book](http://www.nltk.org/book/ch03.html)
-* [CLTK documentation for WordTokenizer](http://docs.cltk.org/en/latest/latin.html#word-tokenization)
+* [CLTK documentation for WordTokenizer](http://legacy.cltk.org/en/latest/latin.html#word-tokenization)
 * [Text Mining Online](http://textminingonline.com/dive-into-nltk-part-ii-sentence-tokenize-and-word-tokenize)
 * [Text Analysis with Topic Models for the Humanities and Social Sciences](https://de.dariah.eu/tatom/preprocessing.html#tokenizing)

_posts/2015-08-02-updated-accuracies-pos-taggers.markdown

@@ -40,6 +40,6 @@ The testing corpus I had used, however, was considerably skewed. Essentially, th
 
 The TnT algorithm returns the best results at 83% accuracy for Greek and 70% for Latin. These are not bad scores, it seems to me, however they are something of a letdown from scores in the high 90's which I claimed earlier!
 
-To get the latest taggers, update your `greek_models_cltk` and `latin_models_cltk` files ([directions here](http://docs.cltk.org/en/latest/importing_corpora.html#importing-a-corpus)).
+To get the latest taggers, update your `greek_models_cltk` and `latin_models_cltk` files ([directions here](http://legacy.cltk.org/en/latest/importing_corpora.html#importing-a-corpus)).
 
 I give sincere thanks to Giuseppe and also apologize to anyone who was mislead by my mistake.

_posts/2016-03-27-analyzing-latin-clausulae.markdown

@@ -73,4 +73,4 @@ Type 5a | Cretic + Double Spondee | - u - / - - / - x
 Type 6 | Dactyl + Spondee | - u u / - x
 
 \\
-For more information, see [Clausulae analyses docs](http://docs.cltk.org/en/latest/latin.html#clausulae-analysis).
+For more information, see [Clausulae analyses docs](http://legacy.cltk.org/en/latest/latin.html#clausulae-analysis).

_posts/2017-03-01-cltk-google-summer-code.md

@@ -14,7 +14,7 @@ See our organization's [official GSoC page](https://summerofcode.withgoogle.com/
 
 > See our [Project ideas page](https://github.com/cltk/cltk/wiki/Project-ideas#gsoc-projects) for a list of GSOC tasks that are suited to three months' work for a beginning–to–intermediate programmer or language student. What follows is a high–level overview of these projects and a few tips in applying. Most work will be done in the Python and JavaScript languages, of which a beginner's or intermediate knowledge is expected.
 > 
-> If you know a Classical language that is not yet supported well by the CLTK (e.g., Hebrew, Sanskrit, Chinese), you may follow the pattern set by the current Greek and Latin libraries. See the Projects page on the wiki for ideas of what a good application will include. See also [the CLTK docs](http://docs.cltk.org) for what we can already do for a given language.
+> If you know a Classical language that is not yet supported well by the CLTK (e.g., Hebrew, Sanskrit, Chinese), you may follow the pattern set by the current Greek and Latin libraries. See the Projects page on the wiki for ideas of what a good application will include. See also [the CLTK docs](http://legacy.cltk.org) for what we can already do for a given language.
 > 
 > The other family of tasks regards the CLTK's in–development website, the Classical Language Archive ([in Meteor and React](https://github.com/cltk/cltk_frontend)) and API ([in Python's Flask framework](https://github.com/cltk/cltk_api_v2)). See our description of the frontend, experiment with the live demo, and explain in your application which functionality you would most like to see added, why, and how you will do so over the course of three months.
 > 

docs.md

@@ -1,5 +1,5 @@
 ---
-title: Docs (v0.1)
+title: Legacy Docs (v0.1.x)
 redirect_to:
-  - https://docs.cltk.org
+  - https://legacy.cltk.org
 ---

docs_v10.md

@@ -1,5 +1,5 @@
 ---
-title: Docs (v1.0)
+title: Docs
 redirect_to:
-  - https://dev.cltk.org
+  - https://docs.cltk.org
 ---