A working toolkit, not a trophy shelf.

I use the tools that fit the problem, the team, and the system already in place.

I do not expect the list to stop growing. Learning is part of the work: understand the constraint, study the right tool, apply it carefully, and leave the system clearer than I found it.

Frontend

The browser layer: clear structure, responsive systems, and purposeful interaction.

Semantic HTML
Modern CSS
JavaScript
TypeScript
React
Next.js

Backend & APIs

The connective work behind forms, data movement, and custom application behavior.

PHP
CodeIgniter
REST APIs
Server-side forms
Plivo
Iframe integrations

CMS & content

Publishing systems shaped for both editors and the interfaces consuming their content.

WordPress
Gutenberg
Elementor
Advanced Custom Fields
Sanity CMS
Content modeling

Growth & automation

Tools used to make visitor journeys measurable, connected, and easier to operate.

Google Tag Manager
Google Analytics 4
Pardot
Chili Piper
GoHighLevel implementation
Lead-flow validation

Delivery & quality

The practices that turn working code into a dependable release.

Git
GitHub
Vercel
Responsive QA
Accessibility
Performance checks

Platform capability

GoHighLevel implementation

Comfortable treating GHL as a connected operating tool—not just a page builder. The focus is on understanding the journey, implementing the required funnels or workflows, and making the handoffs understandable for the people who maintain them.

How I keep growing

Learn in context. Test the edges. Keep what works.

01
Start with the problem
A tool is useful only when it improves the actual system or outcome.
02
Go beneath the tutorial
I learn the underlying model so I can debug, adapt, and make deliberate tradeoffs.
03
Share the understanding
Clear code, documentation, and maintainable patterns let the learning outlive one task.

Need someone who can learn the system—not just the syntax?

Let's talk about the work.

Email Aiden