Skip to content

fix(docs): set GitHub Pages base path so the site loads#9

Merged
enixCode merged 1 commit into
mainfrom
fix/docs-pages-base
May 29, 2026
Merged

fix(docs): set GitHub Pages base path so the site loads#9
enixCode merged 1 commit into
mainfrom
fix/docs-pages-base

Conversation

@enixCode
Copy link
Copy Markdown
Owner

What

The published docs site at https://enixcode.github.io/light-runner/ renders blank: the VitePress config had no base, so it emitted asset URLs rooted at / (enixcode.github.io/assets/...) which 404 under the project sub-path. The HTML loads but its CSS/JS never resolve.

  • Set base: '/light-runner/' in docs/.vitepress/config.ts.
  • VitePress auto-prepends base to absolute (/...) asset and head URLs, so the favicon (/banner.webp) and the generated CSS/JS now resolve under /light-runner/. No other change needed.
  • og:image / twitter:image already use full absolute URLs and are unaffected.
  • Goes live only once merged to main (the Docs workflow deploys on push to main touching docs/**).

build with cc

- The site deploys to https://enixcode.github.io/light-runner/ but the
  VitePress config had no base, so it emitted asset URLs rooted at /
  (enixcode.github.io/assets/...). Those 404 under the project sub-path,
  leaving the published page blank.
- Set base to /light-runner/. VitePress auto-prepends it to absolute asset
  and head URLs, so the favicon href and generated CSS/JS now resolve under
  /light-runner/. og:image and twitter:image already use full absolute URLs
  and are unaffected.

build with cc
@enixCode enixCode merged commit 747ef88 into main May 29, 2026
4 checks passed
@enixCode enixCode deleted the fix/docs-pages-base branch May 29, 2026 14:29
enixCode added a commit that referenced this pull request May 29, 2026
Ship attached-run state persistence + state-dir size cap (PR #8) and the
GitHub Pages base-path fix (PR #9). Version bump done manually because the
preversion hook's local VitePress build is unusable on a OneDrive-synced
working tree; the published npm package (dist JS) and the deployed docs site
(CI Docs workflow) are unaffected.

build with cc
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