What the work proves
- Information architecture for complex offers and large proof inventories
- Responsive UI systems across WordPress and Next.js
- Service-flow and operational-state mapping
- Frontend-aware decisions, accessibility checks and visual QA
Alexandra Bogdanova · Product Designer · UI/UX · Brand Systems
Complex products, clearly designed.
I turn dense offers, proof and operational constraints into understandable information architecture, responsive interfaces and implementation-ready systems.
- Best fit
- Web products · service journeys · content platforms · design systems
- Work format
- Remote employment · contract · embedded product work
- Working standard
- Clear decisions · responsive systems · implementation QA
Portfolio range
From structure to implementation.
The work combines service journeys, content products, responsive interface systems and frontend-aware decisions for complex, content-led brands.
Additional strengths
- Bilingual product and content systems
- Operational states, approval paths and recovery logic
- Direct collaboration with frontend constraints
- Structured handoff and release QA
Selected case studies
Decisions, not just screens.
Content Control Room
Context
Project data, assets, approvals and publishing actions needed a shared path rather than disconnected manual handoffs.
UX challenge
Make intake, validation, approval, publish, update, archive and error states explicit enough for implementation and review.
Key decisions
- Mapped two intake routes into one source of truth.
- Separated service responsibilities and failure states before UI polish.
- Implemented a bounded agent run with a QA gate, rollback and auditable trace.
- Output
- Product screens for intake, approval, activity and recovery connected to an agent system across Telegram, PostgreSQL, n8n, Playwright and WordPress.
- My role
- Product + System Designer / Developer
- Status
- Product design · agent systems · QA
Evidence Governance
Context
A portfolio spanning agency and independent work can create uncertainty about authorship, role and implementation status.
UX challenge
Let a recruiter or client identify relevant proof quickly while keeping every source boundary checkable.
Key decisions
- Built one reusable case model for role, source, status and boundaries.
- Separated website, system and motion proof instead of treating all work as one gallery.
- Implemented bilingual responsive routes, metadata and automated content checks.
- Output
- Bilingual Next.js portfolio, typed evidence model and product interface for publication gates.
- My role
- Product Designer + Frontend Developer
- Status
- Independent work · product design · frontend
Modern House — client journey
Context
An architecture bureau needed one public system for a broad service range, a large project archive, press proof and direct contact routes.
UX challenge
Help a prospective client understand the relevant service, trust the body of work and reach the right contact without flattening the editorial brand.
Key decisions
- Grouped service, project and press content into scannable decision layers.
- Used project proof and geography as orientation, not decorative volume.
- Kept responsive navigation and contact routes available across long-form pages.
- Output
- Live WordPress website with a source-backed local implementation package.
- My role
- Designer + Developer
- Status
- Live website · agency work at Lex Wizhevsky Architects
Working method
From ambiguity to interface.
- 01
Frame
Business goal, users, constraints, proof and the next decision.
- 02
Structure
Information architecture, priority journey, states and content model.
- 03
Interface
Critical screens, responsive logic and interaction decisions.
- 04
System
Components, hierarchy, content rules and implementation handoff.
- 05
Verify
Accessibility, responsive behaviour, source accuracy and visual QA.
Working range
Design that survives the build.
- UX
- Information architecture · user and service journeys · state mapping · content modelling
- UI
- Responsive interface systems · typography · hierarchy · component logic · interaction states
- Build
- WordPress · Elementor · Next.js · React · HTML/CSS/JavaScript · Git
- QA
- Responsive review · accessibility basics · source boundaries · content and visual checks
Role / contract fit
Need design that works in production?
Send the role, product surface and current constraint. I will reply with the closest proof and the specific part I can own.
Email Alexandra