Skip to main content

Documentation Index

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

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

The Contact page appears as “Drop a Note” in the navigation bar. It is one of the most important pages to update before publishing because the portfolio is not only a visual piece — it is a practical way for people to reach you. Every visitor who wants to hire you, collaborate with you, or give you feedback will come here first. Placeholder links and empty email addresses turn that intent into a dead end.
Update the Contact page with your real contact information before publishing. Placeholder email addresses, empty links, or template text will be visible to every visitor who reaches out. Check each link manually after publishing to confirm it works.

File location

pages/Contact.html

What to include

The README recommends making contact information easy to find. At minimum, include:
FieldNotes
Email addressA direct contact email; can be a Gmail, custom domain, or any address you actively check
GitHub profile URLhttps://github.com/yourusername
LinkedIn profile URLhttps://linkedin.com/in/yourprofile
Portfolio or personal siteOnly if different from this GitHub Pages site
Résumé or CV downloadOptional; link to a PDF hosted in the repository or an external service
Link each item as a standard anchor element so visitors can click directly to each destination.

Contact form

The theme includes a .dye-bleed-input CSS utility class in assets/main.css for styled form inputs. The class adds a cyan-to-magenta glow on focus that fits the theme’s color system. Use it on <input> and <textarea> elements if you add a contact form:
<input
  type="email"
  class="dye-bleed-input"
  placeholder="your@email.com"
/>
<textarea
  class="dye-bleed-input"
  placeholder="Your message"
  rows="5"
></textarea>

Static form options

The Artisan Developer theme is fully static — there is no backend server to receive form submissions. To make a contact form functional on GitHub Pages, use a third-party form service:
ServiceNotes
FormspreeFree tier available; set action to your Formspree endpoint
Netlify FormsAvailable if you migrate hosting to Netlify
EmailJSSends email directly from the browser using a client-side API key
All three work without a server and are compatible with static GitHub Pages sites. Formspree is the most common choice for quick setup. “Drop a Note” can be renamed to anything that fits your communication style. Edit the contact entry in components/SwirlNav.js:
{ path: "/contact", label: "Drop a Note" },
// Change to:
{ path: "/contact", label: "Contact" },
Other options: “Reach Out”, “Get in Touch”, “Say Hello”, “Work Together”.

Build docs developers (and LLMs) love