Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/a-master-artificer/llms.txt

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

The homepage is your portfolio’s first impression. In the A Master Artificer theme, it maps to the route / and carries the themed navigation label Cover. The file responsible for it is index.html, located at the root of the repository. This is the file GitHub Pages looks for first when someone visits your published URL, so it must stay at the repository root at all times.

​
File

index.html
Route: /
Themed label: Cover
Asset: assets/Home.js

​
HTML Structure

Every page in the theme shares the same HTML shell. The page content — including your name, headline, and introduction — lives inside the JavaScript bundle, not in the HTML itself. The HTML file’s job is to load that bundle and give React a place to mount. 
<!doctype html>
<html lang="en">

<head>
    <meta charset="UTF-8" />
    <link rel="icon" type="image/svg+xml" href="./vite.svg" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>A Master Artificer</title>
    <script type="module" crossorigin src="./assets/main.js"></script>
    <link rel="modulepreload" crossorigin href="./assets/proxy.js">
    <link rel="modulepreload" crossorigin href="./components/grimoire/AstrolabeNav.js">
    <link rel="modulepreload" crossorigin href="./components/grimoire/CustomCursor.js">
    <link rel="stylesheet" crossorigin href="./assets/main.css">
</head>

<body>
    <div id="root"></div>
</body>

</html>
The <div id="root"> element is where React mounts the application. When the browser loads index.html, assets/main.js runs, detects the current route (/), and renders the Cover page content inside that element. You will not find your name or headline written directly in the HTML — they live in assets/Home.js alongside the rest of the homepage component.

​
What to Edit

1

Update your displayed name

Open assets/Home.js and find the text that contains the portfolio owner’s name. Replace it with your own name exactly as you want it to appear on screen.
2

Write your headline

The headline sits directly beneath the name. It is usually a short phrase that describes what you do — a title, a discipline, or a defining characteristic. Keep it to one line if possible.
3

Write your short introduction

The introduction is a few sentences below the headline. This is the first piece of body text a visitor reads. Use it to tell them who you are, what you make, and why the work matters. Write it in your own voice — this page sets the tone for everything that follows.
4

Update the page title

In index.html, change the <title> value from A Master Artificer to a title that reflects your portfolio — typically your name or your name plus a descriptor.
5

Keep index.html at the root

Do not move index.html into a subfolder. GitHub Pages requires it at the repository root to serve the site at your published URL.

​
Key File: .nojekyll

A file called .nojekyll lives beside index.html at the repository root. It must stay there and remain completely empty. It tells GitHub Pages to publish your files directly without trying to process the site as a Jekyll project. If this file is missing or renamed, GitHub Pages may fail to load JavaScript files that start with an underscore. 
.nojekyll
Correct — the file exists and is empty.
Edit the homepage first. Getting your name, headline, and introduction right before working on any other page makes the rest of the customization easier. The voice and framing you establish on the Cover page will guide how you write the About page, how you describe your projects, and how you present your skills. Starting here gives the whole portfolio a consistent point of view from the beginning.

Build docs developers (and LLMs) love

Get started for freeTalk to us