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 Skills page appears as “Pigments” in the navigation bar. It presents the technologies, tools, and areas of expertise that define your technical capabilities in a structured, scannable layout. Rather than listing every tool you have ever touched, this page works best when it reflects the stack you actively use and want to be hired for.

File location

pages/Skills.html

Content structure

Group your skills by category so visitors can scan the page quickly. Common groupings include:
CategoryExample contents
LanguagesJavaScript, TypeScript, Python, Rust
FrameworksReact, Next.js, Vue, Svelte
ToolsGit, Docker, Figma, VS Code
DesignCSS, Tailwind, animation, accessibility
InfrastructureGitHub Actions, Vercel, AWS, Netlify
The MarbledCard component works well for skill category cards, with the category name as the title prop and a concise list of specific skills as the excerpt prop:
<MarbledCard
  title="Languages"
  excerpt="JavaScript, TypeScript, Python — with working knowledge of Rust and Go."
  category="Core"
  delay={0}
/>

<MarbledCard
  title="Frameworks"
  excerpt="React (primary), Next.js, and Svelte. Experience with Vue on legacy projects."
  category="Frontend"
  delay={0.1}
/>

What to customize

Replace the placeholder skill names and tool lists in pages/Skills.html with your actual technology stack. Keep each group focused — four to six specific items per category is easier to scan than an exhaustive list. Visitors should be able to read the skills section in under a minute and come away with a clear picture of what you can build.

Design note

The theme uses the .tie-dye-text CSS class for decorative skill headings and badge-style elements with teal borders for individual skill names. These styles are defined in assets/main.css. If you want to adjust the visual treatment of skill badges, that is the file to edit — avoid inline style overrides that would conflict with the theme’s responsive layout rules.

Build docs developers (and LLMs) love