Task 1 & Task 2 — Cloudflare Pages / Basic DNS

Task 1 — Cloudflare Pages (free version)

Direct summary: no need to buy a domain. You deploy your GitHub repo to Cloudflare Pages. Cloudflare gives you a *.pages.dev subdomain. Every git push to the configured branch triggers an automatic build and publish.

Useful commands:

git add .
git commit -m "update"
git push origin main

Your current index.html can stay as a single file (HTML + inline CSS). It's clean for proof of concept.

Task 2 — Basic DNS Setup (Google Cloud)

Summary: Task 2 requires a real purchased domain. Then you create DNS records to point to your Google Cloud VM (or other host). Here are basic records to create at your registrar / Cloud DNS:

A    @     203.0.113.45    TTL 3600    ; IPv4 of your VM (example)
CNAME www   @               TTL 3600    ; www.yoursite.com -> yoursite.com
TXT  @     "google-site-verification=xxxxx"  ; Google/email verification

Replace 203.0.113.45 with your Google Cloud VM's public IP and yoursite.com with your real domain.

Example text to include in your report

Paste this if you need to justify your choices:

Task 1: Deployed on Cloudflare Pages using the GitHub repo. Site accessible via <project>.pages.dev. Automatic deployment on each push.
Task 2: Requires a purchased domain. Basic DNS config (A, CNAME, TXT) pointing to a Google Cloud VM serving the static site.

Quick reminders (no BS)

• Cloudflare Pages = free + auto SSL + pages.dev.
• For a custom domain (ex: yoursite.com) you must buy it — no reliable free trick.
• Task 2 = DNS config + IP/VM; check TTL and propagation (few minutes to 24h depending on registrar).