A custom domain gives your map a cleaner, event-specific URL — something likeDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/samgutentag/sbburgerweek/llms.txt
Use this file to discover all available pages before exploring further.
sbburritoweekmap.com — instead of the default username.github.io/sbburgerweek path. The CNAME file in the repo and the GitHub Pages custom domain setting work together to route traffic correctly. The CNAME file is managed automatically by apply-theme.py, so you won’t need to edit it by hand.
Buy a domain
Any domain registrar works. Popular options include Namecheap, Cloudflare Registrar, and Google Domains. Pick whichever you’re comfortable with — the DNS steps below are the same regardless of registrar.Set up DNS
Add the following records at your DNS provider. The fourA records point the apex domain (@) to GitHub Pages’ IP addresses, and the CNAME record points the www subdomain to your GitHub Pages URL.
| Type | Name | Value |
|---|---|---|
| A | @ | 185.199.108.153 |
| A | @ | 185.199.109.153 |
| A | @ | 185.199.110.153 |
| A | @ | 185.199.111.153 |
| CNAME | www | YOUR_USERNAME.github.io |
YOUR_USERNAME with your actual GitHub username. DNS changes can take a few minutes to a few hours to propagate depending on your provider’s TTL settings.
Configure GitHub Pages
Once your DNS records are saved, connect the domain to your repository:- Go to your repo on GitHub → Settings → Pages
- Under Custom domain, enter your domain (e.g.
sbburritoweekmap.com) and click Save - GitHub will run a DNS check. Once it passes, check Enforce HTTPS
Update config.js
SetsiteUrl in config.js to your custom domain, then run apply-theme.py to propagate the change:
apply-theme.py reads siteUrl from config.js, extracts the domain, and writes it to the CNAME file. It also updates the og-image.svg, og-image.png, OG meta tags in HTML pages, the Hits badge URL in README.md, and the embed snippet domain — all from that single siteUrl value.