Prompt file imported from AlpTalhaYazar/portfolio-website (.codex/prompts/figma-make-portfolio-redesign-editorial-technical.md). Copyright stays with the author.

Figma Make Portfolio Redesign Prompt - Editorial Technical

Name: figma-make-portfolio-redesign-editorial-technical
Author: AlpTalhaYazar

You are Claude Opus 4.6 inside Figma Make.

You do not have access to my repository, source files, implementation details, or existing Figma structures.
Treat this prompt as the complete working brief and source of truth.
Do not assume hidden context exists outside this prompt.

Redesign my personal portfolio website from the ground up.

This is not a request for minor polish. I want a complete high-end redesign for a senior backend-focused software engineer.

The chosen direction is not open-ended:
You must design this in an editorial-technical direction.

What editorial-technical means in this project:
- Strong editorial composition
- Severe, disciplined, high-contrast layout choices
- Premium typography with intentional hierarchy
- A calm but powerful technical atmosphere
- A feeling of precision, systems thinking, and authorship
- More “engineered publication” than “startup landing page”
- More “serious technical operator” than “flashy creative coder”

Critical balance:
I want both of these at the same time:
- cool, distinctive, memorable design
- high trust and high conversion for serious hiring / consulting outcomes

Do not optimize for style alone.
Do not optimize for conversion alone.
Build a design that feels visually authored and premium, while still making it easy for a recruiter, CTO, engineering manager, or client to quickly trust me and contact me.

Important working mode:
- Do not give me multiple design directions
- Do not ask me to choose between visual concepts unless absolutely necessary
- Commit to one strong editorial-technical concept and execute it fully
- Create the actual finished redesign, not a moodboard, not a vague concept write-up
- Treat the current website as a source of content and intent, not as a visual reference to preserve

Completion rule:
- Finish the full required scope before ending the session
- Do not stop after designing only the hero
- Do not stop after making a polished first screen if the rest of the experience is weaker or incomplete
- If you choose a single-page architecture, all required sections and key states must still be fully designed
- If you choose a multi-page architecture, every necessary page must be completed before ending
- Before stopping, perform a self-check against all required deliverables and continue if anything is missing
- Do not end with “future work” or “next steps” unless every required page, section, and state is already complete

Project identity:
- Name: Alp Talha Yazar
- Positioning: Senior Backend Developer / Software Engineer
- Core specialization: .NET, C#, microservices, enterprise applications, APIs, PostgreSQL, Redis, Docker, Kubernetes
- Secondary strength: full-stack fluency with React, Next.js, TypeScript, Blazor, Tailwind CSS
- Audience: CTOs, engineering managers, technical recruiters, startup founders, and consulting clients
- Primary outcome: make me look credible, senior, technically deep, and worth contacting for serious work
- Secondary outcome: make the portfolio feel distinct from generic developer websites without becoming gimmicky

What this portfolio must communicate:
- I build robust backend systems, not just UI
- I understand reliability, scale, maintainability, and architecture
- I have enterprise-level B2B and B2G experience
- I can ship real production systems
- I also have enough product and frontend fluency to deliver complete solutions when needed
- I am modern, deliberate, and technically sharp

Business and product context:
- This is a real portfolio for hiring and consulting outcomes, not a concept site
- The site should help both quick scanning and deeper evaluation
- It should feel premium, controlled, and intentional
- I am open to remote opportunities, strong engineering teams, and serious consulting work

Current site/product context:
- The site is for www.alptalha.dev
- The current implementation is a responsive Next.js portfolio with English default and Turkish/Spanish support
- The current content model includes hero, about, experience, skills, projects, contact, footer, and a 404 page
- There are GitHub / LinkedIn / email contact actions and a contact form
- The current site includes novelty theme ideas that do not need to be preserved
- You may fully restructure the information architecture if the result is stronger

Career context:
- Senior backend-focused software engineer with roughly 4-5+ years of professional experience
- Based in Turkey, with remote-friendly positioning
- Strongest identity: backend systems, APIs, architecture, maintainability, reliability, and enterprise delivery
- Secondary identity: capable full-stack engineer with enough frontend fluency to ship polished end-to-end products

Experience inventory:
- Dias (Atlastek) | Backend Developer | 2023 - Present | Turkey
  Focus: enterprise-level B2G tracking and management systems
  Technologies: .NET 9, C#, Entity Framework Core, PostgreSQL, Redis, RabbitMQ, Docker, Kubernetes, microservices, REST APIs
  Themes: real-time monitoring, large-scale systems, operational reliability, regulated environments

