Frontend Developer · Product and systems thinking

I turn complex requirements into clear, reliable web products.

I build responsive websites, frontend applications and content systems for small businesses, B2B teams, cultural organisations and institutions.

View selected work Start a conversation

Italy · Remote collaboration

Portfolio indexRequirements → system → evidence

01
Buildinterfaces, flows and systems
02
Documentdecisions, ownership and constraints
03
Verifybehaviour, release and limitations

Evidence-backed workResponsive-first implementationDocumented decisionsTransparent limitations

Selected work

Different problems. One standard of proof.

I work at the intersection of frontend implementation, product thinking and systems thinking, especially where content, requirements, dependencies and responsibility need to become clear.

01Institutional · Editorial frontend

Via Flaminia Festival

Turning a distributed cultural programme into a readable, responsive and verifiable digital experience.

Read case details

My role: Frontend implementation, content structure and release verification.
Context: Seven municipalities, multiple venues, dates, biographies, booking links and institutional responsibilities had to become one coherent experience.
Contribution: Modelled events and locations, implemented the React/Vite interface, structured the navigation and verified the published release.
Evidence: Live project, release v7_v3, responsive checks and implementation notes.

Read case study ↗Live project

02Frontend application · Modular JavaScript

Personal Finance App

A stateful frontend application built with modular JavaScript, explicit domain state, routing, persistence and automated tests.

Read case details

My role: Frontend implementation, architecture, documentation and automated verification.
Context: The visual design, starter data, fonts and image assets originate from Frontend Mentor; the implementation turns the brief into a framework-free application with explicit boundaries.
Contribution: Implemented native ES modules, domain actions, pure selectors, UI state, hash routing, persistence, reusable views and components, currency API integration and the automated test harness.
Evidence: Live application, public repository, requirements contract, system model, unit tests and integration tests.

Read case study ↗Live application Repository

03Digital systems · Operations

Sfere di Luce

Building a complete digital-commercial ecosystem from zero: offer, content, funnel, booking, payments, delivery and measurement.

Read case details

My role: Digital systems strategy, offer architecture, end-to-end flow coordination and operational governance.
Context: At the start there was no integrated digital-commercial structure. The offer, editorial presence, acquisition flows, booking, payments, delivery, email automation and analytics had to be designed and connected.
Contribution: Built the system from the ground up: defined the offer and funnel, structured the digital presence, coordinated the visual work, connected booking, payments, delivery and automation, then reverse-engineered the result into a governed system.
Evidence: Public project, internal case study, system map, evidence register, flow validation and remediation roadmap.

Read case study ↗Public project

04Systems engineering · C

AxonLA

A compact C17 linear algebra library exploring API design, memory ownership, numerical kernels and testable systems structure.

Read case details

My role: Systems project author.
Context: The project moves beyond interface work into explicit ownership, aligned allocation, dense kernels, decompositions, solvers, tests and benchmarks.
Contribution: Designed the public API and implementation structure, added tests and examples, and documented performance and known limits.
Evidence: Public repository, local build, test suite, benchmark output and project documentation.

Read case study ↗Repository

05Frontend implementation · Lead capture

FitPages

A responsive landing page with structured sections, pricing, contact flow and CTA-oriented interaction points.

Read case details

My role: Frontend implementation and interaction structure.
Context: A multi-section marketing interface needed to remain readable across devices while making the next action explicit.
Contribution: Implemented the responsive layout, page sections, form path and interaction points using semantic frontend structure.
Evidence: Live deployment and project screenshot; outcome data is not claimed.

Read case study ↗Live project

Frontend practice archive

Small components and focused exercises remain available as implementation evidence, but they are not presented as equivalent to the larger case studies.

Explore the archive ↗

Capabilities

Useful at the boundary between content, interface and system.

The emphasis is not a long technology list. It is the ability to make a real requirement clearer, build the relevant path and leave evidence behind.

Frontend systems

Semantic, responsive interfaces with clear structure, reusable sections and maintainable client-side behaviour.

Content and interaction

Editorial hierarchies, event information, form flows, validation states and interactions that remain understandable across devices.

Measurement-ready interfaces

Practical event models and conversion paths that make important interactions observable without making measurement the primary product.

Systems thinking

From commercial ecosystems to a C library: I make requirements, dependencies, ownership and verification visible.

Ways I can help

One core capability, three contexts.

Services are deliberately scoped around the problems demonstrated by the work. A first conversation is used to clarify context, constraints and the right level of intervention.

For small businesses and independent professionals

A web presence people can understand and act on.

Focused websites, landing pages and contact flows that make the next step clear without adding unnecessary complexity.

Landing or site structure
Contact and booking flows
Responsive implementation
Measurement foundations

For B2B teams

Frontend systems that make a commercial path easier to inspect.

Interfaces, forms and measurement-ready workflows that connect product communication with useful operational signals.

Frontend implementation
CTA and form flow review
Event model and handoff
Prioritised technical recommendations

For institutions and cultural organisations

Editorial experiences for complex programmes and real audiences.

Clear digital structures for events, places, programmes and institutional content, with attention to data ownership and responsive access.

Content and event structure
Responsive editorial UI
Places, dates and navigation
Release and QA documentation

How I work

Clarity before surface complexity.

A small, explicit process makes collaboration safer for a sole proprietor, a B2B team or an institution.

Clarify

Turn the requirements into constraints, ownership and a definition of done.

Structure

Choose the content, interface and technical model before adding surface complexity.

Build

Implement the smallest coherent system and make important states and dependencies visible.

Verify

Check the result across devices, links, forms, accessibility basics and documented limitations.

About

Technical work should make responsibility visible.

I work at the intersection of frontend implementation, product thinking and systems thinking. I am particularly interested in projects where content, requirements, dependencies and responsibility need to become clear before they can become reliable software.

ScopeWhat is included, what is not, and what remains to be verified.
OwnershipWhat I personally designed, implemented, debugged or documented.
EvidenceLive links, repositories, tests, release notes or explicit limitations.

Contact

Start a conversation

Tell me what you are trying to build, improve or understand. The form accepts project, collaboration, employment and other requests.

landing.fast0@gmail.com LinkedIn ↗GitHub ↗