Tutorial ladder for OpenSPP, DHIS2, and FHIR onboarding

[jeremi]

Migrated from: jeremi/registry-docs#65
Original author: @jeremi
Source repository: jeremi/registry-docs
Source issue: #65
Source labels: none
Source milestone/release intent: none
Target area/path: docs/site

Issue

Goal

Design the next tutorial ladder after OpenCRVS so users can repeat the same learning path with OpenSPP, DHIS2, and FHIR-shaped sources.

Scope

• Define what each tutorial should teach beyond connector-specific setup.
• Identify shared structure across tutorials: credential file, generated config inspection, evidence question, smoke test, optional credential issuance.
• Decide which connector examples are docs-only and which require registryctl recipe support.
• Keep DCI/OpenFn/FHIR implementation details visible only where users must configure them.

Acceptance criteria

• Produces a short public docs plan or issue breakdown.
• Names the first tutorial to implement after OpenCRVS.
• Identifies shared text/components that should be reused.
• Identifies any runtime gaps before writing docs.

Migration Metadata

• Migrated to the public monorepo on 2026-06-25.
• Source title, body, labels, milestone/release intent, and pre-migration discussion were preserved where available.
• Code-grounded audit note: Tutorial ladder for OpenSPP, DHIS2, and FHIR onboarding is not present.
• Private/internal references, secrets, and obvious deployment-only details were redacted instead of copied forward.

[jeremi]

A small generic existing-HTTP-API tutorial is now tracked separately in #519. It should establish the beginner pattern with a stable public demo API and offline fixtures. This issue can then focus on the domain ladder, including OpenSPP, DHIS2, and FHIR, without making the first integration tutorial carry all domain complexity.

[jeremi]

Triage decision: close as not planned.

A standing tutorial ladder for OpenSPP, DHIS2, and FHIR creates roadmap and documentation commitments before each source has a maintained support claim, owner, and executable evidence. #72 already owns the supported OpenCRVS and DHIS2 proof boundary.

Create one focused tutorial when a specific integration is promoted and has a released starter, fixtures, and maintainer. Do not design an abstract ladder first.