RO6ONE
Trabzonspor Ro6one Robotics — FRC Team #11919
A long-form editorial site for a first-year FRC robotics team — bilingual, chaptered, built to be read rather than skimmed.
- SvelteKit
- TypeScript
- Cloudflare
- i18n (EN/TR)
Fig. 01 Depth / Motion
Index 00 / 08
Yiğit Pursalı — Leyoo, Web Developer
Web. Code. Motion.
01 Intro Identity / Practice
Yiğit Pursalı
Known online as Leyoo.I build for the screen —sites, interfaces, andthe motion between them.
Self-taught, still experimenting. Most of what I know came from building the thing, breaking it, and building it again.
- 01 Web Development
- 02 Creative Code
- 03 Interaction
- 04 Technology
02 What I Do Four disciplines / one practice
Build.
Refine.
Repeat.
Four overlapping disciplines. In practice they are one job — making something on a screen behave the way it looks like it should.
- 01
Web Development
Modern, responsive, genuinely fast websites.
- 02
Frontend Engineering
Interfaces built to hold up under real use.
- 03
Digital Products
Ideas taken from sketch to something people can open.
- 04
Creative Development
Where design, code and motion stop being separate jobs.
03 Selected Work
Selected
Work
Shipped work and the thinking behind it. Each one opens into a full case study — the projects live inside this site, not somewhere else.
Ulu Boya & Tadilat
Painting and renovation trade — Maltepe, İstanbul
A Turkish trade site built for one job: turn a search into a phone call. Warm, plain-spoken, and engineered around contact.
- Astro
- Cloudflare Workers
- Türkçe
Leyoo
This site — personal brand and portfolio
The site you are reading. A brand system and a testbed for scroll choreography, built to be the loudest thing in the portfolio.
- SvelteKit
- TypeScript
- GSAP
- Lenis
04 Process How the work happens
Process
01
Understand
Every build starts with the question underneath it. Who it is for, what it has to do, what it must never do. Defined before anything gets drawn.
02
Design
Structure first, surface second. Grid, hierarchy and rhythm — then the details that make it feel like something rather than nothing.
03
Build
Typed, componentised, measured. Fast on a mid-range phone on a bad connection, not only on the machine it was built on.
04
Refine
The last ten percent is most of the work. Timing, weight, easing — adjusted until nothing feels arbitrary.
05 Identity Who is behind this
Fig. 02 TR / 2026
Yiğit Pursalı aka Leyoo
I care about the things most people never consciously notice — how fast a page becomes usable, where the eye lands first, whether a transition finishes when it feels like it should. Get those right and the rest looks easy.
- Name
- Yiğit Pursalı
- Alias
- Leyoo
- Role
- Web Developer
- Based
- Türkiye
- Status
- Available
06 Questions Before the first call
Asked
before.
The things worth knowing before we talk. If yours is not here, ask it directly — the answer is usually one message away.
-
Marketing and brand sites, editorial and long-form sites, local business sites built around getting calls, and interactive one-offs. If it lives in a browser and the front end is the hard part, it is probably a fit. I do not take on backend-heavy platforms or app development.
-
Both, and I prefer both. Design and build are the same decision made twice, and splitting them across two people is where most of the quality leaks out. If you already have a designer or a finished design, I am happy to build to it.
-
Yes. Rebuilds and rescues are common — usually a site that looks acceptable but is slow, unreadable on a phone, or never converts. Send me the URL and I will tell you honestly whether it needs a rebuild or just work.
-
A focused single-page or local business site is usually 1–2 weeks. A multi-section site with real content and custom motion is closer to 3–6 weeks. The variable is almost never the build — it is how quickly copy, photography and decisions arrive.
-
What the site is for, who it is aimed at, and what you want someone to do after visiting it. Anything you already have — copy, logo, photography, competitors you like or hate — makes the first pass sharper. If you have none of it, we start with the brief instead.
-
Scope and quote, then design, then build, then a review round, then launch. You see it running on a real URL early rather than waiting for a big reveal, and every stage has a definition of done agreed before it starts.
-
It depends on scope, so I quote per project rather than per hour, after we have talked. Sending a budget range with your brief is not a trap — it lets me tell you straight away whether what you want fits it.
-
You get the code and the hosting under your own accounts — nothing is held hostage. I can stay on for changes and upkeep if you want it, and I am reachable afterwards either way.
07 Start a project Reply within a day
Bring me
the problem.
Four questions, about a minute. It builds a brief and hands it to email or WhatsApp — whichever you prefer. Nothing is sent anywhere until you press send.
- 01 No forms into a void — it opens your app
- 02 A rough budget saves us both a round
- 03 Not ready? Just say hello instead
Step 01 04 — Pick the closest one.
Rather skip the form? Write to pursaliyigit@gmail.com or message +90 544 359 39 71.
06 Contact Open for work
Let's build something fast.
Freelance work, collaborations, or an idea you want pressure-tested. Best reached by email — I answer everything.