Schneider

Autumn 2022 — Spring 2025

Live version

Challenge

Developing and maintaining a design system, a component library, and new pages, as well as providing long-term project support.

My Role

Frontend development

Getting Started at a Digital Agency

After university, I was eager to start working full time. I found a job fairly quickly — I was even hired without a technical interview, based on my previous work. At first, I had questions about that, but after our initial code reviews I realized I’d landed exactly where I wanted — in an environment where there was a lot to learn. I remember my first pull request being reviewed by a very meticulous colleague. In a stereotypically German fashion, every line was analyzed and commented — I had to redo everything. Honestly, it did me a world of good: I learned a lot from veterans of the craft with decades of experience.

Getting acclimated was much easier thanks to friendly colleagues, especially the team lead who hired me. Very careful, welcoming, and positive people. It’s the kind of environment that makes you want to do your best work.

About the Project

This was my first project, so I really wanted to prove myself. The project was split into parts: the main website, the shop site, and a design system with a component library. The main site was written in PHP, the shop in React, and the library in StencilJS paired with Storybook.

The main site introduced the company, promoted pen product lines, highlighted individual customer stories, covered manufacturing, and more. The shop’s purpose was to sell pens and showcase the range of available options. Both sites imported the component library. We chose StencilJS because it lets you export the library as web components for PHP integration and as React components for React integration.

Schneider Architecture

Project structure.

Component Library

The design system was based on the principles of Atomic Design. In other words, the structure followed “atoms → molecules → organisms → templates → pages”. For example, an atom is a button; a molecule could be an image, text, and a button; an organism is a sequence of sections with images, text, and buttons (possibly with different parameters); and a template is a set of various organisms.

This approach helps clearly define the component hierarchy by scale of importance. The main difficulty lies in maintenance during changes: updating component structures as designs evolve without breaking existing layouts.

Storybook Overview

Button component overview in Storybook.

Development Process

I started by learning Stencil, which came fairly easily thanks to its similarities with React: syntax, lifecycle, component architecture, and reactivity — i.e., state triggering re-renders, one-way data flow via props, and so on. The key difference is that React components can’t be integrated elsewhere, whereas Stencil generates web components that are compatible with different frameworks — React, Angular, Vue, Svelte — or plain JS, without rewriting the components.

Storybook also presented no major hurdles — it’s a convenient tool for showcasing and monitoring the entire library. It’s handy for testing not only individual components but also whole organisms, page structures, and all their variants.

Unusual Requests, Unusual Solutions

Overall, there was nothing overly complex in the project. The goal was to follow a clear structure and keep the library flexible. But one unusual module stuck with me.

The idea was to render a headline against several brush-stroke lines. The challenge: headlines had to be dynamic. I needed to write a component that accepts a prop with the text, splits it into lines automatically, and adjusts the font size so everything fits. An extra constraint was preserving a specific line pattern — e.g., the first line could be longer than the second and third, and the third longer than the second.

Final Component Overview

Final component result overview.

The solution came after 3–4 days of thinking. The algorithm ended up like this: calculate how much space is available on the page → estimate how much space each line would take at a base font size → decrease the font size until all text fits → split the text according to the target pattern.

In the end, it worked exactly as intended. Writing unusual modules with non-standard algorithms was new for me — and I enjoyed it. Of course, you have to consider performance, mobile optimizations, and a bunch of other factors in such cases. But it was a lot of fun.

Results

Main view Zoomed view Shaded view

The second iteration of the project

Conclusion

The client loved the result. Everything was delivered cleanly and precisely.

I adapted to the fast-paced agency workflow, adopted new development standards, expanded my toolkit, and tried my hand at creative coding for the first time.

Let’s work together,
or just say hello :)

hello@khurshidernazarov.uz

View case