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 contact section of the A Master Artificer theme spans two pages. contact.html is the Send Familiar page — the primary place where visitors can find your email address, GitHub profile, LinkedIn, and any other contact or profile links. testimonials.html is the Whispers page, where you can include recommendations, feedback, or comments from collaborators, clients, instructors, or colleagues. Both pages are important to update before publishing.

​
Send Familiar — contact.html

The contact page maps to the route /contact and carries the themed navigation label Send Familiar. It is the destination visitors reach when they want to get in touch. All of your contact links and external profile addresses live here.

​
File

contact.html
Route: /contact
Themed label: Send Familiar
Asset: assets/Contact.js

​
HTML Structure

contact.html uses the same HTML shell as every other page in the theme. The contact links and layout are rendered by the React application from assets/Contact.js. 
<!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>

​
What to Edit

Open assets/Contact.js and replace the placeholder contact information with your own.
1

Add your email address

Include a working email address that you check regularly. Use a mailto: link so visitors can open their email client directly from the page. If you prefer not to publish your email publicly, use a contact form service or a masked address.
2

Add your GitHub profile link

Link to your GitHub profile using the full URL — for example, https://github.com/yourusername. This is one of the most important links on the contact page for a technical portfolio.
3

Add your LinkedIn profile link

Link to your LinkedIn profile if you maintain one. Use the full URL including your custom profile path.
4

Add any other relevant links

Add links to other platforms or profiles that are relevant to your work. This might include a portfolio on a design platform, an npm profile, a public résumé, or a link to your personal domain. Only include links to profiles you actively maintain.
5

Remove placeholder links

Check for any placeholder links — such as #, https://example.com, or links pointing to the theme author’s profiles — and replace or remove them entirely. Leaving placeholders in place when you publish is one of the most common portfolio mistakes.
6

Update the page title

In contact.html, update the <title> tag to include your name and the page context — for example, Your Name — Contact.
Test every external link on the contact page before publishing, and again after any update. A broken email link, a dead GitHub URL, or a LinkedIn path that returns a 404 makes it impossible for a visitor to reach you — which defeats the entire purpose of the contact page. Open each link manually in a browser, confirm it loads the correct destination, and repeat this check whenever you change a link.

​
Whispers — testimonials.html

The testimonials page maps to the route /testimonials and carries the themed navigation label Whispers. This page is the place to include feedback, recommendations, or comments that speak to the quality and character of your work.

​
File

testimonials.html
Route: /testimonials
Themed label: Whispers
Asset: assets/Testimonials.js

​
HTML Structure

testimonials.html uses the same HTML shell as the rest of the theme. The one difference from the other pages is that it omits the <link rel="icon"> favicon line and the CustomCursor.js modulepreload tag contains a minor typo (href=. instead of href=) that does not affect page functionality. 
<!doctype html>
<html lang="en">

<head>
    <meta charset="UTF-8" />
    <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>

​
What to Edit

Open assets/Testimonials.js and replace the sample testimonial content with real feedback you have received.
1

Add real testimonials

Include feedback from people who have worked with you — collaborators, supervisors, clients, instructors, or fellow contributors on open-source projects. Ask for permission before publishing someone’s words.
2

Include the person's name and context

Each testimonial should include the name of the person who gave it and their relationship to you or the work — for example, “Engineering Manager at Company Name” or “Collaborator on Project Name.” Context makes the feedback more credible.
3

Keep testimonials relevant

Focus on feedback that speaks to the quality of your work, your communication, your problem-solving, or your reliability. Avoid testimonials that are purely personal and unrelated to your professional skills.
4

Update the page title

In testimonials.html, update the <title> tag to include your name and the page context — for example, Your Name — Testimonials.

​
Footer Link Pattern

The theme includes footer links that appear on every page. These links give visitors consistent access to your contact information without requiring them to navigate to the contact page first. The contact information in the footer should match what is on the Send Familiar page exactly. When you update the contact page, also check the footer in assets/main.js or the shared layout component and confirm that every link there points to the correct destination. Inconsistent contact links — where the footer links to a different email than the contact page, for example — erode the impression of a carefully maintained portfolio. Common footer link targets to verify:
  • Email address (mailto: link)
  • GitHub profile URL
  • LinkedIn profile URL
  • Portfolio or personal domain URL
  • Any other social or professional profile links

Build docs developers (and LLMs) love

Get started for freeTalk to us