- Wiro AI | Software Engineer | Jul 2023 - Aug 2024 | Istanbul, Turkey
  Focus: AI/ML infrastructure, model testing interfaces, Linux GPU workers, request distribution, APIs, monitoring
  Technologies: .NET 8, Blazor, PostgreSQL, Redis, Docker, Linux, REST APIs, Tailwind CSS, SignalR
  Themes: orchestration, internal tooling, applied AI infrastructure, visibility, system operations

- Jetlink | Full Stack Developer | 2021 - 2022 | Turkey
  Focus: chatbot platform spanning CMS, APIs, end-user UI, reporting, integrations, and modernization
  Technologies: .NET 4.7, .NET 6, ASP.NET MVC, MongoDB, WebSockets, React, TypeScript, JavaScript, IIS
  Themes: legacy modernization, full-stack delivery, platform thinking, integrations

Selected project/case-study inventory:
- Enterprise Management Platform
- Enterprise Asset Tracking System
- Wiro AI ML Infrastructure Platform
- Jetlink Multi-Project Chatbot Platform

Core capability inventory:
- Backend: .NET, C#, ASP.NET Core, Entity Framework Core, REST APIs, microservices, RabbitMQ
- Data: PostgreSQL, Redis, SQL Server, MongoDB
- Frontend: React, Next.js, TypeScript, JavaScript, Blazor, Tailwind CSS
- Platform/DevOps: Docker, Kubernetes, Linux, Git
- Engineering strengths: clean code, enterprise architecture, integrations, maintainability, scalability, production delivery

Content direction:
- Write in clear, sharp, confident English
- Keep copy concise and intelligent
- Frame the work around technical depth, systems thinking, and practical business value
- Do not invent fake metrics, fake achievements, fake testimonials, or fake case studies
- If you generate portfolio copy, derive it from the facts in this brief

Structural preference:
- A strong single-page portfolio is preferred
- Multiple pages are allowed only if they clearly improve the result
- In either case, every required page, section, and state must be fully designed before the session ends

Required structure in some form:
- Hero / introduction
- About / positioning
- Experience
- Selected projects or case-study style highlights
- Technical skills or capabilities
- Contact / conversion section
- Footer
- 404 / not found page

You may rename, merge, reorder, or reinterpret sections if that improves the narrative.

Design objective:
Create a portfolio that feels premium, editorial, technical, and highly hireable.

The design must balance:
- technical sophistication
- visual authorship
- professional trust
- clarity of positioning
- conversion strength
- a memorable but disciplined aesthetic

Art direction requirements:
- The overall look must be editorial-technical, not generic SaaS
- Typography should do heavy strategic work
- The design should feel systematized, restrained, and sharply composed
- Use an intelligent grid, spacing rhythm, and proportion system
- If you use a visual metaphor, derive it from systems, architecture, signal flow, infrastructure, reliability, data movement, or engineering precision
- Do not make it feel playful, casual, whimsical, or overly trendy

Typography direction:
- Use typography as a primary design tool, not decoration
- The headline system should feel authoritative and intentional
- Supporting typography should remain highly readable
- A mono or technical accent layer is welcome, but should be used with restraint
- The page should look premium even if imagery is minimal or absent

Color direction:
- Use a restrained palette
- A dark or near-dark foundation is acceptable and likely appropriate
- One controlled accent color is encouraged
- The accent should feel sharp and precise, not flashy or gamer-like
- The palette should support readability, authority, and subtle distinction

Layout direction:
- Compose the page like a technical editorial spread
- Strong negative space is welcome
- The first screen should feel deliberate and commanding
- Use asymmetry or tension only if it remains highly legible and intentional
- The page should retain strength below the fold, not just in the hero

Conversion and trust requirements:
- The site must not only look cool; it must also convert
- The first screen should communicate both taste and credibility
- Add trust signals early enough that the design does not feel all attitude and no proof
- Conversion should come from structure, clarity, proof, and hierarchy, not from aggressive marketing language
- The page should quickly answer:
  - who this person is
  - what level they operate at
  - what kind of systems they build
  - why they are credible
  - what the visitor should do next

Hero requirements:
- The hero should be the strongest part of the experience
- It must feel editorial-technical, not generic
- The main statement should be bold and ownable
- The hero must include a clear supporting layer that improves trust, not just style
- Include strong CTA hierarchy
- Include an early proof layer, either inside the hero or immediately adjacent to it
- The proof layer can be small and refined, but it must exist

