Skip to content
Ezequiel MagiContact

WordPress DeveloperWebsite ManagerFull Stack Developer

I take ownership of production websites from implementation through long-term maintenance — building, maintaining, optimising and troubleshooting business-critical sites with a focus on reliability, performance, security and user experience.

Email me about a role
LinkedInDownload CV

What I take responsibility for

A live site is not finished when it launches. These are the responsibilities I have held across my work — the exact scope differs by engagement, and each case study states its own.

Implementation
I build from approved designs, deciding section by section where a page builder is the right tool and where hand-written HTML, CSS and JavaScript is — so the design survives without the site becoming unmaintainable.
Maintenance
Core, theme and plugin updates on a planned cadence, with compatibility evaluated before anything is applied rather than after.
Troubleshooting
Layout and responsive regressions after deployment, and production issues on live sites — diagnosed by reviewing the affected pages at the breakpoints involved and inspecting what actually rendered, rather than guessing at the cause.
Performance
Caching and performance configuration at the application layer, and keeping the plugin surface small — plugin sprawl is one of the ordinary causes of performance decay on WordPress.
Security
Deliberate patching rather than automatic: core, theme and plugin updates applied with compatibility checked first, security tooling in place, SSL kept current, and the plugin surface kept small to reduce exposure.
Integrations
Analytics and tag management, contact forms with email delivery, REST APIs and webhooks, and embedded third-party services.
Hosting
Hosting coordination and migrations across shared and cloud environments — Hostinger, WNPower, AWS Lightsail — including SSL and subdomain setup, and coordinating with providers on issues that sit on their side of the boundary.
DNS
I configure and troubleshoot A, CNAME, TXT, MX and DKIM records across Cloudflare, GoDaddy, NIC Argentina and hosting-provider DNS, including domain verification and business email configuration.
Deployments
Deploying to production and verifying the live environment afterwards before treating the work as done — including an explicit responsive check, which exists because a regression once reached production without one.
Continuous improvement
Sites I hold get revisited, not only repaired: I review application health, updates and compatibility on my own initiative rather than waiting for a request.

Selected work

Shown as records of custody rather than launch screenshots. Each engagement states its own scope: what I decided, what I built, what I maintained, and where my responsibility ended.

Tecnodata SA

2023 — 2026

Corporate site for a Chilean IT services and consulting company

Role
Development lead — Frontend / WordPress Developer at NOVAZ Group
Implemented
Led the build of a new site from an approved design. Defined the WordPress architecture, chose the page builder and plugin stack, and hand-wrote the sections and animations the builder could not reproduce faithfully.
Maintained
Three years of core, theme and plugin updates with compatibility checked beforehand, production fixes, new pages and features, and diagnosis across the hosting boundary.
Stack
  • WordPress
  • Elementor Pro
  • HTML, CSS, JavaScript
  • WP Rocket
  • Wordfence
  • Yoast SEO

Read the case studyVisit the live site

Track record

  1. Founder & WordPress Website Manager

    2025 — Present

    WebCare

    Building and refining a WordPress maintenance and website-care service for small businesses, covering reliability, updates, security, performance, analytics and ongoing support.

  2. Frontend / WordPress Developer

    March 2023 — July 2026

    NOVAZ Group

    Led development implementation for corporate WordPress websites from approved Figma designs, defined implementation architecture, selected plugins, participated in production deployments, and maintained applications through updates, compatibility checks, fixes and new features.

  3. Frontend & WordPress Developer

    2020 — Present

    Independent

    Built and supported websites for small businesses, and handled the operational layer directly: hosting coordination, migrations, SSL, subdomains and DNS records across multiple providers.

  4. Tech Instructor

    2007 — 2020

    Informatic Training Center S.A.

    Taught technology and software topics to learners at very different levels of experience, prepared training materials, and guided hands-on exercises.

Technical proficiencies

Grouped by what they are used for. Production tools only — nothing tried once.

Building and extending sites
  • WordPress
  • Elementor Pro
  • Elementor Theme Builder
  • WooCommerce
Front-end implementation
  • HTML5
  • CSS3
  • JavaScript
  • Responsive design
  • Figma-to-code
  • Accessibility
Back-end and integrations
  • PHP
  • REST APIs
  • Webhooks
  • Contact Form 7
  • Google Analytics
  • Google Tag Manager
Hosting, DNS and deployment
  • Hostinger
  • WNPower
  • AWS Lightsail
  • Cloudflare
  • GoDaddy
  • NIC Argentina
  • SSL
  • Migrations
Performance, SEO and diagnostics
  • WP Rocket
  • Yoast SEO
  • Caching configuration
  • Production troubleshooting
Security and maintenance
  • Wordfence
  • Backups
  • Update and compatibility checks
  • Redirection

How I work

  • When a technical decision carries a trade-off the client will feel later, I put it to them in their terms before building it. On one project that meant asking the client to approve custom code for sections a page builder could not reproduce, and explaining the trade-off — visual fidelity against how easily they could edit the site afterwards. I spent thirteen years teaching technology to people at very different levels of experience, and that is most of where this comes from.
  • I document implementation details and make sure more than one person knows where the non-obvious code lives, so a project never depends on me being reachable. Having maintained one site for three years, I would now document custom sections more explicitly than I did at the start — that is the part you only learn by living with your own work.
  • I reproduce before I theorise. On a post-deployment regression that meant reviewing the affected pages at the breakpoints involved and inspecting what had actually rendered rather than guessing, correcting it, and re-verifying in production. Then I change the process so that class of problem is caught earlier — in that case, an explicit post-deployment responsive check.

Open to new roles

If you are hiring for a role that involves owning production websites, I would be glad to talk.

Email me about a role

Spanish — NativeEnglish — Conversational