Hosting & Deploying

Overview of the ways to deploy to Netlify: Git, CLI, drag and drop, API, build hooks and deploy buttons.

How to attach an apex domain or subdomain to a Pages project. Apex domains need the zone on Cloudflare; subdomains just need a CNAME to <site>.pages.dev. Add the domain in the dashboard first or you may get a 522.

Quickstart for importing a Git project into Netlify, reviewing auto-detected build settings and publishing, with optional custom domain setup afterward.

Explains adding the domain in repository settings and creating DNS records: four A (and optional AAAA) records or ALIAS/ANAME for the apex, CNAME for www. Warns against wildcard DNS records because of takeover risk.

Creates a username.github.io repository, enables Pages from a branch, and sets a title and description in _config.yml. Changes can take up to 10 minutes to appear.

Netlify support explains why stacking Cloudflare's orange-cloud proxy on Netlify causes stale content, wrong analytics, broken split testing and harder debugging. Recommended fix is DNS-only mode and a Netlify-issued certificate; Cloudflare Origin Certificates should not be installed on Netlify.

Reference for netlify.toml: build base, publish and command, deploy contexts, redirects, headers and functions. Values in the file override the UI.

How to set or remove HTTP response headers for static assets with a _headers file, including splat/placeholder syntax and the 100-rule limit. Redirects are applied before headers.

How the _redirects file works on Pages: source, destination and optional code per line (default 302), splats and placeholders, and limits of 2,000 static and 100 dynamic rules. It does not apply to Pages Functions.

Shows how to define redirects and rewrites with a _redirects file or netlify.toml. Rules are matched top to bottom, first match wins, and _redirects rules are processed before netlify.toml.