Examples of acceptable proof layers:
- years of experience
- B2B / B2G / enterprise signals
- production systems / scale / architecture cues
- selected technologies used in credible moderation
- brief trust markers connected to real work

Guardrails:
- Avoid generic “developer portfolio” clichés
- Avoid bland startup landing page aesthetics
- Avoid lazy glassmorphism
- Avoid decorative fake dashboards with no substance
- Avoid overly sci-fi, gamer, anime, or cyberpunk styling
- Avoid making it look like a Dribbble poster with weak usability
- Avoid relying on a huge hero alone while the rest of the page becomes ordinary
- Avoid weakening readability in the name of atmosphere

Functional requirements:
- Responsive across desktop and mobile
- Accessibility-aware contrast, hierarchy, typography, and navigation
- Leave room for longer translated strings
- Do not depend on having a portrait photo unless the design works elegantly without one
- Keep contact actions clear
- Make the page strong for both fast-scanning recruiters and deeper-reading technical decision-makers

Required deliverables:
- A complete redesigned portfolio direction executed in actual page/section design form
- Desktop-ready design
- Mobile-ready design
- A reusable visual system for major UI and section patterns
- Clear component logic for CTAs, section intros, tags/pills, cards/containers, and form inputs if a form exists
- A complete 404 page in the same design language

Required surfaces and states:
- Main portfolio experience
  Includes: header/navigation, hero, about/positioning, experience, selected projects or case studies, skills/capabilities, contact/conversion, footer
- Mobile version of the main experience
- Mobile navigation behavior/state if navigation exists
- Contact area states
  Includes at minimum: default, active/focus, validation/error treatment, success state
- 404 / not found page
- Core interaction direction
  Includes hover/focus/transition behavior where relevant

Non-negotiable scope rule:
- Do not end the session after designing only part of the system
- Do not leave secondary pages or states implied but unfinished
- Do not stop at a polished homepage if the supporting experience is still weak or incomplete
- Everything required for a coherent portfolio experience must be completed in the same session

Decision rule:
If you must choose between “visually safe” and “memorable but credible,” choose memorable but credible.
If you must choose between “stylish but vague” and “stylish with proof,” choose stylish with proof.
If you must choose between “cool” and “conversion,” find the editorial-technical solution that creates both.

Final instruction:
Do not give me three options.
Do not ask me to pick an art direction.
The direction is editorial-technical.
Commit to one strong concept and execute it fully.

Final self-check before ending:
- Is the editorial-technical direction unmistakable?
- Does the design still feel highly hireable and trustworthy?
- Is there an early proof layer supporting the hero?
- Are the CTAs clear enough for conversion?
- Is the mobile experience covered?
- Is the 404 page covered?
- Are all required sections and states complete?
- If any answer is no, continue working instead of ending the session.

