
Yevhen Stuzhuk - Personal Portfolio
I am a Senior Software Engineer
Marketing and corporate websites
Fast Astro sites and landings: Core Web Vitals, SEO and AI-search readiness (AISO), multilingual structure, and production builds.
I build marketing, corporate, and product sites that load fast on mobile, convert for humans, and stay discoverable—in classic search, AI Overviews, and chat assistants.
Stack: Astro + TypeScript, SSR when you need previews, forms, or lightweight APIs. You get maintainable code, predictable builds, and guidance on hosting and caching.
Representative work
Recent deliveries include vf-site and stuzhuk.page—systems where marketing and corporate websites skills (Astro, SSR, Tailwind, Core Web Vitals, accessibility, SEO, AISO, JSON-LD, hreflang, i18n, content architecture, image pipeline, deployment) were applied end to end.
Those projects combined product UI, APIs, and operational concerns: roles, exports, integrations, and observability. The goal is always software your team can extend—not a one-off demo that collapses under real users.
Typical collaboration starts with a written brief: constraints, integrations, compliance, and what “done” means for the first release. We slice work into vertical milestones so you see progress every one to two weeks and can reprioritize without losing the thread.
After go-live we offer a short hypercare window: fix edge cases, tune performance, and transfer knowledge. Long-term support can stay with your in-house team or continue as a retainer—your choice.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
FAQ
Tap a question to expand the answer.
Why Astro instead of a React SPA?
Astro ships mostly static HTML with minimal JS, which helps Core Web Vitals and gives crawlers full page text without waiting for hydration.
Do you support multiple languages?
Yes: hreflang, locale-specific routes, shared components, and content in Markdown/MDX or a CMS—depending on who edits copy.
Is SEO included or a separate service?
Every launch includes a technical SEO baseline (canonical, sitemap, JSON-LD, performance). Deep AEO/GEO/AISO work is a dedicated track.
Who updates content after launch?
You can edit Markdown/MDX, use a headless CMS, or a built-in admin—scoped to what your team actually needs.
Do you optimize images?
Yes: WebP, correct dimensions for layout, lazy loading, and caching guidance so LCP does not regress after go-live.


