Olivier Larose

Personal PortfolioVisit siteolivierlarose.com

A dramatic typographic composition expresses a front-end developer’s personality without requiring a photographic hero.

Olivier Larose — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Why this pattern works

Making a specialty memorable while keeping Blog, Contact, and LinkedIn immediately visible. The live page continues into an indexed list of client projects. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

Design notes

Mood: Expressive Developer Portfolio. A dramatic typographic composition expresses a front-end developer’s personality without requiring a photographic hero.
Colors: Near-black and warm white.
Type: A deliberate mixture of editorial serif, looping script, and pixel-style symbols.
Layout: Centered multi-line identity composition beneath minimal corner navigation.
Motion: The live hero animates; a viewport capture preserves its settled state rather than a blank scroll transition.
Texture: Typography and small symbolic ornaments provide the entire visual texture.
Imagery: Use original typography treatment and real project screenshots in the work section.
Don't: Keep experimental type out of essential navigation and ensure the hero has a stable readable state.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Olivier Larose
Source: https://www.olivierlarose.com/
Swipefile reference: https://swipefile.design/ref/personal-olivier-larose/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Expressive Developer Portfolio. A dramatic typographic composition expresses a front-end developer’s personality without requiring a photographic hero.
- colors: Near-black and warm white.
- typography: A deliberate mixture of editorial serif, looping script, and pixel-style symbols.
- layout: Centered multi-line identity composition beneath minimal corner navigation.
- motion: The live hero animates; a viewport capture preserves its settled state rather than a blank scroll transition.
- texture: Typography and small symbolic ornaments provide the entire visual texture.
- dont: Keep experimental type out of essential navigation and ensure the hero has a stable readable state.

Useful for: Making a specialty memorable while keeping Blog, Contact, and LinkedIn immediately visible. The live page continues into an indexed list of client projects. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Olivier Larose

Make it your own

Keep exploring