Skip to main content
Chris Spurlock
Menu
Headshot of Chris Spurlock

Tools and technologies I use

The tools I actually reach for.

Some are part of my everyday stack. Others come in when a project needs a particular interface, integration, or delivery workflow.

The tools I know well

I choose tools based on the people using the site, its content, and the systems it needs to connect to.

Tools I use most: JavaScript and TypeScript, HTML and CSS, Eleventy and Nunjucks, Tailwind CSS, Figma, WordPress, GitHub, and Netlify.

Core web development

Languages and libraries for websites, web applications, content systems, and animation.

  • JavaScript
  • TypeScript
  • PHP
  • HTML
  • CSS
  • React
  • Vue
  • Eleventy
  • Nunjucks
  • Tailwind CSS
  • shadcn/ui
  • Radix UI
  • Headless UI
  • Alpine.js
  • Framer
  • Lottie
  • GSAP

Design and publishing

Tools for wireframes, prototypes, user flows, interface design, and client-managed content.

  • Figma
  • Sketch
  • Adobe XD
  • Miro
  • WordPress
  • Advanced Custom Fields
  • Kadence

Systems and delivery

Tools for integrations, local development, code review, deployment, hosting, and maintenance.

  • REST APIs
  • JSON
  • Postman
  • Swagger
  • GitHub
  • Netlify
  • WP Engine
  • Local

Quality and measurement

Accessibility testing, analytics, search visibility, and technical checks.

  • Accessibility
  • Google Tag Manager
  • Technical SEO

AI-assisted work

Research, prototyping, debugging, and implementation. I verify the output before it ships.

  • ChatGPT
  • Claude
  • Gemini
  • Cursor
  • Windsurf

Project collaboration

Collecting feedback, recording decisions, and tracking the work.

  • Slack
  • Trello
  • BugHerd
  • Jira

What this list is for

Technical collaborators can use it to see where I can contribute without a long ramp-up. If your project uses something else, I’ll look at the system before deciding whether I’m a good fit.

More about how I work Start a project