llnl / llnl/llnl.github.io

Missing dependencies and broken links when using GH Pages

Open
#478 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
67
Forks
58
PR merge metrics
No merged PRs in 30d

Description

I am able to serve this project locally using `bundle exec jekyll serve` and navigate around the UI. Unfortunately, this does not seem to work through Github Pages. There appear to be several assets (css and js files) hosted separately on software.llnl.gov which are not available to github pages.

Steps to reproduce:
1. Fork llnl.github.io into own account.
2. Rebuild data index using MASTER.sh script
3. Delete CNAME file
4. Enable github pages pointing to "master"
5. Navigate to github pages url (in my case, https://jordanperr.github.io/llnl.github.io/)

Expected Behavior: Site should appear as it does locally.
Observed Behavior: UI is broken, many assets not loaded (404 errors in developer console).

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.

Research direction

Start by reproducing the deployment with the listed fork, MASTER.sh data-index rebuild, deleted CNAME, and GitHub Pages configuration. Inspect the generated page's CSS and JavaScript asset URLs and compare them with the locally served site; done means the GitHub Pages site loads its assets without 404 errors and matches the local UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, jekyll
Domain
web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.