Front-end with
Angular and React

(01) — The stack

What I build with, and when I pick each one

Angular

For applications with real state, long forms and teams that need the structure a framework imposes. TypeScript, standalone components, services and lazy-loaded routes. It is the stack behind the SKÅL Madrid rebuild.

React

For interfaces made of pieces that change fast. React 18, React Router and Vite. It is the stack I rebuilt the Djehuty Project site with: 1,269 pages and 38 routes in 224 KB of JavaScript.

Next.js

React with server rendering and file-based routes, for products that need SEO and a light first load. It is the stack behind the Retina · GAME TV rebuild.

TypeScript

By default on both. A wrong type shows up as you type it; wrong data shows up in production.

Semantic HTML5

The base for everything else. Landmarks, headings in order, labelled forms. That is half of accessibility and half of SEO, for free.

Modern CSS

Grid, container queries, custom properties, color-mix, clamp(). Fluid type and light and dark themes out of the same token set.

Tailwind CSS

Utilities over a theme of my own: the design system's semantic tokens live in the configuration, not scattered through the templates. The Retina rebuild is styled this way.

Framework-free JavaScript

When a project does not need a framework, I do not give it one. This portfolio runs without one.

Vite · Git

Build, version control and static deployment. Sites served from a CDN that do not fall over on a Sunday.

GitHub · Vercel

A repository with its history and continuous deployment: every published change can be seen live, and the code can be read, not just believed.

(02) — What is included

What a front-end engagement contains

• Implementation from the design Figma to browser, with the states the mock-up never shows: loading, empty, error, offline, absurdly long text.
• Component libraries in code The design system, built and documented. Tokens that come from one place and components that do not get duplicated by the third sprint.
• WCAG 2.2 AA accessibility Complete keyboard paths, visible focus, measured contrast and screen readers actually tested, not assumed fine.
• Performance and Core Web Vitals JavaScript weight, images served at the right format and size, fonts that do not block paint, LCP and CLS watched.
• Motion and interaction Movement that explains something, respectful of prefers-reduced-motion, and that does not cost thirty frames.
• Responsive emails and newsletters The HTML that still has to be written with tables so Outlook does not break it. Unglamorous, very necessary.
• Migrations and rescues Legacy code that has to move without losing its URLs or its content. I have done it with 1,356 PHP files.
• Technical SEO Semantic markup, structured data, hreflang, sitemap and metadata. This very site is the example.

(03) — The proof

(04) — The difference

The designer and the developer are the same person

(FAQ) — Frequently asked

What people ask before hiring me

• 01

  Do you work with Angular, React, or both?

  Both, in production. Angular when the application has complex state, long forms and a team that benefits from the structure the framework imposes; React when the interface is made of pieces and changes quickly. If your team has already chosen, I work with what they chose: the framework argument is rarely the one that decides whether the product ships well.

• 02

  Can you join an Angular or React project that has already started?

  Yes, and that is usually how it goes. The first thing I do is read: the folder structure, how state is handled, where the duplicated components are, and which conventions are written down and which only live in somebody's head. I work inside whatever conventions I find; if one needs changing, I propose it with the reasoning and the cost, I do not change it for taste.

• 03

  Do accessibility and performance come included, or are they extra?

  They come included. Accessibility is a delivery requirement, not a phase that gets cut when the calendar tightens: keyboard paths, visible focus, measured contrast and screen readers actually tested. Performance the same: JavaScript weight, images in the right format, fonts that do not block paint. I also run standalone WCAG 2.2 AA audits, with the fix list ordered by effort rather than by clause number.

• 04

  Can you build something someone else designed?

  Yes. I ask for access to the design file and to the person who made it, because there are always four states the mock-up does not show and it is faster to ask than to invent them. If the design has problems that will show up in the browser, I say so before building them, not after.

• 05

  What do you hand over at the end?

  The repository with its history, the project building and deployed, the component library documented, and a short document with the decisions I made and the ones I left open. The test for a complete handover is simple: your team should be able to add a new screen without writing to me.