MinistryPlatform Help Center — Context7-ready Corpus

A markdown mirror of the MinistryPlatform Help Center, created so AI coding assistants (Claude Code, Cursor, etc.) can query MinistryPlatform documentation they otherwise can't reach — the help-center portal blocks bot crawlers, so conventional web-retrieval and search-engine indexing don't work.

Maintained by Jason Lee of Northwoods Church (a MinistryPlatform customer), with permission from ACS Technologies. Not an official ACS Technologies product.

Who this is for

1. AI coding assistants using Context7 MCP — query the corpus directly from your IDE while you work.
2. MinistryPlatform customers — clone this repo locally and point your own AI tools at it.
3. The MP developer community — accurate, cite-able documentation for building integrations against the MP REST API, widgets, and platform features.

Using this corpus

Via Context7 MCP (recommended for developers)

Once published, add this library to your Context7 MCP client:

use library: <context7-slug-to-be-assigned-on-submit>

Then ask your assistant MP-related questions; it will retrieve from this corpus automatically and cite the canonical help.acst.com URL.

Locally

git clone https://github.com/TheFamLee/ministryplatform-help-center.git
cd ministryplatform-help-center

Tell your agent to read CLAUDE.md first — it explains how the corpus is organized and how to query it efficiently without preloading all 1,196 pages into context.

Entry points:

• llms.txt — flat index of every page with one-line descriptions.
• docs/<section>/README.md — 66 curated section summaries with key concepts, page groupings, and typical workflows.
• docs/<section>/.../<slug>.md — 1,196 individual help-center pages with YAML frontmatter (title, source_url, breadcrumbs, last_modified, keywords).
• assets/ — 905 mirrored images, GIFs, and diagrams keyed by their Heretto object UUID.

What's included

• 1,196 pages covering: Help Topics (Platform, PocketPlatform, Widgets, Tools, Integrations, Reports, Connect Suite, Check-In Suite, BMT, CloudServices, Get Started, Support & Services), Guides, Video Library, What's New, Widget Configurator, Developer Resources, Privacy & Security.
• 66 curated READMEs — human-written overviews for every section and major subsection.
• 905 binary assets mirrored locally so the corpus is self-contained (no dependency on Heretto's expiring CDN URLs).
• 35 Vimeo video catalog entries with titles, descriptions, durations, and direct Vimeo URLs (videos themselves are not mirrored).
• Source-side issue log at _discovery/source-issues.md listing typos and content defects that originate in the source pages (preserved verbatim in the mirror, reportable to ACS directly).

Coverage is verified 100% against the portal's canonical structure API.

Refreshing

npm install   # once per machine
npm run all   # discover → crawl → assets → build → enrich → index

Individual steps:

• npm run discover — regenerate URL manifest from the live sitemap.
• npm run crawl — fetch pages via /api/content/<path> (cached by slug; RECRAWL=1 to force).
• npm run assets — download Heretto-hosted images (cached by UUID).
• npm run build — convert cached payloads to markdown.
• npm run enrich — regenerate docs/video-library/README.md.
• npm run index — regenerate llms.txt.
• node scripts/validate.mjs — verify asset + link integrity.

Environment knobs: CONCURRENCY (default 4), DELAY_MS (default 250), RECRAWL=1 to refetch.

Repository layout

.
├── CLAUDE.md                       # Agent onboarding — read this first
├── NOTICE.md                       # Source attribution and permission statement
├── README.md                       # This file
├── context7.json                   # Context7 indexing config
├── llms.txt                        # Flat page index
├── docs/
│   └── <section>/<sub…>/
│       ├── README.md               # Curated section summary
│       └── <slug>.md               # Individual help-center pages (1,196 total)
├── assets/                         # 905 mirrored binary assets, keyed by UUID
├── scripts/                        # Build pipeline (ESM Node)
│   ├── discover.mjs                # Sitemap → URL manifest
│   ├── crawl.mjs                   # Content API fetcher
│   ├── download-assets.mjs         # Asset mirror
│   ├── build.mjs                   # Payloads → markdown
│   ├── enrich-video-library.mjs    # Video catalog rebuilder
│   ├── build-index.mjs             # llms.txt generator
│   ├── validate.mjs                # Asset + link integrity check
│   └── lib/heretto.mjs             # API helpers
└── _discovery/
    ├── urls.json                   # URL manifest (tracked)
    ├── assets.json                 # URL → local-path map (tracked)
    ├── source-issues.md            # Source-side defects catalog (tracked)
    ├── playwright/                 # Canonical structure snapshot (tracked)
    └── raw/                        # Cached API payloads (gitignored, 85MB)

Page format

Every markdown file starts with YAML frontmatter:

---
title: "Impersonating Users"
description: "Learn about the impersonate a user feature in MinistryPlatform."
source_url: "https://help.acst.com/en/ministryplatform/guides/admins-setting-up-new-users/impersonating-users"
section: "guides"
slug: "guides/admins-setting-up-new-users/impersonating-users"
topic_type: "topicref"
topic_id: "concept-2052"
uuid: "c194ec36-e3c2-4634-bf7f-ebeeab6ba1bc"
last_modified: "2026-03-03T22:40:54.015Z"
breadcrumbs: [...]
keywords: [...]
source: MinistryPlatform Help Center (ACS Technologies)
---

Internal links are rewritten to absolute https://help.acst.com/en/… URLs. Images resolve via relative paths into the local assets/ directory.

For ACS Technologies

We'd love for this to become an official ACS Technologies resource. If you (ACS) want to take ownership:

• GitHub repo transfer preserves all history, issues, stars, and sets up redirects — zero link rot for existing consumers.
• Context7 library transfer moves the indexing target with it.
• We're happy to walk through the pipeline, document the refresh cadence, and hand over keys.

Open an issue or email the maintainers to start that conversation. See NOTICE.md for full attribution and contact details.

Reporting issues

• Page out of date or different from help.acst.com: open an issue (use the "Page out of date" template).
• Typo or factual error in source content: report it directly to ACS Technologies through normal MP support channels. See _discovery/source-issues.md for known examples.
• Broken link, missing asset, or conversion artifact: open an issue — those are our bugs to fix.

Acknowledgements

• All content © ACS Technologies Group, Inc. Mirrored with permission.
• Portal technology: Heretto DITA CMS with a Next.js delivery layer.
• HTML → Markdown conversion: turndown with a Heretto-aware ruleset.