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.

All of the portfolio content in the Artisan Developer theme lives directly in the HTML files — there is no CMS, database, or build step involved. To change any text, open the relevant file in a text editor, find the content you want to replace, edit it, and save. The file is immediately ready to publish as-is.

​
Homepage (index.html)

The homepage is your first impression and the GitHub Pages entry point. Open index.html at the repository root and update your name, professional headline, and the introductory paragraph that describes who you are and what kind of work you do.
index.html must stay at the repository root. GitHub Pages serves it as the default entry file for the site. Moving it into a subfolder will break the published URL.
The KineticHeadline and TieDyeSwirl components on this page are decorative — the text content they display is what you need to personalize. Keep the headline concise and specific to how you want visitors to remember you.

​
About page (pages/About.html)

Open pages/About.html to update your biography, career background, education history, and personal story. This page gives visitors the context behind the work shown elsewhere on the site. Write it to be read rather than scanned — biography content benefits from complete sentences and a clear narrative arc. Consider covering:
  • What you do and how long you have been doing it
  • Your technical background or creative background
  • What kind of projects or roles you are looking for
  • Any education, certifications, or notable training
  • A personal detail or two that makes the portfolio feel human

​
Projects page (pages/Projects.html)

Open pages/Projects.html to list your featured work. Each project entry is structured using the MarbledCard component, which keeps content visually consistent while keeping the layout scannable. For each project, include:
  • Title — the name of the project or product
  • Brief description — one to three sentences explaining what it is and why it matters
  • Technologies used — the languages, frameworks, tools, or platforms involved
Keep descriptions short. Visitors should be able to read the whole projects page quickly and decide which entries deserve a deeper look. Save the extended detail for Case Studies.

​
Skills page (pages/Skills.html)

Open pages/Skills.html to list your technical skills, tools, and areas of expertise. The MarbledCard component structures these entries. Grouping skills by category (for example, Languages, Frameworks, Tools, Design, and Platforms) makes the page easier to scan than a flat list. Update the category labels and individual skill names to match your actual toolkit. Remove any skills that do not apply and add any that are missing.

​
Work history (pages/Work.html)

Open pages/Work.html to update your professional experience. Entries are displayed using the FabricStripTimeline component, which presents experience in a vertical chronological layout. Each entry should include:
  • Year range — for example, 2021 – 2024 or 2023 – Present
  • Role — your job title
  • Company — the organization name
  • Description — a short summary of your responsibilities and what you accomplished
List entries from most recent to oldest so visitors reading top to bottom see your current experience first.

​
Case studies (pages/CaseStudies.html)

Open pages/CaseStudies.html to add detailed technical or design writeups for selected projects. This page uses the MarbledCard layout and is the right place for longer explanations that would not fit on the Projects page — architecture decisions, design rationale, challenges, and outcomes. A strong case study covers:
  • The problem or goal
  • Your approach and key decisions
  • Technologies or methods used
  • The result or outcome

​
Blog (pages/Blog.html)

Open pages/Blog.html to add your writing archive, article index, or long-form content listings. This page works well as an index of posts with titles, dates, and short summaries, or as a direct host for longer written pieces. Update the article titles, publication dates, and summaries to match your actual writing. If you have external articles published elsewhere, link out to those with a short description of each piece.

​
Testimonials (pages/Testimonials.html)

Open pages/Testimonials.html to add quotes and feedback from colleagues, collaborators, clients, or managers. Each testimonial should include the quote text, the person’s name, and their role or relationship to you. Keep testimonials genuine and specific. A quote that describes a particular outcome or working style is more convincing than a general compliment.

​
Contact (pages/Contact.html)

Open pages/Contact.html to add your contact information and preferred communication channels. This is the last page many visitors will read before deciding whether to reach out, so it should be clear and complete.
Update your contact information before publishing the site. The default placeholder values in the theme are not your details. Publishing without updating this page means visitors who want to hire or collaborate with you will have nowhere to reach you.
Consider including:
  • Your email address
  • GitHub profile URL
  • LinkedIn profile URL
  • Portfolio or personal site URL
  • A link to your résumé or CV

​
Pre-publish checklist

Before pushing the site to GitHub Pages, work through this checklist to confirm every section is ready:
1

Update the homepage

Open index.html and replace the name, professional headline, and introductory paragraph with your own.
2

Replace all page content

Open each file in pages/ — About.html, Projects.html, Skills.html, Work.html, CaseStudies.html, Blog.html, Testimonials.html, and Contact.html — and replace the placeholder content with your own.
3

Replace screenshots

Add your own preview images to images/screenshots/. Replace the existing screenshot filenames or update the paths in the HTML if you use different names.
4

Test every navigation link

Open the site in a browser and click every link in the SwirlNav to confirm that each page loads correctly and no links return a 404.
5

Confirm .nojekyll is at the root

Verify that the .nojekyll file is present alongside index.html at the repository root. GitHub Pages requires this file to publish the site directly without treating the repository as a Jekyll project.
GitHub Pages is case-sensitive — About.html and about.html are treated as entirely different files. If your links use lowercase paths but your files are capitalized (as they are in this theme), the links will return 404 errors. Always use relative paths that exactly match the filename capitalization, for example ./pages/About.html rather than ./pages/about.html.

Build docs developers (and LLMs) love

Get started for freeTalk to us