Once your Welcome, Mortals site is live, keeping it current is straightforward: GitHub Pages monitors your publishing branch and automatically rebuilds the site whenever a new commit is pushed. You don’t need to re-enable Pages or trigger a manual deploy — committing the change is the entire workflow.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/welcome-mortals/llms.txt
Use this file to discover all available pages before exploring further.
How GitHub Pages handles updates
GitHub Pages watches the branch and folder you selected during setup (typicallymain and /(root)). Every time a commit lands on that branch, GitHub queues a rebuild and pushes the result to your live URL. There is no separate “publish” button to press after the initial setup.
Rebuilds are automatic but not instant. After committing a change, allow at least a minute before checking the live URL. If the update isn’t visible yet, wait another minute and try again.
Edit a file through the GitHub website
The GitHub web interface lets you edit any text file directly in the browser without installing Git locally. This is the fastest way to fix a typo, update a project description, or swap out a contact link.Open the repository
Navigate to your Welcome, Mortals repository on GitHub. Make sure you’re on the correct branch — the same branch configured as your Pages publishing source.
Open the file to edit
Browse the file list or use the repository search to find the file you want to change. Common targets include
index.html for homepage content, page-specific HTML files such as projects.html or contact.html, and assets/main.css for style changes.Select the Edit this file button
Click the pencil-shaped Edit this file button near the top-right corner of the file preview. The file opens in an inline editor.
Make the change
Edit the content directly in the browser editor. For HTML files, locate the text or element you want to update and make your change. Keep surrounding tags and indentation intact to avoid breaking the page layout.
Commit the changes
Scroll to the bottom of the editor page. Add a short commit message that describes what you changed — for example,
Update contact email on contact.html. Select Commit changes to save directly to the branch.What happens automatically vs. what requires action
Understanding which steps GitHub Pages handles on its own helps avoid confusion after committing.| Step | Who handles it |
|---|---|
| Rebuilding the site after a commit | GitHub Pages — automatic |
| Pushing the rebuilt files to the live URL | GitHub Pages — automatic |
| Waiting for the rebuild to finish | You — allow about a minute |
| Clearing the browser cache to see the update | You — hard-refresh the browser |
| Verifying the change looks correct on the live site | You — manual check recommended |
After updating: what to verify
A quick check after each update catches problems before visitors encounter them. The Welcome, Mortals theme includes decorative elements and interactive components that can behave unexpectedly if surrounding markup is accidentally changed. After committing an update, confirm the following on the live site:- Navigation — click through each page link to confirm no broken paths were introduced
- Images — scroll through updated pages to confirm images load correctly; GitHub Pages paths are case-sensitive, so a filename capitalization change will break an image reference
- Interactive elements — confirm the custom cursor and spider interaction still behave as expected on the affected pages
- Mobile layout — resize the browser or check on a phone to confirm spacing and layout are intact, especially after CSS edits