Changes Parish Editors Can Usually Make
Depending on your assigned role, routine content changes may include:
- Correcting text on approved pages.
- Publishing articles.
- Publishing sermons.
- Publishing featured Events.
- Updating the parish-owned external calendar.
- Adding approved photos.
- Correcting links, dates, biographies, and ministry information.
Changes to Send to BOTH/AND
Contact BOTH/AND before changing:
- The header, footer, or main navigation structure.
- Site-wide fonts, colors, spacing, or button styles.
- Templates, template parts, global styles, or style variations.
- The selected Herman, Patrick, Fotoni, or future Come and See style.
- Website forms, form recipients, confirmation messages, or automated replies.
- Analytics, Search Console, calendar integrations, or tracking code.
- Plugins, themes, custom code, or user-role definitions.
- Domain, DNS, SSL, hosting, or email records.
- Permanent URLs or slugs for important pages and content archives.
These changes can affect many pages or prevent future updates from reaching the site.
Requesting Support
Use the Website Support form and include:
- Parish name.
- Page URL.
- What you expected to happen.
- What happened instead.
- The exact wording of any error.
- A screenshot when it helps explain the problem.
- Whether the problem affects everyone or one user/device.
- Whether there is a deadline or immediate public-safety concern.
Do not email passwords. If temporary access is needed, BOTH/AND will provide a safe next step.
Urgent and Non-Urgent Requests
Examples of urgent problems include:
- The public site is unavailable.
- A form exposes private information or sends sensitive information to the wrong person.
- The site appears compromised.
- A domain or SSL problem prevents normal access.
- A clearly incorrect service time creates an immediate visitor problem.
Examples of normal requests include:
- A new page or substantial content section.
- A style preference.
- A future event or ministry update.
- A new user account.
- A revised photograph or biography.
Labeling every request urgent makes it harder to recognize a genuine emergency.
BOTH/AND prioritizes genuine urgent requests when they are received. The standard annual service promises a response by the end of the next two business days; it does not include 24-hour monitoring or a guaranteed immediate emergency response.
Parish Responsibilities After Launch
The parish remains responsible for:
- Accurate service times, events, clergy, staff, and contact information.
- Calendar maintenance.
- Content and media permissions.
- Parish-owned domain, email, analytics, calendar, and social accounts.
- Promptly reporting staff and volunteer role changes.
- Reviewing the site periodically for stale information.
- Keeping internal or pastoral information out of public content.
A Simple Monthly Review
Once a month, check:
- Homepage service times and alerts.
- Calendar and next several events.
- Clergy and contact information.
- Visitor, prayer, question, and contact forms.
- Navigation and important outside links.
- Featured announcements for stale or inaccurate content.
- Whether sermons, articles, and photographs are being added when the parish intends to maintain those sections. Useful older archives may remain; their age does not prevent the website from operating.
When in Doubt
Content should be easy to update. The design system should remain stable. If a change feels like it could affect the entire site, stop and ask before saving it.