Add CAA records docs

[adityaoberai]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

[appwrite]

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)

Site	Status	Logs	Preview	QR
website 69d7f2670014e24571ca	Ready	View Logs	Preview URL

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)

Site	Status	Logs	Preview	QR
website 68496a17000f03d62013	Queued	View Logs	Preview URL

---

Tip

Deploy functions via zip upload or connect directly to your Git repo

[greptile-apps]

Greptile Summary

This PR adds a new dedicated documentation page for Certification Authority Authorization (CAA) records and cross-links it from the custom domains, TLS, DNS, and Sites domains pages. It explains when CAA records are required, how to add them, how to handle multiple CAs, and how wildcard and apex/subdomain scoping work.

• New caa-records/+page.markdoc covers the full CAA lifecycle: the certainly.com CA value for Appwrite Cloud, apex vs. subdomain inheritance, multiple-record additive behavior, wildcard issuewild handling, and a troubleshooting checklist.
• Existing pages (custom-domains, tls, dns, sites/domains) are updated with inline links and callouts clarifying that existing CAA records must be kept alongside any new Appwrite record.

Confidence Score: 5/5

Documentation-only change adding a new CAA records page and updating cross-links; no logic or runtime code is affected.

All changes are Markdoc content and a single nav entry in a Svelte layout. The new page accurately describes CAA record behavior per RFC 8659, correctly identifies certainly.com as Fastly/Appwrite's CA, and handles edge cases (multiple CAs, wildcard issuewild, apex vs. subdomain inheritance). Cross-links are consistent and step numbering in custom-domains was updated correctly.

No files require special attention.

Important Files Changed

Filename	Overview
src/routes/docs/products/network/caa-records/+page.markdoc	New CAA records documentation page explaining when and how to add a CAA record for Appwrite's CA (certainly.com), including apex/subdomain scoping, multiple records, wildcard certificates, and troubleshooting.
src/routes/docs/products/network/+layout.svelte	Adds "CAA records" nav entry between DNS and DDoS mitigation in the network section sidebar.
src/routes/docs/advanced/platform/custom-domains/+page.markdoc	Inserts a new conditional step 5 for adding a CAA record and renumbers the subsequent verification and SSL steps correctly.
src/routes/docs/advanced/security/tls/+page.markdoc	Appends a new "CAA records" section noting that certainly.com must be authorized when a domain has restrictive CAA records, with a link to the new dedicated page.
src/routes/docs/products/network/dns/+page.markdoc	Adds inline links to the new CAA records page in the DNS record type table and CNAME flattening instructions, plus an info callout about keeping existing CAA records.
src/routes/docs/products/sites/domains/+page.markdoc	Updates step 6 and 9 in the apex domain setup to link to the CAA records page and clarify that existing CAA records should not be replaced.

_{Reviews (5): Last reviewed commit: "Apply suggestion from @adityaoberai" | Re-trigger Greptile}