Kononenko Architectural Bureau

Editorial AgencyVisit sitekononenkogroup.com

Architecture leads the page, followed by a large statement and a sparse studio profile. Mixing sans and serif display type gives the project work an editorial rhythm.

Kononenko Architectural Bureau — captured interface — Page excerpt · scroll inside to explore

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

Content & media Creative tools

Why this pattern works

Architecture and design practices whose project photography should carry the presentation.

Design notes

Mood: Quiet and deliberate
Colors: White, black, neutral architecture photography
Type: Large sans statements alternating with expressive serif service text
Layout: Full-bleed project image, centered statement, second project image, then a split studio profile
Motion: Static capture of a live site. Open the source to study its interactive behavior.
Texture: Natural materials in imagery with a flat paper-like page
Don't: Adapt the hierarchy and visual principles to your own content; avoid copying the identity, imagery, or exact layout.

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: Kononenko Architectural Bureau
Source: https://kononenkogroup.com/
Swipefile reference: https://swipefile.design/ref/awwwards-kononenko-architectural-bureau/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## 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: Quiet and deliberate
- colors: White, black, neutral architecture photography
- typography: Large sans statements alternating with expressive serif service text
- layout: Full-bleed project image, centered statement, second project image, then a split studio profile
- motion: Static capture of a live site. Open the source to study its interactive behavior.
- texture: Natural materials in imagery with a flat paper-like page
- dont: Adapt the hierarchy and visual principles to your own content; avoid copying the identity, imagery, or exact layout.

Useful for: Architecture and design practices whose project photography should carry the presentation.

## 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.

Useful for: Architecture and design practices whose project photography should carry the presentation.

Kononenko Architectural Bureau

Make it your own

Keep exploring