Support

FAQ

How do I edit the website?

Open the site from your dashboard, choose the section you want to update, make the draft change, preview it, then publish when it is ready.

In-depth answer+

Editing happens in draft so changes can be reviewed before they affect the live site. A clean editing process separates content changes, media changes, navigation changes, and publish approval.

Technical checks

  • Confirm you are editing the intended page and draft, not reviewing an older published version.
  • Preview the affected page after edits and check mobile width, desktop width, image cropping, links, and any repeated content blocks.
  • For layout issues, identify the page, section, block title, browser size, and whether the issue occurs in preview, editor, or published site.
  • For text or data updates like Mass times, staff, events, or announcements, include the exact replacement copy and whether the change is temporary or permanent.

Escalation details to include

  • Send the page URL or editor route, the block or field name, what you changed, what you expected, and what happened after saving.
  • Attach before and after screenshots for visual regressions, especially mobile layout, overlapping text, or cropped images.
  • If save fails, copy the visible error text and note whether the same change works on another page.

Reference notes

  • Draft: editable content that is not yet public.
  • Preview: the review surface for checking draft changes before publish.
  • Version history: used to compare, rename, or restore meaningful saved versions.
  • Audit context: sensitive changes such as giving links should be treated as publish-reviewed changes.

Can I restore an older version?

Yes. Version history is designed for safe publishing, so important changes can be reviewed and restored when available.

In-depth answer+

Editing happens in draft so changes can be reviewed before they affect the live site. A clean editing process separates content changes, media changes, navigation changes, and publish approval.

Technical checks

  • Confirm you are editing the intended page and draft, not reviewing an older published version.
  • Preview the affected page after edits and check mobile width, desktop width, image cropping, links, and any repeated content blocks.
  • For layout issues, identify the page, section, block title, browser size, and whether the issue occurs in preview, editor, or published site.
  • For text or data updates like Mass times, staff, events, or announcements, include the exact replacement copy and whether the change is temporary or permanent.

Escalation details to include

  • Send the page URL or editor route, the block or field name, what you changed, what you expected, and what happened after saving.
  • Attach before and after screenshots for visual regressions, especially mobile layout, overlapping text, or cropped images.
  • If save fails, copy the visible error text and note whether the same change works on another page.

Reference notes

  • Draft: editable content that is not yet public.
  • Preview: the review surface for checking draft changes before publish.
  • Version history: used to compare, rename, or restore meaningful saved versions.
  • Audit context: sensitive changes such as giving links should be treated as publish-reviewed changes.

Can I change Mass times, confession, adoration, staff, events, and announcements?

Yes. Those are first-class parish content areas so staff can update them without redesigning pages.

In-depth answer+

Editing happens in draft so changes can be reviewed before they affect the live site. A clean editing process separates content changes, media changes, navigation changes, and publish approval.

Technical checks

  • Confirm you are editing the intended page and draft, not reviewing an older published version.
  • Preview the affected page after edits and check mobile width, desktop width, image cropping, links, and any repeated content blocks.
  • For layout issues, identify the page, section, block title, browser size, and whether the issue occurs in preview, editor, or published site.
  • For text or data updates like Mass times, staff, events, or announcements, include the exact replacement copy and whether the change is temporary or permanent.

Escalation details to include

  • Send the page URL or editor route, the block or field name, what you changed, what you expected, and what happened after saving.
  • Attach before and after screenshots for visual regressions, especially mobile layout, overlapping text, or cropped images.
  • If save fails, copy the visible error text and note whether the same change works on another page.

Reference notes

  • Draft: editable content that is not yet public.
  • Preview: the review surface for checking draft changes before publish.
  • Version history: used to compare, rename, or restore meaningful saved versions.
  • Audit context: sensitive changes such as giving links should be treated as publish-reviewed changes.

Contact us

Include the domain, current site or dashboard URL, what changed, what you expected, and a screenshot when the issue is visual.

Need urgent help?

We will get back to you as soon as possible.