Skip to content

fix(site): serve from custom domain reasonix.io#3880

Merged
esengine merged 1 commit into
main-v2from
fix/site-custom-domain-paths
Jun 10, 2026
Merged

fix(site): serve from custom domain reasonix.io#3880
esengine merged 1 commit into
main-v2from
fix/site-custom-domain-paths

Conversation

@esengine

Copy link
Copy Markdown
Owner

What

The landing site is now served from the apex custom domain reasonix.io at the site root, not from the GitHub Pages repo subpath (esengine.github.io/DeepSeek-Reasonix/).

Why

After pointing reasonix.io at GitHub Pages, the site rendered unstyled: the build still carried the Astro base: '/DeepSeek-Reasonix', so every asset URL was prefixed (e.g. the stylesheet resolved to /DeepSeek-Reasonix/static/index.*.css) and 404'd at the domain root. canonical and og:url were also hardcoded to the old esengine.github.io/DeepSeek-Reasonix/ URL.

Changes

  • site/astro.config.mjs: set site: 'https://reasonix.io', drop base: '/DeepSeek-Reasonix'.
  • site/src/layouts/Base.astro: derive canonical/og:url from Astro.site instead of hardcoding the URL, so they won't go stale on a future domain change.

Verification

Local npm run build output now resolves to root-relative paths (stylesheet /static/index.*.css, favicon /favicon.svg, canonical/og:url https://reasonix.io/). No residual /DeepSeek-Reasonix prefixes remain in the build output.

Note: this is independent of the pending HTTPS certificate issuance for the custom domain.

The site is now served from the apex domain reasonix.io at the root,
not from the GitHub Pages repo subpath. Drop the Astro base
'/DeepSeek-Reasonix' (which prefixed every asset URL and broke CSS),
point site at https://reasonix.io, and derive canonical/og:url from
Astro.site instead of hardcoding the old esengine.github.io URL.
@esengine esengine requested a review from SivanCola as a code owner June 10, 2026 15:53
@esengine esengine merged commit 0f27608 into main-v2 Jun 10, 2026
12 of 14 checks passed
@esengine esengine deleted the fix/site-custom-domain-paths branch June 10, 2026 16:03
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