Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/691ff205-cea0-8003-bde5-f449b081a1e1
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: Alright Boss, let’s untangle all of this cleanly. === Alright Boss, let’s untangle all of this cleanly. ==== Think of Git like a 3-step publishing pipeline: ==== # <code>git add .</code> > - . means “everything that changed in this folder”. - Nothing is uploaded yet, you’re just staging the changes. # <code>git commit -m "your message"</code> > - This creates a version of your code (a checkpoint) locally on your machine. - Still not on GitHub yet. # <code>git push</code> > - This is what syncs your local work → remote repo. - If you don’t push, GitHub (and GitHub Pages) never see your new files. So when you run npm run build, it only updates files on your computer (like your /docs folder). To make GitHub Pages use that new build, you must: <syntaxhighlight lang="bash">npm run build # creates/updates /docs git add . git commit -m "Build for GitHub Pages" git push # uploads /docs + config changes </syntaxhighlight> Only after the push will you see /docs and new files in the GitHub repo UI. ==== From your screenshots: ==== * Repo: h2wdemo.github.io * Vite config: - outDir: "docs" ✅ - base: "/h2wdemo.github.io/" ✅ * GitHub Pages: - Source: gh-pages branch, folder /docs ✅ (as long as gh-pages has a docs folder) The black screen + IWSDK ASCII art in DevTools tells me: * Your built JS is loading and running on the page. * The console errors you’re seeing: - Failed to load resource: webxr.png 404 → missing PNG asset, not fatal. - Unchecked runtime.lastError: The message port closed before a response was received → usually a browser extension, you can ignore. - Uncaught (in promise) Event → WebXR session request failing (e.g., device not supported or user gesture requirement). That’s common with XR demos in a regular desktop tab. So the blank screen is most likely: # Just the XR canvas with a black clear color – No visible UI fallback, so it feels “broken” even though it’s running. # Or the build you just ran isn’t the one Pages is serving – Because you haven’t pushed the latest /docs to the branch Pages is using. ==== Let’s lock in a simple, repeatable flow. ==== ===== Simplest for now: ===== * In GitHub → repo → Settings → Pages * Set: - Source: Deploy from a branch - Branch: main - Folder: /docs So Pages will serve from: 👉 main branch → /docs directory. ===== From your project folder (C:\Users\Marlaina\h2wdemo002): ===== <syntaxhighlight lang="bash">npm run build # 1) generates /docs (static site) git add . git commit -m "Update build for GitHub Pages" git push # 2) uploads /docs and code to GitHub main </syntaxhighlight> After the push: * GitHub sees updated /docs. * GitHub Pages rebuilds the site. * Your public URL stays: 👉 https://bossleoio.github.io/h2wdemo.github.io/ Give it a minute, then refresh with Ctrl+F5 (hard reload). ==== Do these to confirm everything is wired correctly: ==== # On GitHub (repo main branch): - You should see a <code>docs/</code> folder with a bunch of built HTML/JS/CSS files inside. # On your local machine in Windsurf: - npm run build finishes without errors. # In the browser at your Pages URL: - Open DevTools → Network tab → refresh. - You should see JS/CSS files loading from /h2wdemo.github.io/..., status 200. If you want a visual confirmation that the page is actually loading, add something obvious to index.html above the XR canvas, like: <syntaxhighlight lang="html"><body style="margin: 0;"> <h1 style="position: absolute; z-index: 10; color: white;">H2W Demo Loaded</h1> <div id="scene-container"></div> <script type="module" src="/src/index.ts"></script> </body> </syntaxhighlight> If you see the “H2W Demo Loaded” text on GitHub Pages, the site is working; any remaining issues are inside the XR scene, not deployment. If you send me: * A fresh screenshot of your repo root on GitHub (showing whether /docs exists), and * The full GitHub Pages settings panel (source/branch/folder), I can tell you exactly what one or two switches to flip to make it fully stable.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)