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.

Getting your portfolio live with A Master Artificer takes only a few steps. Because this theme ships as a finished static build — plain HTML, CSS, and JavaScript files — there is no package installation, no local build command, and no server to configure. You edit the files, upload them to GitHub, enable GitHub Pages, and the site is live.
1
Fork or Download the Repository
2
Go to the theme repository and get your own copy:
3
https://github.com/apursley2012/a-master-artificer
4
  • Fork the repository to create a copy under your own GitHub account. This is the easiest path if you want to track changes from the original.
  • Download the ZIP archive if you prefer to start fresh without the original commit history. Use the Code → Download ZIP button on the repository page.
    • 5
    Either way, make sure the contents of the theme end up at the root of your repository — index.html must sit at the top level, not inside a subfolder.
    6
    Understand the Folder Structure
    7
    Before editing, take a moment to understand what each folder and file does. The theme is organized so page content, shared styling, and interface behavior stay in separate places.
    8
    a-master-artificer/
├── .nojekyll
├── README.md
├── index.html
├── assets/
│   ├── About.js
│   ├── Article.js
│   ├── BlogIndex.js
│   ├── CaseStudies.js
│   ├── Contact.js
│   ├── Home.js
│   ├── Projects.js
│   ├── Skills.js
│   ├── Testimonials.js
│   ├── Work.js
│   ├── main.css
│   ├── main.js
│   ├── proxy.js
│   └── use-transform.js
├── components/
│   └── grimoire/
│       ├── AstrolabeNav.js
│       ├── CustomCursor.js
│       └── PageChrome.js
├── images/
│   └── screenshots/
└── pages/
    ├── About.html
    ├── Article.html
    ├── BlogIndex.html
    ├── CaseStudies.html
    ├── Contact.html
    ├── Projects.html
    ├── Skills.html
    ├── Testimonials.html
    └── Work.html
    9
    Key points:
    10
  • index.html is the homepage and the entry point GitHub Pages uses.
  • pages/ holds the standalone HTML file for each portfolio section.
  • assets/ holds the compiled CSS, the per-page JavaScript modules, and shared build helpers.
  • components/grimoire/ holds the three pre-compiled theme interface components.
  • .nojekyll tells GitHub Pages to serve the files directly without Jekyll processing.
    • 11
    The .nojekyll file is intentionally empty. Its presence — not its contents — is what matters. Do not add text to it, rename it, or give it a file extension. The correct form is exactly .nojekyll with no extension and no content.
    12
    Edit Your Personal Information in index.html
    13
    Start with index.html. This is the homepage, and it sets the tone for the entire portfolio.
    14
    Open index.html in any text editor and update:
    15
  • Your name — the display name shown in the hero section
  • Your headline — a short professional description beneath your name
  • Your introduction — the opening paragraph that tells visitors who you are
    • 16
    Because the file is standard HTML, you can edit it in a plain text editor, VS Code, or any code editor you prefer. No compiler or preview server is needed; you can open index.html directly in a browser to check your changes before uploading.
    17
    Update Each Portfolio Page
    18
    Work through the pages in pages/ and replace the placeholder content with your real work. Each file corresponds to one section of the portfolio:
    19
    FileThemed LabelWhat to Updatepages/About.htmlThe PractitionerBackground, education, interests, creative pathpages/Projects.htmlConjuringsProject names, descriptions, screenshots, linkspages/Skills.htmlAthenaeumLanguages, tools, technologies, and capabilitiespages/Work.htmlPast CovensJob titles, employers, dates, and responsibilitiespages/CaseStudies.htmlField NotesIn-depth breakdowns of selected projectspages/BlogIndex.htmlLoose PagesWriting index and article linkspages/Article.htmlLoose Pages (article)Individual article contentpages/Testimonials.htmlWhispersRecommendations, feedback, and endorsementspages/Contact.htmlSend FamiliarEmail, GitHub, LinkedIn, and other contact methods
    20
    When writing project descriptions, be specific: explain what the project does, why you built it, which technologies you used, what decisions mattered, and what the result demonstrates.
    21
    GitHub Pages paths are case-sensitive. Pages/About.html and pages/About.html are treated as different files on the live server even if they look the same on Windows or macOS. Always use the exact filename casing shown in the folder structure above, and match that casing in every internal link.
    22
    Upload Files to GitHub
    23
    Upload the theme contents to your GitHub repository so that index.html sits at the root — not inside a nested folder.
    24
    To upload through the GitHub website:
    25
  • Open your repository on GitHub.
  • Select Add file → Upload files.
  • Drag the theme files and folders into the upload area.
  • Confirm that index.html appears at the top level of the repository.
  • Confirm that .nojekyll, assets/, components/, pages/, and images/ were all uploaded.
  • Add a commit message and select Commit changes.
    • 26
    Correct structure after upload:
    27
    your-repo/
├── .nojekyll
├── index.html
├── assets/
├── components/
├── images/
└── pages/
    28
    Incorrect — extra folder layer:
    29
    your-repo/
└── a-master-artificer/
    ├── index.html
    └── assets/
    30
    If index.html is nested inside a subfolder, GitHub Pages will not find it automatically and the site will show a 404 error.
    31
    Enable GitHub Pages
    32
    Once your files are uploaded, turn on GitHub Pages for the repository:
    33
  • Open the repository on GitHub.
  • Select Settings.
  • Select Pages from the left sidebar.
  • Under Build and deployment, choose Deploy from a branch.
  • Set the branch to main and the folder to / (root).
  • Select Save.
    • 34
    GitHub will begin building the site. The first build usually takes about one to two minutes.
    35
    Test the Live URL
    36
    After the build finishes, your portfolio is published at:
    37
    https://<username>.github.io/<repo-name>/
    38
    For example, if your GitHub username is jsmith and your repository is named my-portfolio, the URL will be:
    39
    https://jsmith.github.io/my-portfolio/
    40
    Open the URL and test:
    41
  • The homepage loads with your name and headline.
  • Navigation works from every page.
  • Images, styles, and interactive effects load correctly.
  • The site looks correct on a phone-width screen.
    • 42
    If the site does not appear immediately, wait a minute and refresh. GitHub Pages can take a short time to finish the first deployment.

    ​
    Next Steps

    After your portfolio is live, committed changes to the main branch are republished automatically. You can update any file through the GitHub website using the pencil Edit this file button — no local development environment needed. For a complete guide to deployment settings, common problems, and the .nojekyll file, see the detailed deployment reference:

    GitHub Pages Deployment

    Full deployment guide covering required repository structure, GitHub Pages settings, path case-sensitivity, and troubleshooting common problems.

    Build docs developers (and LLMs) love

    Get started for freeTalk to us