Classic themes
Hand-built PHP templates, hooks and the template hierarchy. Where most of the real web still lives — and where most agencies stop looking.
Marco Lizardo — senior creative technologist — México City
Whtever WordPress you throw at me
Builders, classic themes, block themes, half-finished handoffs, plugin graveyards. I use proven tools strategically and write custom code when it matters.
Robust workflows. Enterprise stability. Zero compromise.
◆ 
◆ 
◆ 
◆ 
◆ 
◆ 
◆ 
◆ 
◆ Tools I build with
PHP
WordPress
React.js
Vue.js
Alpine.js
Tailwind CSS
Shopify
Webflow
GSAP
JavaScript (ES6+)
Git
Vite
Laravel
Livewire
AWS
Figma
TypeScript
Sass
Node.js
WooCommerce
Bricks Builder
Elementor
4+
Years building scalable systems
50+
Projects shipped on time
100%
Projects still running strong
The rchive
2020 — 2026Capabilities — no wrong starting point
However it was
lready built
Most work does not start on a blank folder. It starts on someone else's theme, someone else's builder, someone else's forty plugins. I meet the codebase where it is and make it hold.
Block & FSE
theme.json design systems, patterns, and custom blocks — native React edit UI or PHP render callbacks, whichever the team can maintain.
Inherited builders
Elementor, Bricks, Divi, WPBakery. I do not rip out what already works. I make it fast, safe, and editable by the people who own it.
Custom plugins
Scoped functionality shipped as a versioned Composer package instead of another marketplace dependency nobody updates.
Rescue & performance
Query profiling, asset diets, caching strategy, and untangling forty-plugin dependency graphs without breaking the site on Friday.
Integrations
REST and WooCommerce work, CRMs, transactional mail, third-party APIs — with retries, logging, and a failure mode that is not silence.
Workshop
Tools I build to do the work faster
When a task repeats three times it becomes tooling. These are mine — used on client work, not shelf-ware.
Read the TAW docs ↗TAW
My own theme framework: PHP blocks that own their data, a config-driven metabox engine, and a Vite pipeline. Used when a project starts clean.
Framework
taw CLI
Scaffolds a block, its class, template and stylesheet in one command. Exports and imports blocks between projects as portable ZIPs.
Scaffolding
AI layer
Skills, live introspection and static analysis so an agent can read and write theme fields safely instead of guessing at the codebase.
Agent tooling
Audit kit
Repeatable checklist and scripts for inherited sites: plugin surface, query cost, asset weight, editor experience, upgrade path.
Diagnostics
Off the clock
How I spend my days (and late nights)
Loading contribution history…
Could not load GitHub activity right now.
Less
More
Frameworks work; well-designed systems ake them invisible.
→ philosophy(): string
