Add TubeCMS website template

[jonathanh]

Description

Adds a Domain Connect template for TubeCMS, a SaaS platform for YouTube creators. Each creator gets a site at {slug}.tubecms.app and can connect a custom domain. This template creates a CNAME record pointing the custom subdomain to on.tubecms.app (our Cloudflare Custom Hostnames fallback origin).

• Provider: tubecms.app
• Service: website
• Record: CNAME %sub% → on.tubecms.app

Type of change

• New template
• Bug fix (non-breaking change which fixes an issue in the template)
• New feature (non-breaking change which adds functionality to the template)
• Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

• Schema validated using JSON Schema template.schema
• Template functionality checked using Online Editor
• Template is checked using template linter (including -cloudflare flag — exit code 0, no warnings)
• Template file name follows the pattern <providerId>.<serviceId>.json (tubecms.app.website.json)
• resource URL provided with logoUrl is actually served by a webserver (https://tubecms.app/logo-transparent.svg)

Checklist of common problems

• digital signatures are used and syncPubKeyDomain specified (tubecms.app, public key at _dcpubkeyv1.tubecms.app TXT record)
• syncRedirectDomain is specified when intended to use redirect_uri parameter in the synchronous flow — N/A, we pass redirect_uri as a query parameter in the signed apply URL
• no TXT record with SPF content — N/A, only a CNAME record
• txtConflictMatchingMode is set on TXT records which shall be unique on a label — N/A, no TXT records
• variables are set to the smallest scope needed — single custom variable %sub% used only in the host field of one CNAME record
• no variables as a host name to apply template on subdomain instead of standard host parameter — %sub% is a custom variable passed via query string, not the standard host parameter
• no explicit usage of %host% variable in host attribute
• essential setting is used on records — N/A, single CNAME record that should be removed when the template is removed

Example variable values

"testData": {
  "testingSet": {
    "variables": {
      "domain": "example.com",
      "host": "",
      "sub": "www"
    },
    "results": [
      {
        "type": "CNAME",
        "name": "www",
        "ttl": 3600,
        "data": "on.tubecms.app"
      }
    ]
  }
}

[github-actions]

Linter OK:

Linter result for tubecms.app.website.json