LIMBITLESS SOLUTIONS
2026
Unifying Press and News Pages
Overview
Creating a structure around storytelling
As my experience expanded across product design, websites, and Framer development, my previous portfolio no longer reflected the quality or range of projects I wanted to showcase. New work was difficult to add, case studies lacked consistency, and the overall experience felt more like a collection of pages than a cohesive system.
The goal was to create a portfolio that could support detailed storytelling, scale with future projects, and communicate both my design process and visual style. Rather than treating it as a simple redesign, I approached it as a product that would continue evolving over time.
Problem
Balancing personality with clarity
Many portfolio websites struggle to find the right balance between visual expression and usability. Some prioritize aesthetics but make projects difficult to understand, while others focus heavily on process and lose any sense of personality.
I wanted to create an experience that felt visually distinctive without distracting from the work itself. The portfolio needed to support long-form storytelling, showcase a variety of project types, and remain easy to navigate across different devices. At the same time, it needed a structure that would allow future projects to be published quickly without rebuilding layouts from scratch.
FINAL PRODUCT
Manage and organize in one place
Team members can search and organize 200+ materials, view key details, and switch to Orders to track reorders all in one place.
switching between inventory and orders tab
Request and track orders
Team members and managers can view and change status of a request directly from the order tab. Managers are notified, and the request can be followed through Pending, Accepted, or Rejected states.
updating request order card
Reflection
What I learned
Designing for more than one team.
Different people cared about different parts of the product. The Finishing Team focused on the daily workflow, while my manager and developers focused on what was realistic to build. I learned to consider both sides instead of designing from only one perspective.
Simple designs take a lot of work.
The final workflow looks straightforward, but getting there meant working through existing habits, stakeholder feedback, and technical constraints. I learned that my role as a designer is to understand that complexity and turn it into something that feels simple to use.