Website Maintenance


The church website is hosted by but maintained through a private git repository on as illustrated in the diagram below.

Church Website Maintenance Overview

Church Website Maintenance Overview

In order to make changes to the website, you must first be granted access to the private repository. Once you have been given access, the procedure to modify the website is as follows:


  1. Install a git client:
    • On Windows, Mac, and Linux, provides the graphical user inerface Sourcetree to manage git repositories.
    • On Mac and Linux, the git command is sufficient to manage git repositories.
  2. Install the hugo command, available for Windows, Mac, and Linux. This will allow you to preview your website changes before pblishing them.
  3. You will need to clone (make a full copy of) the website repository onto your laptop/workstation as indicated by arrow #1 in the diagram above:
    • The graphical Sourcetree client provides dialogues to achieve this task.
    • The command “git clone <repository>” will clone the repository to the current directory.

Making Changes

The website is composed of markdown content, static files, and themes arranged in a directory structure. In order to make changes, you will need a much deeper understanding of the organization. It is recommended that you make a test website of your own by following the quick start guide on the hugo website. For a more detailed description of directory/file layout, again we refer you to the hugo documentation.

Procedure for Making Changes

  1. As indicated by arrow #1, retrieve any changes to the repository by issuing a “pull” request, either through the Sourcetree clint or the git command.
  2. Within the directory containing your copy of the website repository, start the hugo server with the command “hugo server -D”. By pointing your web browser to “http://localhost:1313", you will able to see the church website served by your laptop/wprkstation. Any changes made by you to the local repository will be instantly viewable through your web browser.
  3. Create or modify content files.
  4. Commit each change that you have completed and previewed.
  5. When all the changes that you wish to make have been committed, push your updates to the bibucket repository (as indicated by arrow #2 in the diagram above).

How does it get online?

  1. The process is automatic.
  2. Every 20 minutes, the web server checks for changes on the repository, and will regenerate the static content when found.