← All work
Web Design System
Consistency without uniformity.
A responsive design system for a complex SaaS platform, built from zero.
My role
Created and owned the system end to end
Team
Me, partnering with engineering
Platform
Responsive web: desktop, tablet, phone
Scope
Main platform and other web products
October
‹ ›
M
T
W
T
F
S
S
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Save changes
Cancel
+
All
Arriving
Departing
In-house
Blocked
Discard changes?
×
Your unsaved edits will be lost. This can’t be undone.
Cancel
Discard
Status
Status (2)
✓
Confirmed
✓
Pending
Cancelled
Email notifications
Auto-confirm requests
Sync with calendar
Guest name
Maria Alvarez
As it appears on the booking.
Confirmed
Pending
Blocked
Visuals are original illustrations created for this portfolio and do not depict proprietary product screens.
Starting from zero.
No design files, no component library, no documented patterns. Only a set of brand colors, and clients asking for a platform that looked and worked like a modern product.
One system. Every screen size.
The system powers the main platform and the company’s other web products. Every component is designed to be responsive, and adaptive where a layout needs to change, from desktop to tablet and phone browsers.
Reservations
Guest
Property
Check-in
Nights
Status
M. Alvarez
Cedar Cabin
Oct 12
3
Confirmed
J. Chen
Harbor Loft
Oct 16
5
Confirmed
R. Okafor
Harbor Loft
Oct 13
4
Pending
D. Kim
Pine Suite
Oct 20
3
Confirmed
A. Rossi
Bay House
Oct 21
4
Pending
Desktop
Full table
Reservations
Guest
Check-in
Status
M. Alvarez
Oct 12
Confirmed
J. Chen
Oct 16
Confirmed
R. Okafor
Oct 13
Pending
D. Kim
Oct 20
Confirmed
A. Rossi
Oct 21
Pending
Tablet
Priority columns
Reservations
M. Alvarez
Confirmed
Cedar Cabin · Oct 12 · 3 nights
J. Chen
Confirmed
Harbor Loft · Oct 16 · 5 nights
R. Okafor
Pending
Harbor Loft · Oct 13 · 4 nights
D. Kim
Confirmed
Pine Suite · Oct 20 · 3 nights
Phone browser
Stacked cards
Responsive, and adaptive where the layout needs to change.
Built on a proven library. Designed where it falls short.
I started from an established component library, then invested design where it wasn’t enough. Every component landed in one of three tiers: used as-is, extended, or built from scratch. The custom tier is where the complexity lives. Scheduling and booking needed calendar components no general-purpose library offers.
Email notifications
Auto-confirm requests
Sync with calendar
Used as-is
Switch
Discard changes?
×
Your unsaved edits will be lost. This can’t be undone.
Cancel
Discard
Extended
Modal, restyled to the brand
All
Arriving
Departing
In-house
Blocked
Status (2) ▾
Property
Custom
Chips and filter
Status (2) ▾
Property
⇅
✓
Confirmed
✓
Pending
Cancelled
Blocked
Count shows how many
filters are applied
Multi-select options
Icon-only variant
where space is tight
Options open in
a popup menu
A custom component, where no library option fit.
Availability
Oct 12 – 25
Week
2 weeks
Month
Status (2)
Mon
12
Tue
13
Wed
14
Thu
15
Fri
16
Sat
17
Sun
18
Mon
19
Tue
20
Wed
21
Thu
22
Fri
23
Sat
24
Sun
25
Cedar Cabin
2 bd · sleeps 6
Harbor Loft
1 bd · sleeps 2
Pine Suite
Studio · sleeps 2
Bay House
4 bd · sleeps 10
Studio 4B
Studio · sleeps 3
Ridge Villa
5 bd · sleeps 12
M. Alvarez
J. Chen
Owner stay
R. Okafor
S. Patel
L. Novak
Maintenance
D. Kim
The Morales family
A. Rossi
T. Lee
E. Walsh
K. Ahmed
Owner stay
J. Chen
Confirmed
Oct 16 – 21 · 5 nights
2 adults · 1 child
Designed from scratch: a scheduling grid concept.
90+
documented pages
3
tiers of design investment
7
sections on every component page
Organized by function. Documented the same way.
Foundations first, then components grouped by what they do. Every component page follows one template, from usage guidance to design tokens and responsive behavior. The components were implemented and remain in use across the platform.
Every component page
Overview
What it is
Usage
When to use it
Variants
Types and options
Sizes
Large, medium, small
States
Default to disabled
Design tokens
Colors and values
Responsiveness
Behavior across screens
Accessible by default.
Accessibility is part of the foundation, not a final check. The system includes accessibility guidance, and decisions about color, contrast, and text size are made once, at the system level, so every new page inherits them.
Owned end to end.
Every component, pattern, and change went through me: a single point of governance that kept the system consistent as it grew. A designer on my team contributed documentation and refinements along the way.
Built with engineering, not handed to it.
A system only works if it ships. I established the design-to-engineering handoff practices and trained engineering teams to work with the system, so components were built once and reused across the platform.
Cleaner. Easier to navigate.
More than 30 pages of the platform now run on the new system, with more moving over. Recently released pages, including a redesigned owner dashboard, drew very positive client feedback on how they look, what they show, and how they work.
A design system isn’t a library of finished UI. It’s a framework for deciding what stays consistent, what adapts, and what’s allowed to differ.
Next case study
Native Design System →
Product design leader. Design functions,
systems, and products for complex SaaS.
Work
Web design system
Native design system
Unified Inbox
AI capability
About
About
Résumé
© 2026 Alina Dohotaru
Visuals are original illustrations and do not depict proprietary product screens.
← All work
Web Design System
Consistency without uniformity.
A responsive design system for a complex SaaS platform, built from zero.
My role
Created and owned the system end to end
Team
Me, partnering with engineering
Platform
Responsive web: desktop, tablet, phone
Scope
Main platform and other web products
October
‹ ›
M
T
W
T
F
S
S
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Save changes
Cancel
+
All
Arriving
Departing
In-house
Blocked
Discard changes?
×
Your unsaved edits will be lost. This can’t be undone.
Cancel
Discard
Status
Status (2)
✓
Confirmed
✓
Pending
Cancelled
Email notifications
Auto-confirm requests
Sync with calendar
Guest name
Maria Alvarez
As it appears on the booking.
Confirmed
Pending
Blocked
Visuals are original illustrations created for this portfolio and do not depict proprietary product screens.
Starting from zero.
No design files, no component library, no documented patterns. Only a set of brand colors, and clients asking for a platform that looked and worked like a modern product.
One system. Every screen size.
The system powers the main platform and the company’s other web products. Every component is designed to be responsive, and adaptive where a layout needs to change, from desktop to tablet and phone browsers.
Reservations
Guest
Property
Check-in
Nights
Status
M. Alvarez
Cedar Cabin
Oct 12
3
Confirmed
J. Chen
Harbor Loft
Oct 16
5
Confirmed
R. Okafor
Harbor Loft
Oct 13
4
Pending
D. Kim
Pine Suite
Oct 20
3
Confirmed
A. Rossi
Bay House
Oct 21
4
Pending
Desktop
Full table
Reservations
Guest
Check-in
Status
M. Alvarez
Oct 12
Confirmed
J. Chen
Oct 16
Confirmed
R. Okafor
Oct 13
Pending
D. Kim
Oct 20
Confirmed
A. Rossi
Oct 21
Pending
Tablet
Priority columns
Reservations
M. Alvarez
Confirmed
Cedar Cabin · Oct 12 · 3 nights
J. Chen
Confirmed
Harbor Loft · Oct 16 · 5 nights
R. Okafor
Pending
Harbor Loft · Oct 13 · 4 nights
D. Kim
Confirmed
Pine Suite · Oct 20 · 3 nights
Phone browser
Stacked cards
Responsive, and adaptive where the layout needs to change.
Built on a proven library. Designed where it falls short.
I started from an established component library, then invested design where it wasn’t enough. Every component landed in one of three tiers: used as-is, extended, or built from scratch. The custom tier is where the complexity lives. Scheduling and booking needed calendar components no general-purpose library offers.
Email notifications
Auto-confirm requests
Sync with calendar
Used as-is
Switch
Discard changes?
×
Your unsaved edits will be lost. This can’t be undone.
Cancel
Discard
Extended
Modal, restyled to the brand
All
Arriving
Departing
In-house
Blocked
Status (2) ▾
Property
Custom
Chips and filter
Status (2) ▾
Property
⇅
✓
Confirmed
✓
Pending
Cancelled
Blocked
Count shows how many
filters are applied
Multi-select options
Icon-only variant
where space is tight
Options open in
a popup menu
A custom component, where no library option fit.
Availability
Oct 12 – 25
Week
2 weeks
Month
Status (2)
Mon
12
Tue
13
Wed
14
Thu
15
Fri
16
Sat
17
Sun
18
Mon
19
Tue
20
Wed
21
Thu
22
Fri
23
Sat
24
Sun
25
Cedar Cabin
2 bd · sleeps 6
Harbor Loft
1 bd · sleeps 2
Pine Suite
Studio · sleeps 2
Bay House
4 bd · sleeps 10
Studio 4B
Studio · sleeps 3
Ridge Villa
5 bd · sleeps 12
M. Alvarez
J. Chen
Owner stay
R. Okafor
S. Patel
L. Novak
Maintenance
D. Kim
The Morales family
A. Rossi
T. Lee
E. Walsh
K. Ahmed
Owner stay
J. Chen
Confirmed
Oct 16 – 21 · 5 nights
2 adults · 1 child
Designed from scratch: a scheduling grid concept.
90+
documented pages
3
tiers of design investment
7
sections on every component page
Organized by function. Documented the same way.
Foundations first, then components grouped by what they do. Every component page follows one template, from usage guidance to design tokens and responsive behavior. The components were implemented and remain in use across the platform.
Every component page
Overview
What it is
Usage
When to use it
Variants
Types and options
Sizes
Large, medium, small
States
Default to disabled
Design tokens
Colors and values
Responsiveness
Behavior across screens
Accessible by default.
Accessibility is part of the foundation, not a final check. The system includes accessibility guidance, and decisions about color, contrast, and text size are made once, at the system level, so every new page inherits them.
Owned end to end.
Every component, pattern, and change went through me: a single point of governance that kept the system consistent as it grew. A designer on my team contributed documentation and refinements along the way.
Built with engineering, not handed to it.
A system only works if it ships. I established the design-to-engineering handoff practices and trained engineering teams to work with the system, so components were built once and reused across the platform.
Cleaner. Easier to navigate.
More than 30 pages of the platform now run on the new system, with more moving over. Recently released pages, including a redesigned owner dashboard, drew very positive client feedback on how they look, what they show, and how they work.
A design system isn’t a library of finished UI. It’s a framework for deciding what stays consistent, what adapts, and what’s allowed to differ.
Next case study
Native Design System →
Product design leader. Design functions,
systems, and products for complex SaaS.
Work
Web design system
Native design system
Unified Inbox
AI capability
About
About
Résumé
© 2026 Alina Dohotaru
Visuals are original illustrations and do not depict proprietary product screens.
← All work
Web Design System
Consistency without uniformity.
A responsive design system for a complex SaaS platform, built from zero.
My role
Created and owned the system end to end
Team
Me, partnering with engineering
Platform
Responsive web: desktop, tablet, phone
Scope
Main platform and other web products
October
‹ ›
M
T
W
T
F
S
S
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Save changes
Cancel
+
All
Arriving
Departing
In-house
Blocked
Discard changes?
×
Your unsaved edits will be lost. This can’t be undone.
Cancel
Discard
Status
Status (2)
✓
Confirmed
✓
Pending
Cancelled
Email notifications
Auto-confirm requests
Sync with calendar
Guest name
Maria Alvarez
As it appears on the booking.
Confirmed
Pending
Blocked
Visuals are original illustrations created for this portfolio and do not depict proprietary product screens.
Starting from zero.
No design files, no component library, no documented patterns. Only a set of brand colors, and clients asking for a platform that looked and worked like a modern product.
One system. Every screen size.
The system powers the main platform and the company’s other web products. Every component is designed to be responsive, and adaptive where a layout needs to change, from desktop to tablet and phone browsers.
Reservations
Guest
Property
Check-in
Nights
Status
M. Alvarez
Cedar Cabin
Oct 12
3
Confirmed
J. Chen
Harbor Loft
Oct 16
5
Confirmed
R. Okafor
Harbor Loft
Oct 13
4
Pending
D. Kim
Pine Suite
Oct 20
3
Confirmed
A. Rossi
Bay House
Oct 21
4
Pending
Desktop
Full table
Reservations
Guest
Check-in
Status
M. Alvarez
Oct 12
Confirmed
J. Chen
Oct 16
Confirmed
R. Okafor
Oct 13
Pending
D. Kim
Oct 20
Confirmed
A. Rossi
Oct 21
Pending
Tablet
Priority columns
Reservations
M. Alvarez
Confirmed
Cedar Cabin · Oct 12 · 3 nights
J. Chen
Confirmed
Harbor Loft · Oct 16 · 5 nights
R. Okafor
Pending
Harbor Loft · Oct 13 · 4 nights
D. Kim
Confirmed
Pine Suite · Oct 20 · 3 nights
Phone browser
Stacked cards
Responsive, and adaptive where the layout needs to change.
Built on a proven library. Designed where it falls short.
I started from an established component library, then invested design where it wasn’t enough. Every component landed in one of three tiers: used as-is, extended, or built from scratch. The custom tier is where the complexity lives. Scheduling and booking needed calendar components no general-purpose library offers.
Email notifications
Auto-confirm requests
Sync with calendar
Used as-is
Switch
Discard changes?
×
Your unsaved edits will be lost. This can’t be undone.
Cancel
Discard
Extended
Modal, restyled to the brand
All
Arriving
Departing
In-house
Blocked
Status (2) ▾
Property
Custom
Chips and filter
Status (2) ▾
Property
⇅
✓
Confirmed
✓
Pending
Cancelled
Blocked
Count shows how many
filters are applied
Multi-select options
Icon-only variant
where space is tight
Options open in
a popup menu
A custom component, where no library option fit.
Availability
Oct 12 – 25
Week
2 weeks
Month
Status (2)
Mon
12
Tue
13
Wed
14
Thu
15
Fri
16
Sat
17
Sun
18
Mon
19
Tue
20
Wed
21
Thu
22
Fri
23
Sat
24
Sun
25
Cedar Cabin
2 bd · sleeps 6
Harbor Loft
1 bd · sleeps 2
Pine Suite
Studio · sleeps 2
Bay House
4 bd · sleeps 10
Studio 4B
Studio · sleeps 3
Ridge Villa
5 bd · sleeps 12
M. Alvarez
J. Chen
Owner stay
R. Okafor
S. Patel
L. Novak
Maintenance
D. Kim
The Morales family
A. Rossi
T. Lee
E. Walsh
K. Ahmed
Owner stay
J. Chen
Confirmed
Oct 16 – 21 · 5 nights
2 adults · 1 child
Designed from scratch: a scheduling grid concept.
90+
documented pages
3
tiers of design investment
7
sections on every component page
Organized by function. Documented the same way.
Foundations first, then components grouped by what they do. Every component page follows one template, from usage guidance to design tokens and responsive behavior. The components were implemented and remain in use across the platform.
Every component page
Overview
What it is
Usage
When to use it
Variants
Types and options
Sizes
Large, medium, small
States
Default to disabled
Design tokens
Colors and values
Responsiveness
Behavior across screens
Accessible by default.
Accessibility is part of the foundation, not a final check. The system includes accessibility guidance, and decisions about color, contrast, and text size are made once, at the system level, so every new page inherits them.
Owned end to end.
Every component, pattern, and change went through me: a single point of governance that kept the system consistent as it grew. A designer on my team contributed documentation and refinements along the way.
Built with engineering, not handed to it.
A system only works if it ships. I established the design-to-engineering handoff practices and trained engineering teams to work with the system, so components were built once and reused across the platform.
Cleaner. Easier to navigate.
More than 30 pages of the platform now run on the new system, with more moving over. Recently released pages, including a redesigned owner dashboard, drew very positive client feedback on how they look, what they show, and how they work.
A design system isn’t a library of finished UI. It’s a framework for deciding what stays consistent, what adapts, and what’s allowed to differ.
Next case study
Native Design System →
Product design leader. Design functions,
systems, and products for complex SaaS.
Work
Web design system
Native design system
Unified Inbox
AI capability
About
About
Résumé
Contact
aln.dohotaru@gmail.com
© 2026 Alina Dohotaru
Visuals are original illustrations and do not depict proprietary product screens.
← All work
Web Design System
Consistency without uniformity.
A responsive design system for a complex SaaS platform, built from zero.
My role
Created and owned the system end to end
Team
Me, partnering with engineering
Platform
Responsive web: desktop, tablet, phone
Scope
Main platform and other web products
October
‹ ›
M
T
W
T
F
S
S
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Save changes
Cancel
+
All
Arriving
Departing
In-house
Blocked
Discard changes?
×
Your unsaved edits will be lost. This can’t be undone.
Cancel
Discard
Status
Status (2)
✓
Confirmed
✓
Pending
Cancelled
Email notifications
Auto-confirm requests
Sync with calendar
Guest name
Maria Alvarez
As it appears on the booking.
Confirmed
Pending
Blocked
Visuals are original illustrations created for this portfolio and do not depict proprietary product screens.
Starting from zero.
No design files, no component library, no documented patterns. Only a set of brand colors, and clients asking for a platform that looked and worked like a modern product.
One system. Every screen size.
The system powers the main platform and the company’s other web products. Every component is designed to be responsive, and adaptive where a layout needs to change, from desktop to tablet and phone browsers.
Reservations
Guest
Property
Check-in
Nights
Status
M. Alvarez
Cedar Cabin
Oct 12
3
Confirmed
J. Chen
Harbor Loft
Oct 16
5
Confirmed
R. Okafor
Harbor Loft
Oct 13
4
Pending
D. Kim
Pine Suite
Oct 20
3
Confirmed
A. Rossi
Bay House
Oct 21
4
Pending
Desktop
Full table
Reservations
Guest
Check-in
Status
M. Alvarez
Oct 12
Confirmed
J. Chen
Oct 16
Confirmed
R. Okafor
Oct 13
Pending
D. Kim
Oct 20
Confirmed
A. Rossi
Oct 21
Pending
Tablet
Priority columns
Reservations
M. Alvarez
Confirmed
Cedar Cabin · Oct 12 · 3 nights
J. Chen
Confirmed
Harbor Loft · Oct 16 · 5 nights
R. Okafor
Pending
Harbor Loft · Oct 13 · 4 nights
D. Kim
Confirmed
Pine Suite · Oct 20 · 3 nights
Phone browser
Stacked cards
Responsive, and adaptive where the layout needs to change.
Built on a proven library. Designed where it falls short.
I started from an established component library, then invested design where it wasn’t enough. Every component landed in one of three tiers: used as-is, extended, or built from scratch. The custom tier is where the complexity lives. Scheduling and booking needed calendar components no general-purpose library offers.
Email notifications
Auto-confirm requests
Sync with calendar
Used as-is
Switch
Discard changes?
×
Your unsaved edits will be lost. This can’t be undone.
Cancel
Discard
Extended
Modal, restyled to the brand
All
Arriving
Departing
In-house
Blocked
Status (2) ▾
Property
Custom
Chips and filter
Status (2) ▾
Property
⇅
✓
Confirmed
✓
Pending
Cancelled
Blocked
Count shows how many
filters are applied
Multi-select options
Icon-only variant
where space is tight
Options open in
a popup menu
A custom component, where no library option fit.
Availability
Oct 12 – 25
Week
2 weeks
Month
Status (2)
Mon
12
Tue
13
Wed
14
Thu
15
Fri
16
Sat
17
Sun
18
Mon
19
Tue
20
Wed
21
Thu
22
Fri
23
Sat
24
Sun
25
Cedar Cabin
2 bd · sleeps 6
Harbor Loft
1 bd · sleeps 2
Pine Suite
Studio · sleeps 2
Bay House
4 bd · sleeps 10
Studio 4B
Studio · sleeps 3
Ridge Villa
5 bd · sleeps 12
M. Alvarez
J. Chen
Owner stay
R. Okafor
S. Patel
L. Novak
Maintenance
D. Kim
The Morales family
A. Rossi
T. Lee
E. Walsh
K. Ahmed
Owner stay
J. Chen
Confirmed
Oct 16 – 21 · 5 nights
2 adults · 1 child
Designed from scratch: a scheduling grid concept.
90+
documented pages
3
tiers of design investment
7
sections on every component page
Organized by function. Documented the same way.
Foundations first, then components grouped by what they do. Every component page follows one template, from usage guidance to design tokens and responsive behavior. The components were implemented and remain in use across the platform.
Every component page
Overview
What it is
Usage
When to use it
Variants
Types and options
Sizes
Large, medium, small
States
Default to disabled
Design tokens
Colors and values
Responsiveness
Behavior across screens
Accessible by default.
Accessibility is part of the foundation, not a final check. The system includes accessibility guidance, and decisions about color, contrast, and text size are made once, at the system level, so every new page inherits them.
Owned end to end.
Every component, pattern, and change went through me: a single point of governance that kept the system consistent as it grew. A designer on my team contributed documentation and refinements along the way.
Built with engineering, not handed to it.
A system only works if it ships. I established the design-to-engineering handoff practices and trained engineering teams to work with the system, so components were built once and reused across the platform.
Cleaner. Easier to navigate.
More than 30 pages of the platform now run on the new system, with more moving over. Recently released pages, including a redesigned owner dashboard, drew very positive client feedback on how they look, what they show, and how they work.
A design system isn’t a library of finished UI. It’s a framework for deciding what stays consistent, what adapts, and what’s allowed to differ.
Next case study
Native Design System →
Product design leader. Design functions,
systems, and products for complex SaaS.
Work
Web design system
Native design system
Unified Inbox
AI capability
About
About
Résumé
© 2026 Alina Dohotaru
Visuals are original illustrations and do not depict proprietary product screens.