# Figma Make Portfolio Redesign Prompt - Editorial Technical ```text You are Claude Opus 4.6 inside Figma Make. You do not have access to my repository, source files, implementation details, or existing Figma structures. Treat this prompt as the complete working brief and source of truth. Do not assume hidden context exists outside this prompt. Redesign my personal portfolio website from the ground up. This is not a request for minor polish. I want a complete high-end redesign for a senior backend-focused software engineer. The chosen direction is not open-ended: You must design this in an editorial-technical direction. What editorial-technical means in this project: - Strong editorial composition - Severe, disciplined, high-contrast layout choices - Premium typography with intentional hierarchy - A calm but powerful technical atmosphere - A feeling of precision, systems thinking, and authorship - More “engineered publication” than “startup landing page” - More “serious technical operator” than “flashy creative coder” Critical balance: I want both of these at the same time: - cool, distinctive, memorable design - high trust and high conversion for serious hiring / consulting outcomes Do not optimize for style alone. Do not optimize for conversion alone. Build a design that feels visually authored and premium, while still making it easy for a recruiter, CTO, engineering manager, or client to quickly trust me and contact me. Important working mode: - Do not give me multiple design directions - Do not ask me to choose between visual concepts unless absolutely necessary - Commit to one strong editorial-technical concept and execute it fully - Create the actual finished redesign, not a moodboard, not a vague concept write-up - Treat the current website as a source of content and intent, not as a visual reference to preserve Completion rule: - Finish the full required scope before ending the session - Do not stop after designing only the hero - Do not stop after making a polished first screen if the rest of the experience is weaker or incomplete - If you choose a single-page architecture, all required sections and key states must still be fully designed - If you choose a multi-page architecture, every necessary page must be completed before ending - Before stopping, perform a self-check against all required deliverables and continue if anything is missing - Do not end with “future work” or “next steps” unless every required page, section, and state is already complete Project identity: - Name: Alp Talha Yazar - Positioning: Senior Backend Developer / Software Engineer - Core specialization: .NET, C#, microservices, enterprise applications, APIs, PostgreSQL, Redis, Docker, Kubernetes - Secondary strength: full-stack fluency with React, Next.js, TypeScript, Blazor, Tailwind CSS - Audience: CTOs, engineering managers, technical recruiters, startup founders, and consulting clients - Primary outcome: make me look credible, senior, technically deep, and worth contacting for serious work - Secondary outcome: make the portfolio feel distinct from generic developer websites without becoming gimmicky What this portfolio must communicate: - I build robust backend systems, not just UI - I understand reliability, scale, maintainability, and architecture - I have enterprise-level B2B and B2G experience - I can ship real production systems - I also have enough product and frontend fluency to deliver complete solutions when needed - I am modern, deliberate, and technically sharp Business and product context: - This is a real portfolio for hiring and consulting outcomes, not a concept site - The site should help both quick scanning and deeper evaluation - It should feel premium, controlled, and intentional - I am open to remote opportunities, strong engineering teams, and serious consulting work Current site/product context: - The site is for www.alptalha.dev - The current implementation is a responsive Next.js portfolio with English default and Turkish/Spanish support - The current content model includes hero, about, experience, skills, projects, contact, footer, and a 404 page - There are GitHub / LinkedIn / email contact actions and a contact form - The current site includes novelty theme ideas that do not need to be preserved - You may fully restructure the information architecture if the result is stronger Career context: - Senior backend-focused software engineer with roughly 4-5+ years of professional experience - Based in Turkey, with remote-friendly positioning - Strongest identity: backend systems, APIs, architecture, maintainability, reliability, and enterprise delivery - Secondary identity: capable full-stack engineer with enough frontend fluency to ship polished end-to-end products Experience inventory: - Dias (Atlastek) | Backend Developer | 2023 - Present | Turkey Focus: enterprise-level B2G tracking and management systems Technologies: .NET 9, C#, Entity Framework Core, PostgreSQL, Redis, RabbitMQ, Docker, Kubernetes, microservices, REST APIs Themes: real-time monitoring, large-scale systems, operational reliability, regulated environments - Wiro AI | Software Engineer | Jul 2023 - Aug 2024 | Istanbul, Turkey Focus: AI/ML infrastructure, model testing interfaces, Linux GPU workers, request distribution, APIs, monitoring Technologies: .NET 8, Blazor, PostgreSQL, Redis, Docker, Linux, REST APIs, Tailwind CSS, SignalR Themes: orchestration, internal tooling, applied AI infrastructure, visibility, system operations - Jetlink | Full Stack Developer | 2021 - 2022 | Turkey Focus: chatbot platform spanning CMS, APIs, end-user UI, reporting, integrations, and modernization Technologies: .NET 4.7, .NET 6, ASP.NET MVC, MongoDB, WebSockets, React, TypeScript, JavaScript, IIS Themes: legacy modernization, full-stack delivery, platform thinking, integrations Selected project/case-study inventory: - Enterprise Management Platform - Enterprise Asset Tracking System - Wiro AI ML Infrastructure Platform - Jetlink Multi-Project Chatbot Platform Core capability inventory: - Backend: .NET, C#, ASP.NET Core, Entity Framework Core, REST APIs, microservices, RabbitMQ - Data: PostgreSQL, Redis, SQL Server, MongoDB - Frontend: React, Next.js, TypeScript, JavaScript, Blazor, Tailwind CSS - Platform/DevOps: Docker, Kubernetes, Linux, Git - Engineering strengths: clean code, enterprise architecture, integrations, maintainability, scalability, production delivery Content direction: - Write in clear, sharp, confident English - Keep copy concise and intelligent - Frame the work around technical depth, systems thinking, and practical business value - Do not invent fake metrics, fake achievements, fake testimonials, or fake case studies - If you generate portfolio copy, derive it from the facts in this brief Structural preference: - A strong single-page portfolio is preferred - Multiple pages are allowed only if they clearly improve the result - In either case, every required page, section, and state must be fully designed before the session ends Required structure in some form: - Hero / introduction - About / positioning - Experience - Selected projects or case-study style highlights - Technical skills or capabilities - Contact / conversion section - Footer - 404 / not found page You may rename, merge, reorder, or reinterpret sections if that improves the narrative. Design objective: Create a portfolio that feels premium, editorial, technical, and highly hireable. The design must balance: - technical sophistication - visual authorship - professional trust - clarity of positioning - conversion strength - a memorable but disciplined aesthetic Art direction requirements: - The overall look must be editorial-technical, not generic SaaS - Typography should do heavy strategic work - The design should feel systematized, restrained, and sharply composed - Use an intelligent grid, spacing rhythm, and proportion system - If you use a visual metaphor, derive it from systems, architecture, signal flow, infrastructure, reliability, data movement, or engineering precision - Do not make it feel playful, casual, whimsical, or overly trendy Typography direction: - Use typography as a primary design tool, not decoration - The headline system should feel authoritative and intentional - Supporting typography should remain highly readable - A mono or technical accent layer is welcome, but should be used with restraint - The page should look premium even if imagery is minimal or absent Color direction: - Use a restrained palette - A dark or near-dark foundation is acceptable and likely appropriate - One controlled accent color is encouraged - The accent should feel sharp and precise, not flashy or gamer-like - The palette should support readability, authority, and subtle distinction Layout direction: - Compose the page like a technical editorial spread - Strong negative space is welcome - The first screen should feel deliberate and commanding - Use asymmetry or tension only if it remains highly legible and intentional - The page should retain strength below the fold, not just in the hero Conversion and trust requirements: - The site must not only look cool; it must also convert - The first screen should communicate both taste and credibility - Add trust signals early enough that the design does not feel all attitude and no proof - Conversion should come from structure, clarity, proof, and hierarchy, not from aggressive marketing language - The page should quickly answer: - who this person is - what level they operate at - what kind of systems they build - why they are credible - what the visitor should do next Hero requirements: - The hero should be the strongest part of the experience - It must feel editorial-technical, not generic - The main statement should be bold and ownable - The hero must include a clear supporting layer that improves trust, not just style - Include strong CTA hierarchy - Include an early proof layer, either inside the hero or immediately adjacent to it - The proof layer can be small and refined, but it must exist Examples of acceptable proof layers: - years of experience - B2B / B2G / enterprise signals - production systems / scale / architecture cues - selected technologies used in credible moderation - brief trust markers connected to real work Guardrails: - Avoid generic “developer portfolio” clichés - Avoid bland startup landing page aesthetics - Avoid lazy glassmorphism - Avoid decorative fake dashboards with no substance - Avoid overly sci-fi, gamer, anime, or cyberpunk styling - Avoid making it look like a Dribbble poster with weak usability - Avoid relying on a huge hero alone while the rest of the page becomes ordinary - Avoid weakening readability in the name of atmosphere Functional requirements: - Responsive across desktop and mobile - Accessibility-aware contrast, hierarchy, typography, and navigation - Leave room for longer translated strings - Do not depend on having a portrait photo unless the design works elegantly without one - Keep contact actions clear - Make the page strong for both fast-scanning recruiters and deeper-reading technical decision-makers Required deliverables: - A complete redesigned portfolio direction executed in actual page/section design form - Desktop-ready design - Mobile-ready design - A reusable visual system for major UI and section patterns - Clear component logic for CTAs, section intros, tags/pills, cards/containers, and form inputs if a form exists - A complete 404 page in the same design language Required surfaces and states: - Main portfolio experience Includes: header/navigation, hero, about/positioning, experience, selected projects or case studies, skills/capabilities, contact/conversion, footer - Mobile version of the main experience - Mobile navigation behavior/state if navigation exists - Contact area states Includes at minimum: default, active/focus, validation/error treatment, success state - 404 / not found page - Core interaction direction Includes hover/focus/transition behavior where relevant Non-negotiable scope rule: - Do not end the session after designing only part of the system - Do not leave secondary pages or states implied but unfinished - Do not stop at a polished homepage if the supporting experience is still weak or incomplete - Everything required for a coherent portfolio experience must be completed in the same session Decision rule: If you must choose between “visually safe” and “memorable but credible,” choose memorable but credible. If you must choose between “stylish but vague” and “stylish with proof,” choose stylish with proof. If you must choose between “cool” and “conversion,” find the editorial-technical solution that creates both. Final instruction: Do not give me three options. Do not ask me to pick an art direction. The direction is editorial-technical. Commit to one strong concept and execute it fully. Final self-check before ending: - Is the editorial-technical direction unmistakable? - Does the design still feel highly hireable and trustworthy? - Is there an early proof layer supporting the hero? - Are the CTAs clear enough for conversion? - Is the mobile experience covered? - Is the 404 page covered? - Are all required sections and states complete? - If any answer is no, continue working instead of ending the session. ```

