Ádám Levente

Open to work

Email me

Ádám Levente Dániel – Web developer & software tester

Hi, I'm Ádám Levente.

A developer & tester.

Each letter of PORTFOLIO opens one part of my work. Press one, or type it.

0/10 explored · Skip intro ↓

Run your mouse across the keys · click one · or type “portfolio”.

Use the arrow keys to move between the letters and Enter or Space to press one. Each letter of PORTFOLIO stands for one part of my portfolio, and the “Jump” link takes you to it further down the page.

Overview

I build it, then I try to break it.

Final-year IT student on the software development and testing track. I build web apps from the interface to the database and deployment, and I write the test cases for them.

Status
Internships now · junior web developer roles after graduation · freelance websites on the side
Focus
Web development from interface to deployment, and software testing
Client work
lagunalovasklub.hu (live) · vityillo.eu (pre-launch)
Core stack
JavaScript · TypeScript · Supabase · Vercel · Git
Education
Final year, IT & telecommunications, TSZC Bánki Donát – Péch Antal Technical School
Based in
Hungary · available remotely
Email me
[email protected]
GitHub (opens in a new tab)
Selected work

Selected work

Two client sites, then the smaller projects. Each case study answers the same questions: what was the problem, what I built, and what came of it.

  1. 01

    Laguna Lovasklub

    Client2025 – 2026 Live

    Sole developer, from the first brief to handover and upkeep

    • Nuxt
    • Vue
    • Supabase
    • Vercel

    lagunalovasklub.hu (opens in a new tab)

    Problem
    The club needed one site for its horses, competition results, news and shop that Hungarian, English and German visitors can all read.
    Built
    • A trilingual site (Hungarian, English, German) with its own URLs per language
    • Horse listings, competition results, a blog and a webshop
    • Backend on Supabase, deployed on Vercel
    • The legal pages a shop needs: privacy, cookies, terms, data processors, returns
    Result
    • Live at lagunalovasklub.hu
    • Delivered on my own, from the first brief to handover, and still maintained by me

  2. 02

    Vityilló Vendégház

    Client2025 – now Pre-launch

    Sole developer

    • Next.js
    • React
    • TypeScript
    • Tailwind CSS
    • Zod
    • Resend
    • Vitest

    vityillo.eu (opens in a new tab) Code: private repository

    Problem
    The guesthouse needed a site where guests can check availability and send a booking request in Hungarian, English or German, with forms that meet GDPR.
    Built
    • A statically generated Next.js (App Router) site in three languages
    • Availability check and booking request, with input validated by Zod schemas on the server
    • Booking and contact emails through Resend, Google reviews through SerpApi
    • Cookie consent, and a launch checklist covering legal, GDPR, security, accessibility and indexing
    Result
    • Feature-complete; the pre-launch version is online at vityillo.eu
    • Every remaining go/no-go item is tracked in the launch checklist, with an owner
    Testing
    28 Vitest unit tests cover the API guard and the cookie consent.

More projects

  • Parking machine simulation Java console simulation of a parking machine, a team project for the software testing course, with 22 test cases. Java · Text files · Manual testing Code (opens in a new tab)
  • The PORTFOLIO keyboard intro of this site
    This portfolio Astro site with an interactive PORTFOLIO keyboard; everything below the keyboard is plain, static HTML. Astro · TypeScript · Tailwind CSS · GSAP Code: private repository
Tech stack

Tech stack

Sorted by evidence, not by how confident I feel: what runs on a live site, what I have built with, and what I am learning.

Technologies by area, sorted by where I have used them
Languages JavaScript, HTML, CSS, SQL Java, Python TypeScript, PHP
Frontend Nuxt (Vue), Tailwind CSS Next.js, React, Astro, GSAP Vue
Backend & data Supabase (Postgres) Next.js API routes, Zod, Resend, MySQL (XAMPP)
Testing Vitest, Manual & functional testing, Test cases & bug reports JUnit 5
Tools & delivery Git, GitHub, Vercel VS Code, IntelliJ IDEA, Maven, Claude Code
Experience

Experience & education

Work

  1. 2025 – 2026

    Freelance web developer · Laguna Lovasklub, Héreg

    Built and launched the riding club’s website in Hungarian, English and German, with a webshop, blog and horse listings. I still maintain it.

    Case study ↑

  2. 2025 – now

    Freelance web developer · Vityilló Vendégház, Szomód

    Booking website for a guesthouse in three languages. Feature-complete and in pre-launch review against a written launch checklist.

    Case study ↑

Education

  1. Year 5 of 5

    IT & telecommunications, software development and testing track · TSZC Bánki Donát – Péch Antal Technical School

    Final year. The parking machine simulation under Selected work is a school project.

First steps

How I learn new languages, and how I keep getting better at them.

  1. 01

    Use it on a real project

    I learn a stack by building something that has to work. Nuxt came with a client site, Next.js with a booking site and Astro with this portfolio.

    Case study: Vityilló

  2. 02

    Try it small

    I use small practice projects to try a tool, like a number-guessing game in JavaFX with a Maven build.

  3. 03

    Write it up

    To prepare for my JUnit 5 exam I built a one-page study guide to the laws of software testing and put it online.

    szoftverteszteles-alapok.vercel.app (opens in a new tab)

  4. 04

    Teach it to others

    I teach my classmates and tutor them.

Code & docs

Code & docs

How I keep a project in order

  1. Using the Scrum framework

    I plan the work as a prioritised backlog and build it in short sprints. Each sprint ends with a review of what got done and what comes next.

  2. Version control and discipline

    Every change goes through Git in small commits whose messages say what changed and why, so any version can be traced and rolled back. Secrets stay out of the repository.

  3. A checklist before go-live

    Before a client site goes live I work through a go/no-go list of legal, GDPR, security, accessibility and indexing tasks, each with an owner.

    29 checks · 8 blockers

    Go-live checklist

    What I check before a client site goes live. Items marked “Blocker” stop the launch until they are done.

    01 Go / no-go

    • Every open task is in one table with an owner (client, developer or lawyer) and a status Blocker
    • Unfinished features, such as booking or contact forms, stay switched off until the real flow is ready Blocker
    • No placeholders left: social links, sample photos, made-up reviews or ratings without a certificate
    • Test data with personal details deleted from the machine and the repository

    02 Legal pages

    • Imprint with the operator’s legal details, registration and tax numbers, and the hosting provider Blocker
    • Terms and cancellation policy final, with the real deposit and cancellation rules, reviewed by a lawyer Blocker
    • Privacy notice (GDPR Art. 13): the data, purposes, legal bases, a retention period for each purpose, processors and rights
    • Cookie and local storage notice that matches what the code actually stores
    • A licence for every photo, font, icon and logo, recorded in a licence log; consent from people who can be recognised

    03 Privacy and consent

    • No third-party request before consent: checked in the browser’s network panel on a fresh profile Blocker
    • Data processing agreements accepted with every processor: hosting, storage and email Blocker
    • “Accept all” and “Necessary only” with equal weight, no pre-ticked boxes, and consent can be changed from the footer
    • Every form field has a purpose and a legal basis, or it is removed
    • Form data is not written to disk, and logs keep only an ID, never a name or an email address

    04 Security

    • Rate limit on the form endpoints at the hosting platform’s firewall Blocker
    • Security headers: Content-Security-Policy, HSTS, nosniff, Referrer-Policy, frame and permissions policies
    • API routes check the origin, cap the body size, catch bots with a honeypot and validate input against a schema
    • No header injection: line breaks stripped from anything that goes into an email subject
    • Secrets only in environment variables and only on the server; git history scanned and npm audit clean
    • Error responses never reveal internal state; a failed email shows a real error, not a fake “thank you”

    05 Accessibility (WCAG 2.2 AA)

    • axe or Lighthouse: no serious or critical issues on any page type, in light and dark theme
    • The whole site works from the keyboard: visible focus, no traps, Esc closes dialogs and focus returns
    • Screen reader pass with NVDA and VoiceOver: headings, landmarks and form errors are read out
    • One h1 per page, alt text written for its purpose, and every field labelled with its error linked to it
    • Reduced motion respected, contrast at least 4.5:1, targets at least 24 px, no sideways scroll at 320 px or 200% zoom

    06 Indexing and launch

    • Until launch: noindex on every response, in the header and the meta tag, with no sitemap and AI crawlers blocked
    • At launch: indexing switched on in production only, then a redeploy, then the headers checked with curl Blocker
    • Sitemap submitted in Search Console; preview deployments stay noindex
    • Unit tests green, forms tested end to end, and a final check on mobile and in every major browser
    A developer’s checklist, not legal advice: the legal texts are reviewed by a lawyer before launch.

Links & demos

Beyond the code

Beyond the code

What I’m looking for

  • An internship now, in web development.
  • After graduation, a junior web developer role.
  • A team that reviews my code. I learn fastest with feedback and a mentor.
  • Freelance websites for small businesses, alongside school.

What I’m into

  • Bringing creative ideas to life.
  • AI-assisted development, which I use every day.
  • AI and machine learning.
  • Music. I’m a musician, too.
Contact

Looking for an intern or a junior developer?

Email is the fastest way to reach me. I usually reply within 24 hours.

[email protected]
Email me GitHub ↗ (opens in a new tab)

Running a small business and need a website? Same address.