Loading this page.
Preparing content, navigation, and supporting references for this route.
Preparing content, navigation, and supporting references for this route.
The public contact route for spcent is contact@spcent.com.
Use it for release questions, content corrections, collaboration notes, and public-site issues tied to the current release. It is a direct public mailbox rather than a staffed support queue, and it is reviewed on a best-effort cadence rather than through live monitoring.
The primary contact route is contact@spcent.com.
Messages are reviewed directly by the project maintainer on a best-effort cadence rather than by a staffed support team.
Reproducible site defects may be moved into GitHub issues to preserve route, repro, and fix history.
Avoid sending secrets or highly sensitive material through the public mailbox.
Use contact@spcent.com as the primary public mailbox for launch-facing contact and project communication.
Incoming mail is forwarded through Cloudflare Email Routing before it reaches the spcent maintainer inbox.
Content detail pages expose feedback links that prefill the current URL, entry kind, slug, and Program. Use those links when the request is tied to a specific framework, model, study, or glossary term.
Entry feedback is triaged as a correction, broken-link report, content request, worksheet request, or confusing-section report before it becomes queue work.
Messages are reviewed directly by the project maintainer rather than routed through a staffed support desk. The mailbox follows a best-effort review cadence, so spcent does not promise a same-day reply window or urgent escalation path.
Replies may come from the maintainer inbox instead of directly from the contact@spcent.com alias. Reproducible site defects may be normalized into GitHub issues so the route, repro, and fix history remain visible in one place.
Do not send secrets, passwords, private credentials, or highly sensitive personal information through this mailbox. The public contact route is for normal project communication, not secure case handling.
If your message touches privacy or policy concerns, use the same mailbox and consult the Privacy Policy for the current handling boundary.
These routes define the public contact and usage boundaries for this site.
Use the public mailbox for release-facing questions, content corrections, or public-site reports.
Use GitHub issues for reproducible public-site bugs that benefit from a durable public fix trail.
Read how messages sent to the public mailbox fit into the current privacy boundary.
Read the public-site usage boundary and disclaimer for the current release.