[About]
A developer witha creative edge
I came into development from Marketing and Advertising — which means I never stopped caring about how things feel, not just how they work. That creative background is what pulled me toward front-end: the need to bridge storytelling and technology, and build for the web in ways that are both efficient and meaningful. I am always chasing the next tool, framework, or pattern that makes that possible. Outside of code, I am a full-time geek — films, music, and gaming take up most of the time I am not thinking about component architecture.
[Name]
Daniel Lopes
[Role]
Senior Front-End Developer
[Location]
Lisboa, Portugal
[Contact]
daniellopes24@gmail.com[Approach]
How I Work
Modular by default
Every component is built to be reused, composed, and extended. Clear props, strict types, single responsibility. If a component only works in one context, it is not done. Modular code is not a nice-to-have — it is what makes a multi-brand codebase possible in the first place.
Type safety everywhere
TypeScript end-to-end, from CMS content models through GraphQL queries to component props. No any, no guessing what shape the data has. When the CMS schema changes, the type system catches it before the browser does. Strict types are not overhead, they are the thing that lets a team move fast without breaking things.
Prototype-level detail
The gap between a Figma comp and the final build should be zero. Semantic HTML, proper accessibility, precise spacing, correct interaction states. Testing that components behave as expected, not just that they render. The craft is in the details that most users never notice but always feel.
[Experience]
Experience & Growth
VML
Senior Front-End Developer
Leading front-end architecture and defining development standards across multi-brand platforms, headless commerce, and creative web experiences.
- —Designed a component API that serves 14+ brand sites from one Next.js codebase — Tailwind theme tokens, typed props from GraphQL codegen, and per-brand render strategies (SSR, ISR, static) without conditionals
- —Built typed React component libraries with strict props contracts, single responsibility, and atomic design patterns reusable across every brand and project
- —Introduced GraphQL codegen as standard — component props generated directly from the CMS schema, eliminating manual type definitions and catching mismatches at build time
- —Integrated headless commerce SDKs into React UI flows — cross-domain auth via iframe strategy, real-time payment state across three providers, and client-side business logic for purchase limits and age gates
- —Built scroll-driven 3D experiences with Three.js, React Three Fiber, custom GLSL shaders, and GSAP ScrollTrigger — coordinating WebGL render loops with scroll-based animations without frame drops
- —Set up Storybook for isolated component development and Playwright for cross-browser E2E testing as standard tooling on every project
Wunderman Thompson
Front-End Developer
Built a multi-brand component system from scratch and delivered front-end across corporate sites, government platforms, Salesforce theming, and internal tooling.
- —Architected an atomic design component library with 20+ CMS-driven section types — each component built for composition, strict typing, and multi-brand reuse without per-brand forks
- —Built a typed GraphQL content layer from CMS to component props — content model changes break at build time, not in production, eliminating a class of runtime bugs
- —Styled Salesforce Experience Cloud for 13+ country markets from a 226-file Sass codebase — custom namespaces, mixin libraries, and a responsive grid, all without access to the source markup
- —Implemented four-language i18n routing with localized slugs, server-side translations, and dynamic form targets configurable from the CMS — zero code changes to add a new language
- —Built multi-step forms with progressive validation, URL-persisted filter state, WCAG accessibility compliance, and integration with third-party APIs handling real citizen data
- —Created print-optimized HTML/CSS for automated PDF generation with multi-brand template inheritance — CSS @page rules, bleed areas, and consistent rendering across headless browser backends
JWT
Junior Front-End Developer
Built campaign microsites, landing pages, and HTML banners under weekly agency deadlines — learning pixel-precision, cross-browser debugging, and constraint-driven CSS.
- —Hand-coded responsive microsites and landing pages in HTML5, CSS3, and vanilla JS — pixel-perfect builds from design comps under tight weekly deadlines
- —Built custom CSS animation frameworks for display banners across ad server environments (Adform, MRAID) — each with different rendering constraints and file size limits
- —Cross-browser debugging down to IE11 — developed a discipline around progressive enhancement, defensive CSS, and fallback patterns that still informs every build
- —Learned to build under extreme constraints: no frameworks, no build tools, strict file size budgets, and rendering across ad servers, email clients, and in-app webviews
[Education]
Background
Front-End Development Specialization
ETIC — Escola de Tecnologias, Inovação e Criação
Postgraduate in Advertising & Creative Strategy
IADE — Creative University
Bachelor's in Marketing and Advertising
Universidade Lusíada de Lisboa