Get the website live at our URL

[Frijol]

Don't do until the rest of the "Website live" milestone is done.. but maybe throw some docs in here

[Frijol]

Seems pretty straightforward: https://docs.github.com/en/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site

Note that it's important to configure CNAME on the Github side before on the DNS side for security reasons.

[Frijol]

Also do https://github.com/edgi-govdata-archiving/EEW-Website/issues/139 when doing this, do by 10/13 at latest

[Frijol]

Looks like routing should be ok on live site per https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages/about-custom-domains-and-github-pages

We'll be using an apex domain

Using an apex domain for your GitHub Pages site An apex domain is a custom domain that does not contain a subdomain, such as example.com. Apex domains are also known as base, bare, naked, root apex, or zone apex domains.

An apex domain is configured with an A, ALIAS, or ANAME record through your DNS provider. For more information, see "Managing a custom domain for your GitHub Pages site."

If you are using an apex domain as your custom domain, we recommend also setting up a www subdomain. If you configure the correct records for each domain type through your DNS provider, GitHub Pages will automatically create redirects between the domains. For example, if you configure www.example.com as your custom domain for your site, and you have ALIAS and CNAME records set up for the apex and www domains, then example.com will redirect to www.example.com. For more information, see "Managing a custom domain for your GitHub Pages site."

Note: DNS changes can take up to 24 hours to propagate.

Here are the specific directions for what I will need to do: https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain

[Frijol]

after much ado..