Add naia.today pages template#1441
Merged
Merged
Conversation
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
Linter OK
|
| Level | Code | Note |
|---|
PR Description Check PassedAll required sections are filled in correctly. Details |
pawel-kow
approved these changes
Jul 24, 2026
|
Thanks @arielvdl for contributing to the template. 🎉 This template has been reviewed and merged by @pawel-kow. 🙌 This template repository and its review process are maintained by independent individuals in their spare time, not as part of a paid role. If you or your company benefit from this protocol and its tools, please show your appreciation by buying a beer for @pawel-kow: https://github.com/sponsors/pawel-kow |
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.
Description
Adds the Domain Connect template for naia Pages (https://naia.today), a Generative Engine Optimization platform. naia Pages publishes customer content on a brand subdomain; this template sets up the CNAME needed to point that subdomain at the naia Pages host, plus a second CNAME (
_acme-challenge) that authorizes issuance of the managed TLS certificate (Google Certificate Manager DNS-01 authorization).naia.todaypageshostRequired: true, sync flow only, requests signed RS256, public key published at_dcpubkeyv1.naia.today"essential": "OnApply"so a manual edit by the domain owner (DNS provider migration, typo fix, etc.) on either record is not treated as a conflict that removes the whole template. This matters most for_acme-challenge, which needs to keep existing for certificate renewal. Follows the pattern of the existingadvancedsending.com.cname.jsontemplate in this repo.syncRedirectDomain: naia.today. No apex records.Type of change
Please mark options that are relevant.
How Has This Been Tested?
Please mark the following checks done
<providerId>.<serviceId>.jsonlogoUrlis actually served by a webserver (https://cdn.naia.today/naia-logos/bimi/naia.svgreturns HTTP 200,image/svg+xml)Checklist of common problems
Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.
syncPubKeyDomainis set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejectedwarnPhishingis not set alongsidesyncPubKeyDomain— the two must not appear togethersyncRedirectDomainis set whenever the template usesredirect_uriin the synchronous flow — not used by this template;syncRedirectDomain: naia.todayis set anyway (harmless)"v=spf1 ...") — use theSPFMrecord type instead — no TXT records in this templatetxtConflictMatchingModeis set on every TXT record that must be unique per label or content prefix (e.g. DMARC) — no TXT records in this template@ TXT "%foo%") unless necessary — prefer@ TXT "service-foo=%foo%"; if bare, justify in the PR description — both records are CNAMEpointsTo, not TXT;%target%/%acmetarget%are computed server-side by naia's signed apply request, never typed by the domain owner, same pattern as the existingadvancedsending.com.cname.jsontemplatehostlabel — the non-variable parts are fixed to limit misuse (e.g.%dkimkey%._domainkey, not%dkimhost%); if bare, justify in the PR description — bothhostfields are fixed literals (@,_acme-challenge), no variables inhosthostfield to create a subdomain — use thehostparameter ormultiInstanceinstead — the subdomain comes from the protocol's ownhostparameter viahostRequired: true%host%does not appear explicitly in anyhostattributeessentialis set toOnApplyon records the end user may need to modify or remove without breaking the template (e.g. DMARC) — set on both CNAME recordsOnline Editor test results
Editor test link(s):
Test naia.today/pages example.com/insights
Test performed:
Check template(extended schema/consistency check, no errors), thenTest apply templatewithDomain: example.com,Host: insights,target: demo.artefacto.naia.today,acmetarget: 11111111-2222-3333-4444-555555555555.authorize.certificatemanager.goog.(representative format matching what our backend generates via Google Certificate Manager'sDnsAuthorizationAPI). Result: both CNAME records applied correctly (insights.example.com. -> demo.artefacto.naia.today,_acme-challenge.insights.example.com. -> ...authorize.certificatemanager.goog.). Apex test not included, exempted byhostRequired: trueper the instructions above.🤖 Generated with Claude Code
https://claude.ai/code/session_01KsMFhRDrA3TtiBoqdT1JYZ