Website Go-Live Checklist

Modified on Wed, 23 Apr at 5:03 PM

TODO: review these notes


Realize that the following checklist is a guideline at a point in time in the development of the Web Engine CMS. It should ensure that the website is ready for launch. If you find anything missing, or in need of update, please contact the support team (web@adventist.cloud)

DATA IMPORT

  • Imports of data have been completed*:
    • [ ] ACMS
    • [ ] OrgMast
    • [ ] Users
    • [ ] Churches
    • [ ] Entities
    • [ ] Newsletter recipients

Not every data import will be needed for every project. Some data import may also be regularly scheduled under Scheduled Jobs below.

Scheduled Jobs

Verify with the support team (web@adventist.cloud) that any jobs required are setup and running correctly.

Articles Module

  • [ ] Module configuration has been reviewed/tested
  • [ ] Articles are appearing in the frontend

Course Module

  • [ ] Module configuration has been reviewed
    • [ ] Verify Provider Basic Information
    • [ ] Check provider configuration, are default advisors assigned?
    • [ ] Check the countries advisor setting
  • [ ] Course workflow tested in the frontend (students)
  • [ ] Course workflow tested in the backend (advisors)

Donation Module

  • [ ] Module configuration has been reviewed
  • [ ] Project donations tested in the frontend
  • [ ] Stripe is changed from Test to Production mode

Events Module

  • [ ] Module configuration has been reviewed
  • [ ] Events are appearing in the frontend

Media Library Module

  • [ ] Module configuration has been reviewed
  • [ ] Shows, Episodes, Hosts, Videos are appearing in the frontend (check all pages!)

Publication Module

  • [ ] Module configuration has been reviewed
  • [ ] Publications are appearing in the frontend

Web Module

Layout and design

  • [ ] Review all website pages for design, layout, and content
  • [ ] If the website has translations, the added languages need to be enabled, so that the language selection menu for the website will be visible
    • Web module > [website title] > Settings > Translations
    • Click on the "Actions" icon to the right of the language (the language opens for editing)
    • Click on the Danger Zone tab
    • Click on the "Enable" button
    • Confirm "Enable" button in the popup
    • Check the frontend for the language menu
    • Repeat for all website languages

SEO

  • [ ] All SEO work for the website is completed (see documentation)

Forms

  • [ ] Verify all Form email addresses are going to the correct person(s) or distribution lists
  • [ ] Verify any consent legal texts are in place

Feeds

  • Have the RSS feeds been setup for the website, and are these working correctly?

Newsletter

  • [ ] Test the running of the newsletter. Verify that all required data is in the newsletter and the layout is correct.
  • [ ] Newsletter recipients were checked?

ANALYTICS

  • Verify that any website analytics tools are in place and properly functioning.

Google

  • [ ] The Google Analytics account and setup are the responsibility of the partner for their own website.

Plausible

  • [ ] The built-in analytics module, if desired by the customer, should be verified as working.
  • [ ] Contact the support team (web@adventist.cloud) for assistance

Broken links

  • [ ] Verify the website has no broken links or navigation issues which will cause visitors problems when they are using the website.

DNS Changes for websites

  • !!! Make DNS changes only when the website is ready to go online.
  • Partner: Must have access to the control panel for the domain name
  • Web Engine support team can assist as needed with DNS changes if things are not working as expected.
  • Partner needs to update the DNS settings, on their DNS Control Panel, as per the Primary domain name under Website > Settings > General tab.
  • Follow the CName and A Record settings under "Important" section.

Website > Settings > General tab:

  • When DNS changes have been made, update the primary domain name to the final domain name.
  • Add any redirect domains

Disable or remove the robots.txt file

  • In the website pagetree look for a page with the name "robots.txt". It should be in the root of the pagetree.
  • Disable this page when the website is live in production. Otherwise the Search Engines will be told by the file to not index the website.

DNS Changes for custom backends

  • If backend access is to be configured: 
  • Create a CNAME record like manage.<your-main-domain-name.org> that points to hope-backend-prod-rzjsb.ondigitalocean.app
  • Ex:
  • manage.hopetv.org > hope-backend-prod-rzjsb.ondigitalocean.app

Backend (access):

  • On the Entity switcher, click on "Manage your entity"
  • Click on Configuration tab > Backend domains
  • Click on the "Add" button to add a backend domain
  • Domain: manage.<your-main-domain-name.org>
  • Ex:
    • manage.hopetv.org
  • Click on the "Update" button

Hope Channel App

  • Administrators need to configure this for the Hope Channel partners
  • If the partner wants to publish content on the Hope Channel App: 
  • Media Library > Channel (name) > Settings > App settings
    • [ ] Media Library
    • [ ] Collections
    • [ ] Livestream
    • [ ] Schedule

Podcasts

  • If the partner has podcasts, they should have created the accounts where they want to publish their content.
  • [ ] iTunes
  • [ ] Spotify
  • !!! if there are existing podcasts, check the URLs, as they may need to be changed.

Analytics & Tracking

  • After the website launch, if it is wished, the website can be added to the Google Search Console. This can be done by the partner, or a designated third party
  • [ ] Add Google Search Console parameter
  • [ ] Add sitemap to GSC new parameter
    • Ex: https://[your-domain-name]/sitemap.xml

Troubleshooting:

Manage Backend configuration

If there are issues with the manage backend, look for a domain name with extra www. For instance, this will need to be done via Vercel.com/accounts login and go to the region and then find the domain to fix.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article