Repetition made the decisions clearer
I designed and developed more than twenty websites for different business needs. Each one had to remain responsive and visually consistent while carrying its own content and brand presentation. Working through that volume made recurring front-end decisions easier to see: where a layout needed a reusable rule, where a one-off adjustment was enough, and where the two should not be confused.
The repetition also made responsive work more concrete. Spacing, hierarchy, and content flow had to hold together across screen sizes, not only in the initial desktop view. Moving from one site to the next gave me a practical way to refine those decisions without forcing every project into the same template.
Design had to live inside the platform
The role included updating the front-end of five e-commerce websites and integrating custom-designed interfaces into OpenCart. Those interfaces could not be treated as static compositions. They had to work with real catalog content and remain usable within an active commerce system.
Alongside the integrations, I supported layout improvements, content updates, and interface adjustments. This connected visual presentation with the routine work required to keep a storefront clear and functional. A design decision was useful only when it could survive both the platform and the content it was meant to present.
The storefront continued after the build
I also managed product entries, website content, and daily OpenCart operations. That part of the role kept the front-end work close to the way the sites were actually maintained. Product information changed, pages needed updates, and the catalog still had to stay organized for visitors.
Together, these responsibilities developed a more operational view of front-end work. Building the interface mattered, but so did understanding the system behind it and the repeated tasks that kept it useful after the initial implementation.