Skip to content

docs(site): serve the site from darkkle.com - #10

Merged
crypto-frog merged 1 commit into
mainfrom
docs/custom-domain
Aug 24, 2026
Merged

crypto-frog merged 1 commit into
mainfrom
docs/custom-domain

Conversation

@crypto-frog

Copy link
Copy Markdown
Owner

Points the published site at the project's own domain.

Changes

File Change
docs/CNAME New, contains darkkle.com. A CNAME file in the publishing source is what tells GitHub Pages to serve the custom domain
docs/_config.yml url → https://darkkle.com; baseurl → "" (empty, since the site is now at an apex root rather than a project subpath)
docs/robots.txt Sitemap reference updated
docs/llms.txt Page list updated

Links to the GitHub repository are unchanged. Only the site's own origin moved.

DNS is already in place

Verified before opening this:

  • apex darkkle.com → all four GitHub Pages IPs (185.199.108-111.153)
  • www.darkkle.com → CNAME → crypto-frog.github.io

After merge

GitHub Pages will detect the CNAME file, provision a Let's Encrypt certificate, and redirect crypto-frog.github.io/darkkle to the new domain so existing links keep working. HTTPS enforcement will be enabled once the certificate is issued.

npm run check passes; docs/ is not in the release archive.

Add a CNAME file so GitHub Pages serves the site from the project's own
domain, and set the site URL accordingly. The baseurl is now empty because
the site is served from the root of an apex domain rather than from a
project subpath.

The sitemap reference in robots.txt and the page list in llms.txt are updated
to the new origin. Links to the GitHub repository itself are unchanged; only
the site's own origin moved.

GitHub Pages will redirect the previous crypto-frog.github.io/darkkle
address to the new domain, so existing links keep working.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@crypto-frog
crypto-frog merged commit ce53638 into main Aug 24, 2026
3 checks passed
@crypto-frog
crypto-frog deleted the docs/custom-domain branch August 24, 2026 00:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant