A small connection.
A bigger possibility.

A contact card worth keeping.

A digital business card with a practical next step.

The premium card has its own home at /contact, pairing my portrait with a subtle reflective surface and a prominent ADD TO CONTACTS action.

Clayton Szakacs · Marketing
clay@clayszak.com
678-673-0786
tap.clayszak.com

The save action downloads a photo-enabled vCard containing my contact details. The visitor’s device handles the final confirmation to add it to their address book. Email and phone links are also available directly.

The separate /social page keeps just two destinations: Instagram @clayszak and Clayton Szakacs on LinkedIn.

My domain becomes personal infrastructure.

One identity across the web and email.

I own clayszak.com and use Cloudflare to manage its DNS. The domain gives the project a stable identity: tap.clayszak.com for the NFC/personal identity hub, and journey.clayszak.com for this project journal.

Cloudflare Email Routing forwards mail addressed to clay@clayszak.com into Gmail. Receiving mail is working. I chose to keep Gmail as my destination inbox so the public address can change without changing where I manage messages.

Sending as the custom-domain address is a separate future capability; incoming forwarding alone does not provide outgoing mail. The domain, website, and email are connected parts of the identity, with different responsibilities.

One project. Two destinations.

The tap should be simple. The story deserves room.

The first website tried to introduce the project and tell the whole story in one place. As the identity experience took shape, those became two different needs.

Now the direction is clear: tap.clayszak.com is the quick introduction. journey.clayszak.com is where I document the build, what I learn, and what comes next.

From a demo to my identity.

The landing page became something that actually feels like me.

The initial V1 paired my photo and name with two focused modes: Identity and Implant. Identity opens my Instagram and LinkedIn. Implant explains the hardware in a concise, approachable way.

The design is black-on-black, with a brief sliced-text introduction. It’s been published, and the editable files are saved in the ImplantOS repository. The photo, links, and content can evolve as the project does.

The first working version.

Before testing the hardware, I needed somewhere for the connection to lead.

With AI coding assistance, I built the first mobile-first website: a browser demo, an explanation of the idea, and my first journal entry. That initial implementation was merged into the GitHub repository.

It made the idea tangible. I could open a real page in a normal browser, think about what a visitor would understand, and start refining the experience before an actual NFC tap.

Learning how the code works—and making changes myself—is part of this project, too.

Before the first tap.

It started with a fascination for body tech—and the chance to build something of my own.

I purchased the NExT v2 and started exploring what I could do with it. The idea of carrying a connection to something I built in my own hand was what drew me in.

“I want to understand what I can build with this technology—and learn by making it my own.”

At the start of this journal, I was waiting for the implant and exploring installation arrangements. No physical NFC tests had happened yet. The first step was the web experience.

I’m documenting this for anyone curious about the project, and as a record of how I approach an idea: the decisions, experiments, setbacks, and results as they happen.