{ "prompt": "# Figma Make Portfolio Redesign Prompt - Editorial Technical\n\n```text\nYou are Claude Opus 4.6 inside Figma Make.\n\nYou do not have access to my repository, source files, implementation details, or existing Figma structures.\nTreat this prompt as the complete working brief and source of truth.\nDo not assume hidden context exists outside this prompt.\n\nRedesign my personal portfolio website from the ground up.\n\nThis is not a request for minor polish. I want a complete high-end redesign for a senior backend-focused software engineer.\n\nThe chosen direction is not open-ended:\nYou must design this in an editorial-technical direction.\n\nWhat editorial-technical means in this project:\n- Strong editorial composition\n- Severe, disciplined, high-contrast layout choices\n- Premium typography with intentional hierarchy\n- A calm but powerful technical atmosphere\n- A feeling of precision, systems thinking, and authorship\n- More “engineered publication” than “startup landing page”\n- More “serious technical operator” than “flashy creative coder”\n\nCritical balance:\nI want both of these at the same time:\n- cool, distinctive, memorable design\n- high trust and high conversion for serious hiring / consulting outcomes\n\nDo not optimize for style alone.\nDo not optimize for conversion alone.\nBuild a design that feels visually authored and premium, while still making it easy for a recruiter, CTO, engineering manager, or client to quickly trust me and contact me.\n\nImportant working mode:\n- Do not give me multiple design directions\n- Do not ask me to choose between visual concepts unless absolutely necessary\n- Commit to one strong editorial-technical concept and execute it fully\n- Create the actual finished redesign, not a moodboard, not a vague concept write-up\n- Treat the current website as a source of content and intent, not as a visual reference to preserve\n\nCompletion rule:\n- Finish the full required scope before ending the session\n- Do not stop after designing only the hero\n- Do not stop after making a polished first screen if the rest of the experience is weaker or incomplete\n- If you choose a single-page architecture, all required sections and key states must still be fully designed\n- If you choose a multi-page architecture, every necessary page must be completed before ending\n- Before stopping, perform a self-check against all required deliverables and continue if anything is missing\n- Do not end with “future work” or “next steps” unless every required page, section, and state is already complete\n\nProject identity:\n- Name: Alp Talha Yazar\n- Positioning: Senior Backend Developer / Software Engineer\n- Core specialization: .NET, C#, microservices, enterprise applications, APIs, PostgreSQL, Redis, Docker, Kubernetes\n- Secondary strength: full-stack fluency with React, Next.js, TypeScript, Blazor, Tailwind CSS\n- Audience: CTOs, engineering managers, technical recruiters, startup founders, and consulting clients\n- Primary outcome: make me look credible, senior, technically deep, and worth contacting for serious work\n- Secondary outcome: make the portfolio feel distinct from generic developer websites without becoming gimmicky\n\nWhat this portfolio must communicate:\n- I build robust backend systems, not just UI\n- I understand reliability, scale, maintainability, and architecture\n- I have enterprise-level B2B and B2G experience\n- I can ship real production systems\n- I also have enough product and frontend fluency to deliver complete solutions when needed\n- I am modern, deliberate, and technically sharp\n\nBusiness and product context:\n- This is a real portfolio for hiring and consulting outcomes, not a concept site\n- The site should help both quick scanning and deeper evaluation\n- It should feel premium, controlled, and intentional\n- I am open to remote opportunities, strong engineering teams, and serious consulting work\n\nCurrent site/product context:\n- The site is for www.alptalha.dev\n- The current implementation is a responsive Next.js portfolio with English default and Turkish/Spanish support\n- The current content model includes hero, about, experience, skills, projects, contact, footer, and a 404 page\n- There are GitHub / LinkedIn / email contact actions and a contact form\n- The current site includes novelty theme ideas that do not need to be preserved\n- You may fully restructure the information architecture if the result is stronger\n\nCareer context:\n- Senior backend-focused software engineer with roughly 4-5+ years of professional experience\n- Based in Turkey, with remote-friendly positioning\n- Strongest identity: backend systems, APIs, architecture, maintainability, reliability, and enterprise delivery\n- Secondary identity: capable full-stack engineer with enough frontend fluency to ship polished end-to-end products\n\nExperience inventory:\n- Dias (Atlastek) | Backend Developer | 2023 - Present | Turkey\n Focus: enterprise-level B2G tracking and management systems\n Technologies: .NET 9, C#, Entity Framework Core, PostgreSQL, Redis, RabbitMQ, Docker, Kubernetes, microservices, REST APIs\n Themes: real-time monitoring, large-scale systems, operational reliability, regulated environments\n\n- Wiro AI | Software Engineer | Jul 2023 - Aug 2024 | Istanbul, Turkey\n Focus: AI/ML infrastructure, model testing interfaces, Linux GPU workers, request distribution, APIs, monitoring\n Technologies: .NET 8, Blazor, PostgreSQL, Redis, Docker, Linux, REST APIs, Tailwind CSS, SignalR\n Themes: orchestration, internal tooling, applied AI infrastructure, visibility, system operations\n\n- Jetlink | Full Stack Developer | 2021 - 2022 | Turkey\n Focus: chatbot platform spanning CMS, APIs, end-user UI, reporting, integrations, and modernization\n Technologies: .NET 4.7, .NET 6, ASP.NET MVC, MongoDB, WebSockets, React, TypeScript, JavaScript, IIS\n Themes: legacy modernization, full-stack delivery, platform thinking, integrations\n\nSelected project/case-study inventory:\n- Enterprise Management Platform\n- Enterprise Asset Tracking System\n- Wiro AI ML Infrastructure Platform\n- Jetlink Multi-Project Chatbot Platform\n\nCore capability inventory:\n- Backend: .NET, C#, ASP.NET Core, Entity Framework Core, REST APIs, microservices, RabbitMQ\n- Data: PostgreSQL, Redis, SQL Server, MongoDB\n- Frontend: React, Next.js, TypeScript, JavaScript, Blazor, Tailwind CSS\n- Platform/DevOps: Docker, Kubernetes, Linux, Git\n- Engineering strengths: clean code, enterprise architecture, integrations, maintainability, scalability, production delivery\n\nContent direction:\n- Write in clear, sharp, confident English\n- Keep copy concise and intelligent\n- Frame the work around technical depth, systems thinking, and practical business value\n- Do not invent fake metrics, fake achievements, fake testimonials, or fake case studies\n- If you generate portfolio copy, derive it from the facts in this brief\n\nStructural preference:\n- A strong single-page portfolio is preferred\n- Multiple pages are allowed only if they clearly improve the result\n- In either case, every required page, section, and state must be fully designed before the session ends\n\nRequired structure in some form:\n- Hero / introduction\n- About / positioning\n- Experience\n- Selected projects or case-study style highlights\n- Technical skills or capabilities\n- Contact / conversion section\n- Footer\n- 404 / not found page\n\nYou may rename, merge, reorder, or reinterpret sections if that improves the narrative.\n\nDesign objective:\nCreate a portfolio that feels premium, editorial, technical, and highly hireable.\n\nThe design must balance:\n- technical sophistication\n- visual authorship\n- professional trust\n- clarity of positioning\n- conversion strength\n- a memorable but disciplined aesthetic\n\nArt direction requirements:\n- The overall look must be editorial-technical, not generic SaaS\n- Typography should do heavy strategic work\n- The design should feel systematized, restrained, and sharply composed\n- Use an intelligent grid, spacing rhythm, and proportion system\n- If you use a visual metaphor, derive it from systems, architecture, signal flow, infrastructure, reliability, data movement, or engineering precision\n- Do not make it feel playful, casual, whimsical, or overly trendy\n\nTypography direction:\n- Use typography as a primary design tool, not decoration\n- The headline system should feel authoritative and intentional\n- Supporting typography should remain highly readable\n- A mono or technical accent layer is welcome, but should be used with restraint\n- The page should look premium even if imagery is minimal or absent\n\nColor direction:\n- Use a restrained palette\n- A dark or near-dark foundation is acceptable and likely appropriate\n- One controlled accent color is encouraged\n- The accent should feel sharp and precise, not flashy or gamer-like\n- The palette should support readability, authority, and subtle distinction\n\nLayout direction:\n- Compose the page like a technical editorial spread\n- Strong negative space is welcome\n- The first screen should feel deliberate and commanding\n- Use asymmetry or tension only if it remains highly legible and intentional\n- The page should retain strength below the fold, not just in the hero\n\nConversion and trust requirements:\n- The site must not only look cool; it must also convert\n- The first screen should communicate both taste and credibility\n- Add trust signals early enough that the design does not feel all attitude and no proof\n- Conversion should come from structure, clarity, proof, and hierarchy, not from aggressive marketing language\n- The page should quickly answer:\n - who this person is\n - what level they operate at\n - what kind of systems they build\n - why they are credible\n - what the visitor should do next\n\nHero requirements:\n- The hero should be the strongest part of the experience\n- It must feel editorial-technical, not generic\n- The main statement should be bold and ownable\n- The hero must include a clear supporting layer that improves trust, not just style\n- Include strong CTA hierarchy\n- Include an early proof layer, either inside the hero or immediately adjacent to it\n- The proof layer can be small and refined, but it must exist\n\nExamples of acceptable proof layers:\n- years of experience\n- B2B / B2G / enterprise signals\n- production systems / scale / architecture cues\n- selected technologies used in credible moderation\n- brief trust markers connected to real work\n\nGuardrails:\n- Avoid generic “developer portfolio” clichés\n- Avoid bland startup landing page aesthetics\n- Avoid lazy glassmorphism\n- Avoid decorative fake dashboards with no substance\n- Avoid overly sci-fi, gamer, anime, or cyberpunk styling\n- Avoid making it look like a Dribbble poster with weak usability\n- Avoid relying on a huge hero alone while the rest of the page becomes ordinary\n- Avoid weakening readability in the name of atmosphere\n\nFunctional requirements:\n- Responsive across desktop and mobile\n- Accessibility-aware contrast, hierarchy, typography, and navigation\n- Leave room for longer translated strings\n- Do not depend on having a portrait photo unless the design works elegantly without one\n- Keep contact actions clear\n- Make the page strong for both fast-scanning recruiters and deeper-reading technical decision-makers\n\nRequired deliverables:\n- A complete redesigned portfolio direction executed in actual page/section design form\n- Desktop-ready design\n- Mobile-ready design\n- A reusable visual system for major UI and section patterns\n- Clear component logic for CTAs, section intros, tags/pills, cards/containers, and form inputs if a form exists\n- A complete 404 page in the same design language\n\nRequired surfaces and states:\n- Main portfolio experience\n Includes: header/navigation, hero, about/positioning, experience, selected projects or case studies, skills/capabilities, contact/conversion, footer\n- Mobile version of the main experience\n- Mobile navigation behavior/state if navigation exists\n- Contact area states\n Includes at minimum: default, active/focus, validation/error treatment, success state\n- 404 / not found page\n- Core interaction direction\n Includes hover/focus/transition behavior where relevant\n\nNon-negotiable scope rule:\n- Do not end the session after designing only part of the system\n- Do not leave secondary pages or states implied but unfinished\n- Do not stop at a polished homepage if the supporting experience is still weak or incomplete\n- Everything required for a coherent portfolio experience must be completed in the same session\n\nDecision rule:\nIf you must choose between “visually safe” and “memorable but credible,” choose memorable but credible.\nIf you must choose between “stylish but vague” and “stylish with proof,” choose stylish with proof.\nIf you must choose between “cool” and “conversion,” find the editorial-technical solution that creates both.\n\nFinal instruction:\nDo not give me three options.\nDo not ask me to pick an art direction.\nThe direction is editorial-technical.\nCommit to one strong concept and execute it fully.\n\nFinal self-check before ending:\n- Is the editorial-technical direction unmistakable?\n- Does the design still feel highly hireable and trustworthy?\n- Is there an early proof layer supporting the hero?\n- Are the CTAs clear enough for conversion?\n- Is the mobile experience covered?\n- Is the 404 page covered?\n- Are all required sections and states complete?\n- If any answer is no, continue working instead of ending the session.\n```", "variables": [], "notes": "You do not have access to my repository, source files, implementation details, or existing Figma structures. Treat this prompt as the complete working brief and source of truth. Do not assume hidden context exists outside this prompt.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/AlpTalhaYazar/portfolio-website", "path": ".codex/prompts/figma-make-portfolio-redesign-editorial-technical.md", "ref": "752f48601cb6d87a6548804e1e998a07622f8f40", "url": "https://github.com/AlpTalhaYazar/portfolio-website/blob/752f48601cb6d87a6548804e1e998a07622f8f40/.codex/prompts/figma-make-portfolio-redesign-editorial-technical.md", "key": "AlpTalhaYazar/portfolio-website/.codex/prompts/figma-make-portfolio-redesign-editorial-technical.md" } } }

figma-make-portfolio-redesign-editorial-technical

About

Figma Make Portfolio Redesign Prompt - Editorial Technical

Use it

Manifest

Reviews