docs: publish SMS policy and consent pages - #41
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds public, direct-path policy pages for a future Twilio A2P Campaign submission:
sms.htmldocuments the optional, limited developer/support SMS program, direct affirmative consent, message frequency, rates, STOP opt-out, and support contact.privacy.htmlandterms.htmlstate the corresponding mobile-number and messaging-consent non-sharing commitment.legal.cssgives the standalone pages an accessible shared presentation.sitemap.xmlpublishes the three canonical HTTPS URLs.The pages do not create a public enrollment flow, do not claim that A2P registration is complete, and avoid an unsupported automatic HELP-response promise. This is an A2P documentation prerequisite only; it does not change the SMS bridge, Twilio configuration, sender selection, or runtime behavior.
Fixes # — not applicable; owner-approved A2P Campaign documentation prerequisite.
Type of change
Validation
131c0fc5b857ef9eac52aade7a3fee5fbd94b731.Adversarial content review found unsupported HELP claims and an inaccurate homepage sitemap
lastmod; both were corrected before this PR. PR CI ran pre-commit, including gitleaks and Prettier, plus unchanged service-worker syntax validation. It does not validate policy wording, HTML/CSS rendering, or sitemap XML semantics; those are deliberately recorded here as post-merge public-verification checks.No local OpenTofu or other validation commands are claimed.
Impact and rollout
Self-contained in
makeitworkcloud/www; no producer/consumer, pin, generated-copy, service-worker, workflow, bridge, or Twilio-account change. After an owner-approved merge, the existingdeploy.ymlautomatically validates, syncs the static site to S3 with--delete, and purges Cloudflare. Public availability of the direct.htmlURLs must be verified separately after deployment. Rollback is a revert followed by the same automatic deployment.Manual A2P Brand/Campaign registration and approved sender association remain separate owner-console actions. The future GitOps switch to the Messaging Service sender mode is unchanged and remains confirmation-gated.
Safety and secrets
This change was materially produced by an AI agent under owner direction.