iulianpoenaru.com

What this had to do

A developer's personal site has an unusually hard job. It gets read by a hiring manager for thirty seconds, by a founder deciding whether to send a brief, and increasingly by an AI assistant answering "who builds React Native apps in Timișoara" on someone else's behalf. All three have to come away with the same answer, and none of them will scroll twice to find it.

So the first screen does the positioning and the rest of the page does the proof. An animated particle field sits behind a condensed headline, and everything a visitor needs in order to act is already there: availability, the stack, email, phone, LinkedIn, one call to action. Nothing is held back for a contact page.

The sections, and why they're in that order

Four services follow the hero, written as four ways to plug into a team rather than four packages to buy - mobile, web, backend, and the advisory work that turns a business requirement into something buildable. Each card carries its own quiet background animation, which is the kind of detail the Premium tier exists for.

The work section is the one piece of real interaction on the page. Three selected projects sit in a list on the left; picking one swaps the preview on the right without a page load, so a visitor can skim all three in a few seconds instead of scrolling through three full case studies.

Then the numbers - five-plus years, twenty shipped projects, nine technologies in production - counting up as the section comes into view. They're there because they're the fastest way to answer "has this person done this before" without asking anyone to read a CV.

The projects page

The home page shows three projects. The projects page shows the whole catalogue - around twenty builds, filterable by technology and by type (web, mobile, backend, console, desktop), each with its stack listed.

This is the page that does the heavy lifting for anyone who's already interested. It's also the page most likely to be read by a machine, which is why every project carries its stack as text rather than as a strip of logos.

Built to be found - and quoted correctly

The GEO work on this build isn't visible on the page, which is rather the point:

• JSON-LD structured data describing the person and the site, so a search engine or an assistant can state who this is and what they do without guessing it out of the prose
• a sitemap and a robots policy, so every page is discoverable rather than reachable only by scrolling the home page
• per-page titles, descriptions and Open Graph metadata, so a link shared in a message or a job thread arrives with a real preview attached

A standard-tier site gets found. A premium-tier site gets quoted correctly.

On a phone

The same build, reflowed rather than cut down - the particle field, the headline and the full contact block all survive the narrow layout.