Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Canonical host williamlay.co.uk (apex): CNAME + DNS

Open Beginner friendly
#35 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github
Domain
documentation, infrastructure, web-dev

Research direction

Start by inspecting public/CNAME on main, then search the repository for www references and review README.md, docs/overhaul/content-audit.md, astro.config.mjs, sitemap entries, and OG tags. Confirm the apex host is used consistently and verify the listed redirects and HTTPS behavior; done means every acceptance criterion is checked on main.

Written by the indexing model from the issue text.

Description

infra needs-william

Canonical host is the apex, https://williamlay.co.uk, for v2 as for v1. Decided 2026-09-15: v1 is already indexed on the apex, the Search Console Domain property is verified, and switching to www would cost a re-indexing transition for no concrete gain. This matches docs/overhaul/architecture.md and astro.config.mjs (site: "https://williamlay.co.uk") on main.

  • public/CNAME = williamlay.co.uk (added at cutover)
  • DNS: apex A/AAAA → GitHub Pages; www CNAME → laywill.github.io so GitHub serves the www → apex redirect.

Acceptance criteria

  • Apex resolves to GitHub Pages (4× A, 4× AAAA in place, verified 2026-09-15)
  • www CNAME → laywill.github.io; http://, https://www. and laywill.github.io all 301 to https://williamlay.co.uk/ with valid HTTPS (verified 2026-09-15 against v1)
  • public/CNAME on main = williamlay.co.uk
  • All canonical URLs, sitemap entries and OG tags on main use the apex host
  • Stale www references on main fixed: README.md ("Canonical host") and docs/overhaul/content-audit.md (CNAME line)
Dominant language
HTML
Stars
0
Forks
0
Avg merge
9h 52m
Merged PRs (30d)
59

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from laywill/laywill.github.io

All issues in laywill/laywill.github.io

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.