Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/color-melt/llms.txt

Use this file to discover all available pages before exploring further.

Static sites on GitHub Pages are straightforward to publish, but a handful of issues trip up almost every new user at some point. This page covers every common problem sourced from the Color Melt README — each one with a direct fix.
A 404 usually means GitHub Pages is either not enabled or can’t find index.html where it expects it.Check each of the following:
  • Pages is enabled. Open the repository → Settings → Pages and confirm the source is configured. If the Source dropdown still says “None,” Pages has not been turned on.
  • Source is set to main and / (root). Both values must be selected and saved. If the folder is set to /docs instead of / (root), GitHub Pages will look in the wrong place.
  • index.html is at the repository root. Open the repository file list and confirm index.html appears at the top level — not inside a subfolder like color-melt/ or theme/.
  • Files were not uploaded inside an extra folder layer. If you dragged the outer Color Melt folder into GitHub instead of its contents, every file will be one level too deep.
  • The repository name in the URL is spelled correctly. GitHub Pages URLs are case-sensitive. My-Repo and my-repo are treated as different repositories.
A blank page or unstyled page almost always means the assets/ folder didn’t make it into the repository, or a file path changed during the upload.Check each of the following:
  • All asset folders were uploaded. Open the repository and confirm assets/ and components/ appear at the root level. If either folder is missing, the stylesheet and scripts won’t load.
  • File paths were not changed. If any folder was renamed or moved after download, the relative paths inside index.html and the page files will point to locations that no longer exist.
  • Filenames and capitalization match exactly. GitHub Pages is case-sensitive. Main.css and main.css are different files.
  • Browser console shows no missing CSS or JS files. Open the browser developer tools (F12 or right-click → Inspect), click the Console tab, and reload the page. Any 404 errors listed there will point directly to whichever file is missing.
Broken images are almost always a missing folder or a capitalization mismatch in the file path.Check each of the following:
  • The images/ folder was uploaded. Open the repository root and confirm images/ is present. If the upload was done in multiple batches, this folder can be missed.
  • Image filenames and paths match exactly. If you renamed an image file after referencing it in the HTML, the src attribute will be pointing at the old name.
  • Capitalization hasn’t changed. Hero.png and hero.png are two different files as far as GitHub Pages is concerned. If you renamed a file on a case-insensitive system like Windows or macOS and re-uploaded it, the original casing may still be what’s referenced in the HTML.
GitHub Pages looks for one specific filename when loading the root URL. If it doesn’t find that exact file, the site returns a 404 instead of the homepage.The homepage file must be named exactly:
index.html
Common mistakes that prevent the homepage from loading automatically:
  • Index.html — capital I
  • index.htm — missing the l
  • home.html — wrong filename entirely
  • index.HTML — wrong case on the extension
Rename the file to index.html (all lowercase, .html extension) and re-upload it to the repository root.
That’s correct — it’s supposed to be empty..nojekyll is not a configuration file with settings inside it. The filename itself is the signal. When GitHub Pages sees a file named .nojekyll at the repository root, it skips Jekyll processing and publishes the files directly. Opening the file and finding nothing inside it is completely expected behavior.If you’re worried it wasn’t uploaded, just confirm the filename appears in the repository root file list alongside index.html. No content is needed inside it.
GitHub Pages republishes automatically after each commit, but there are a few reasons the update might not appear right away.Check each of the following:
  • Changes were committed to the correct branch. Go to Settings → Pages and check which branch is selected as the source. If you committed to a different branch, the live site won’t update.
  • The correct file was edited. It’s easy to edit a local copy and forget to commit it, or to edit a file in the wrong repository.
  • The build has finished. Open Settings → Pages and look for the build status. If a build is still in progress, wait for it to complete before checking the live URL.
  • Your browser is showing a cached version. Do a hard refresh to bypass the cache: Ctrl+Shift+R on Windows and Linux, or Cmd+Shift+R on macOS. On mobile, close and reopen the browser tab.
Color Melt includes decorative components — liquid forms, lava blobs, rainbow arches, sticker elements, and animated transitions — that can affect spacing and layout on narrow screens.If the mobile layout looks off:
  • Test with a real device or browser developer tools. Open browser dev tools (F12), click the device toolbar icon, and check several common phone widths. A real device test is even more reliable.
  • Check whether decorative elements are overlapping content. Animated or absolutely-positioned components can shift at small breakpoints and cover text, buttons, or navigation links.
  • Look for CSS adjustments in assets/main.css. Spacing and sizing for decorative components can be adjusted at mobile breakpoints without changing the desktop layout.
The theme is designed to be expressive without blocking navigation, so any decorative element that covers important content on mobile is worth fixing before sharing the live URL.

​
Still Stuck?

If none of the solutions above resolve the issue, open a GitHub issue with as much detail as possible. Include the affected page URL, the browser and device you’re using, a description of what happened versus what you expected, and a screenshot if you have one.

Report an Issue

Open a GitHub issue with the affected page, browser/device, what happened, and a screenshot.

Build docs developers (and LLMs) love

Get started for freeTalk to us