Switch from cyphai.io to cyphai-project.github.io

[Copilot]

Summary

The cyphai.io domain is being discontinued without redirection. This PR updates the Hugo configuration and removes the custom domain setup so the site is served from the GitHub Pages URL instead.

Changes

• Updated baseURL in hugo.toml from https://cyphai.io to https://cyphai-project.github.io/
• Removed public/CNAME (which had been force-committed to master despite public/ being in .gitignore) so future CI deployments no longer configure www.cyphai.io as a custom domain on the gh-pages branch

The references to cyphai.io in content/updates/2024-03-03-ghpage-migration.md are left unchanged as they are historical context describing the old site migration.

[MasWag]

@copilot Is it OK to have CNAME on gh-pages branch? Where does it come from?

[Copilot]

@copilot Is it OK to have CNAME on gh-pages branch? Where does it come from?

The CNAME on gh-pages (containing www.cyphai.io) came from public/CNAME, which was force-committed directly to the master branch (bypassing .gitignore) back in March 2024 when the custom domain was set up. Since Hugo doesn't delete pre-existing files in public/ before building, the CNAME survived each build and got deployed to gh-pages by the CI workflow.

Since the domain is being discontinued, keeping it is not OK — GitHub Pages would still try to serve the site at www.cyphai.io. I've removed public/CNAME from the tracked files in commit 3134274 so future CI deployments will no longer include it, and the site will be served at cyphai-project.github.io instead.

[Copilot]

Pull request overview

This PR updates the Hugo site configuration to stop using the discontinued cyphai.io custom domain and instead serve the site from the GitHub Pages default URL.

Changes:

• Updated Hugo baseURL to https://cyphai-project.github.io/.
• Removed the tracked public/CNAME file so CI deployments no longer publish a custom domain configuration.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
hugo.toml	Updates baseURL to the GitHub Pages URL to ensure generated absolute/canonical URLs point to the correct host.
public/CNAME	Removes the custom-domain CNAME so the gh-pages deployment no longer configures www.cyphai.io.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[MasWag]

@codex Can you review this PR?

[MasWag]

@copilot Thanks. How is the DNS of www.cyphai.io configured after this update? Is it possible to redirect it to https://CyPhAI-Project.github.io?

[Copilot]

@copilot Thanks. How is the DNS of www.cyphai.io configured after this update? Is it possible to redirect it to https://CyPhAI-Project.github.io?

After this PR's changes, the GitHub Pages deployment will no longer include the CNAME file, so GitHub Pages will stop accepting traffic for www.cyphai.io and will only serve the site at cyphai-project.github.io.

Whether www.cyphai.io can redirect to https://cyphai-project.github.io depends on who controls the DNS registrar for cyphai.io. If you still have access to the registrar, there are a few options:

1. DNS-level URL redirect (easiest): Most registrars offer a "URL forwarding/redirect" feature where you can point www.cyphai.io → https://cyphai-project.github.io/ without needing a server.

2. CNAME + GitHub Pages custom domain: Keep the CNAME DNS record pointing www.cyphai.io → cyphai-project.github.io, and re-add the custom domain setting in the GitHub Pages repository settings (without committing a public/CNAME file — GitHub Pages will manage it). This gives a true redirect at the HTTP level and preserves the old URL.

3. Let it expire: If the domain is not being renewed, once it expires, DNS stops resolving and no redirect is possible.

Since the problem statement describes the domain as "discontinued without redirection," if DNS access is already lost or the domain is expiring, option 3 is the reality and no action is needed on the code side — this PR's changes are sufficient.

[MasWag]

@copilot Thank. I see the following. Does this mean www.cyphai.io is practically redirected to cyphai-project.github.io?

bash-5.3$ host www.cyphai.io
www.cyphai.io is an alias for cyphai-project.github.io.
cyphai-project.github.io has address 185.199.109.153
cyphai-project.github.io has address 185.199.108.153
cyphai-project.github.io has address 185.199.110.153
cyphai-project.github.io has address 185.199.111.153
cyphai-project.github.io has IPv6 address 2606:50c0:8002::153
cyphai-project.github.io has IPv6 address 2606:50c0:8003::153
cyphai-project.github.io has IPv6 address 2606:50c0:8000::153
cyphai-project.github.io has IPv6 address 2606:50c0:8001::153

[Copilot]

@copilot Thank. I see the following. Does this mean www.cyphai.io is practically redirected to cyphai-project.github.io?

...

The DNS CNAME alias is half the picture, but not a complete redirect yet.

What that output shows is that www.cyphai.io has a CNAME record pointing to cyphai-project.github.io, so DNS resolution works — browsers will reach GitHub Pages' servers. However, GitHub Pages routes requests based on the HTTP Host header. Since this PR removes the CNAME file and the custom domain is no longer configured in GitHub Pages settings, a request arriving with Host: www.cyphai.io will get a 404 from GitHub Pages, not the site.

To make www.cyphai.io truly redirect visitors to https://cyphai-project.github.io, the simplest option is to re-enable the custom domain in the repository's Settings → Pages → Custom domain field and set it to www.cyphai.io. GitHub Pages will then serve the site at both domains and issue an HTTP redirect from www.cyphai.io to cyphai-project.github.io (or vice versa, depending on which is set as primary). No CNAME file needs to be committed — GitHub Pages manages it via the API when set through the UI.

If the goal is strictly to drop www.cyphai.io entirely, no further action is needed and the DNS CNAME can be left to expire/be removed by whoever controls the registrar.