Documentation

SiteConfig

The Admin. Panel links to a SiteConfig object, and this object contains the following three properties:

• Email: The e-mail address contact form submissions are sent to
• Plausible:
  • The unique identifier for your Plausible site
  • This defaults to our shared identifier and should be left as-is unless you wish to override it with a custom identifier
• Blog Enabled: When enabled, a Blog link will be added to the site's navigation
• Calendar Enabled: When enabled, a Calendar link will be added to the site's navigation

When a site is first created, we automatically set Email to the contact e-mail address we use to correspond with you. We also default Blog Enabled and Calendar Enabled to disabled. All three values can be updated by the site owner when they first log into the Admin. Panel.

Pages

Page objects represent content pages you publish on the church's site. All sites should have the following two pages, at minimum:

1. Home: The default index that displays when the church site is accessed
2. Contact: A page containing the church's address and phone number

These two pages get created by default and both should both exist at all times. For the Contact page, we automatically inject a feedback form into the content of the page. While you can explicitly list your e-mail address on your Contact page, this may subject your e-mail address to undesirable spam.

Typical examples of user-defined content pages include:

• Service Times: An outline of the church's services and service times
• Leadership: An outline of the church's leadership and staff
• Beliefs: An outline of the church's doctrine
• Sermons: Links to external sermons

The Page object contains the following fields:

• Title
  • The title of the page
  • The title is displayed as the header in the page content and in the metadata of the page
• Content
  • The content of the page
  • Markdown is supported in this field
• Slug
  • The URL used to access the page
  • For example, the slug for https://www.wateringcan.org/pages/documentation/ would be documentation
  • The slug value for the home page index must be home
  • The slug value for the contact page must be contact
• Order
  • The order value for the page dictates the ordering of the page in the site's navigation
  • Page order is sorted ascending; meaning, a page with an order of 100 will have its link displayed to the left of a page with an order of 200
• Enabled
  • When enabled, the page will get added to the site's navigation
  • When disabled, the page won't be in the navigation but will still be accessible when accessed directly

Posts

Post objects represent individual blog posts. Blog posts are displayed in the blog index sorted by the post creation date in descending order.

The Post object contains the following fields:

• Title
  • The title of the blog post
  • The title is displayed as the header in the blog post content and in the metadata of the page
• Content
  • The content of the blog post
  • Markdown is supported in this field
• Enabled
  • When enabled, the blog post will be visible in the blog's index
  • When disabled, the blog post won't be in the blog's index but will still be accessible when accessed directly

The blog's slug is generated automatically based on the title of the blog post. For example, if the blog's title is "Recommended sermons for you to listen to", the slug will get created as recommended-sermons-for-you-to-listen-to.

Events

Event objects represent calendar items. Clicking on a site's calendar loads calendar events for the current month. The current calendar's view includes links to the previous month's events as well as to the next's month's events.

The calendar is typically used for one-off events, rather than for recurring services.

The Event object contains the following fields:

• Title
  • The title of the event
  • The title is displayed as the header for the event
• Description
  • A description providing details of the event
• Date
  • The year, month, and day of the event
• Start
  • The start time of the event
• End
  • The end time of the event
• Enabled
  • When enabled, the event will be visible in the calendar
  • When disabled, the event won't be visible in the calendar