DanielLopes
Senior Front-End Developer
Obsessed with modular components, strict types, and front-end that scales. Clean architecture, reusable systems, and code that works long after the team moves on.
Lisboa, Portugal[Featured Projects]
[Favourite Stack]
[About]
Crafting scalablefront-end systems
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.
Read My Story[Approach]
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.