Merge pull request 'Fix handling of https on backend calls. FE should be able to handle either' (#24) from hotfix/handle-https into develop

Reviewed-on: #24

app/templates/site-purpose.hbs

@@ -1,4 +1,35 @@
 <div class="container mt-5">
   <h2 class="mt-5">Website Purpose</h2>
-  <p class="mt-4">This website is designed to help Bible translators gain valuable insight into the meaning of the biblical text in its original languages. We recognize that formal training in the biblical languages is very limited and few people in the world have the ability to pursue this training. We also recognize that knowledge of the biblical languages helps people to produce more accurate Bible translations. In light of these truths, this website has been developed to give Bible translators access to information about the meaning of the Bible in its original languages. Because most Bible translators are non-native speakers of English, the content on this website is designed to be used by non-native speakers of English. All content has been produced using “writing for international translators”, which is a way of writing for non-native speakers of English that does not use overly technical or complex language.</p>
+  <hr>
+  <p>This website is designed to help Bible translators gain valuable insight into the meaning of the biblical text in its original languages. We recognize that formal training in of the biblical languages is very limited and few people in the world have the ability to pursue this training. We also recognize that knowledge of the biblical languages helps people to produce more accurate Bible translations. In light of these truths, this website has been developed to give Bible translators access to information about the meaning of the Bible in its original languages. Because most Bible translators are non-native speakers of English, the content on this website is designed to be used by non-native speakers of English. All content has been produced using “writing for international translators”, which is a way of writing for non-native speakers of English that does not use overly technical or complex language.</p>
+
+  <h2 class="mt-5">English and Greek Texts Used</h2>
+  <hr>
+  <h5 class="mt-3">English</h5>
+  <p>The English Bible used for this site is the Unlocked Literal Bible (ULB).<br>
+    The Unlocked Literal Bible is an open-licensed version of the Bible derived from 1901 The American Standard Version, and updated using the most reliable Hebrew, Aramaic, and Greek copies of the Biblical texts available. It is intended to accurately reflect the meanings of those texts and to be used as a source text for Bible translators to translate the Bible into their own language.</p>
+
+  <h5>Greek</h5>
+  <p>The Greek text used for this site is the Open Greek New Testament (OGNT).  This text is the result of the Open Greek New Testament Project. The goals of the Open Greek New Testament Project are to:</p>
+    <ul>
+      <li>offer <b>a FREE NA-equivalent text</b> of Greek New Testament, compiled from open-resources;</li>
+      <li>align <b>a FREE NA-equivalent Greek New Testament</b> with a group of high-quality and open-source materials;</li>
+      <li>develop an online reader for <b>FREE ACCESS</b> of major resources integrated in this project. [<a href="https://opengnt.com/" target="_blank">OpenGNT.com</a>]</li>
+    </ul>
+  <p>The text of OGNT was built upon and compiled from a group of high-quality scholarly materials. It serves as the base text for the rest of the project. This provides all bible readers, students or scholars a FREE text of Greek New Testament, which is the closest equivalent to the text of NA28 / NA27, for studies or research purposes.</p>
+
+  <p>As the text of OGNT is close to the text of NA28 / NA27, OGNT is a very good candidate for bridging a free Greek New Testament text with resources, which were originally keyed to the text of NA28 / NA27. So far, Open Greek New Testament Project has successfully aligned the text of OGNT with various scholarly resources, e.g. Tyndale Amalgamated NT Tagged texts, OpenText Linguisitic Annotations, Levinsohn Greek New Testament Features, Mounce Greek-English Dictionary, Berean interlinear translations, etc.</p>
+
+  <h5>The Latest Version (version 3) of the OGNT</h5>
+  <p>The latest base text of Open Greek New Testament Project was compiled from Berean Greek Bible and its associated database, which is primarily based on the Greek New Testament, Η ΚΑΙΝΗ ΔΙΑΘΗΚΗ, edited by Eberhard Nestle, published in 1904 by the British and Foreign Bible Society.</p>
+
+  <p>The Greek New Testament (Nestle, 1904) is now a public domain document worldwide, without any limitations for use or copyright issues. The Berean Bible Translation Committee adopted it years ago as the base text for developing the Berean Greek Bible and associated resources on New Testament.</p>
+
+  <p>The final text of the Berean Greek Bible is primary based on Nestle Greek New Testament (1904), with modernization of spellings and textual decisions reflecting the best and earliest manuscripts. In addition, Berean translation table marks some significant textual variants of popular critical Greek New Testament editions, with a set of symbols.</p>
+
+  <h2 class="mt-5">Purpose of the Lexicon Entries</h2>
+  <hr>
+  <p>The lexicon entries which display after selecting (clicking or tapping) a Greek word are intended to serve the needs of Mother-tongue translators and translation checkers and reviewers. It does this by providing the lexical meaning and other information about each word in the original language of the New Testament.  This lexicon is written in WIT (Writing for International Translators) style so that non-professional translators can more easily translate it into any of the world’s languages.  The Greek words are connected to their associated lexicon entries by Strong’s numbers. Because there are different numbering systems (even within Strong’s system), the Bible Translation Resources website follows the Strong’s numbering system that the Open Greek New Testament uses.</p>
+
+  <p>“Although the Greek words in Strong's Concordance are numbered 1–5624, the numbers 2717 and 3203–3302 are unassigned due to 'changes in the enumeration while in progress'. Not every distinct word is assigned a number, but rather only the root words. For example, αγαπησεις is assigned the same number as αγαπατε – both are listed as Greek word #25 in Strong's Concordance (αγαπαω).” [Source: Wikipedia]</p>
 </div>

config/environment.js

@@ -38,7 +38,7 @@ module.exports = function (environment) {
     ENV.APP.LOG_TRANSITIONS = true;
     ENV.APP.LOG_TRANSITIONS_INTERNAL = true;
     // ENV.APP.LOG_VIEW_LOOKUPS = true;
-    ENV.APP.hostUrl = 'http://backend.bibletranslationresources.org';
+    ENV.APP.hostUrl = 'http://gwt.api';
   }
 
   if (environment === 'test') {
@@ -55,13 +55,13 @@ module.exports = function (environment) {
 
   if (environment === 'production') {
     // here you can enable a production-specific feature
-    ENV.APP.hostUrl = 'http://backend.bibletranslationresources.org';
+    ENV.APP.hostUrl = 'https://backend.bibletranslationresources.org';
   }
 
   if (environment === 'staging') {
-    ENV.APP.hostUrl = 'http://backend.bibletranslationresources.org';
-    ENV.APP.rootURL = 'http://bibletranslationresources.org/test/current/';
-    ENV.APP.baseUrl = 'http://bibletranslationresources.org/test/current/';
+    ENV.APP.hostUrl = 'https://backend.bibletranslationresources.org';
+    ENV.APP.rootURL = 'https://bibletranslationresources.org/test/current/';
+    ENV.APP.baseUrl = 'https://bibletranslationresources.org/test/current/';
     ENV.APP.locationType = 'hash';
   }