I built this Blog in about a day with ChatGPT 5.5. This is the first article here, and I am glad you clicked in to read it.

The tools I used were ChatGPT 5.5, Codex, Cloudflare DNS, and GitHub Pages.

Cost Notes

The Cloudflare domain cost was about 7.5 USD for the first year.

Let's Get Started

Part 1: Generate HTML pages with ChatGPT

I used ChatGPT 5.5 here and asked Codex to generate the home page, blog index, and article page templates directly. After that, I adjusted the styling, interactions, and page structure based on what I wanted. My honest impression is that this model is extremely strong.

Part 2: Buy a domain on Cloudflare

I used Cloudflare's domain service for this site, but Aliyun, Tencent, GoDaddy, and other domain providers would also work. Cloudflare is relatively affordable. The top-level domain I bought is nyaro.org, which cost about 7.5 USD for the first year and about 10 USD for the second year.

Part 3: Get your GitHub Pages URL and upload your code

GitHub Pages already has complete official documentation, so I will not repeat the full setup here. You can refer to: GitHub Pages quickstart

Part 4: Configure DNS settings

After buying the domain, you need to add the DNS records required by GitHub Pages in Cloudflare DNS. GitHub Pages usually requires four A records and one CNAME record.

A records

Point the root domain to the GitHub Pages IP addresses:

Cloudflare DNS / A records
@  A  185.199.108.153
@  A  185.199.109.153
@  A  185.199.110.153
@  A  185.199.111.153

CNAME record

Point the www subdomain to your GitHub Pages address, such as username.github.io.

Cloudflare DNS / CNAME record
www  CNAME  username.github.io

You can also refer to the official GitHub documentation: Configuring a custom domain for GitHub Pages

Part 5: Add the custom domain in GitHub Pages

After configuring DNS, you also need to add your custom domain in GitHub Pages settings. Open Settings > Pages in the repository, enter the domain under Custom domain, and wait for verification.

Part 6: Done

At this point, the site may not be fully active yet. Wait about 10 minutes to an hour, then visit your domain or www subdomain. In most cases, the site should appear.

Closing

With this setup, you can build your own blog fairly easily. Next, I plan to keep refining the article index, multilingual structure, and editing workflow.