Having problems with Github pages

[22catch22]

Select Topic Area

General

Body

Greetings.
I'm working on project for my portfolio, and I'd like to share it on github pages. I set up the repo on github, added all the necessary scripts and stuff. When I type "npm run build", everything works as it should. Everything works fine...until I actually try to access it on github pages. Everytime I try, all I get is a '404' error message.
I don't understand what's going on? Can anyone help me?
Here's the repo in question: https://github.com/22catch22/GizmoHomepagePrototype/settings

update: I think I've found the root of the problem. Whenever I try to deploy the program, the system throws a "git spawn enoent" error message. This doesn't make any sense; I've installed git on my computer. It should be working. What's going on?

[irfan-sec]

Hi @22catch22,

A 404 error on GitHub Pages usually means one of these common issues:

The site hasn’t finished building or is failing to build.

Check the “Pages” section under your repo’s settings (link here) for any build errors or warnings.
If there’s a red error message, click for more details.
You haven’t published the correct branch or folder.

In the “Pages” settings, make sure you’ve selected the correct branch (usually main or gh-pages) and the correct folder (for most static sites, it’s /root or /docs, or sometimes /build or /dist for React/Vue/Next, etc.).
If you’re using a build tool (like React’s npm run build), you usually need to publish the build or dist folder, not the project root.
Your build output is not in the right place.

After you run npm run build, make sure the output is committed and pushed to the branch/folder you configured in GitHub Pages settings.
For example, if Pages is configured to use /docs, your build output should be in a docs folder and pushed to GitHub.
You are accessing the wrong URL.

After publishing, your site will be at https://22catch22.github.io/GizmoHomepagePrototype/ (case-sensitive!).
Make sure you use the exact repository name with correct capitalization.
What to check next:

Visit your Pages settings and confirm the source (branch/folder) is correct.
Look for build errors or warnings.
Ensure your latest build output is in the correct folder and pushed to the correct branch.
If you share what framework or build tool you’re using (React, Vue, static HTML, etc.), I can give more specific steps!

[22catch22]

I'm using Reactjs, jsx, HTML, and Vite

[frijal]

just fork my page frijal.github.io , delete all files inside artikel folder, and enter your content or (static html page) to folder artikelx or artikel.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