Building an e-learning product

Overview#

At Plume, I worked as a frontend developer on an e-learning product built with React.

My work involved implementing product interfaces, integrating frontend components with REST APIs and contributing to reusable patterns across the application.

Component-driven development#

One of the main things I developed during this role was a stronger understanding of component design.

Rather than treating each screen as an isolated implementation, I learned to identify repeated behaviours and visual patterns that could be represented through reusable components and hooks.

This made the application easier to extend and reduced duplication across related learning experiences.

Interactive experiences#

The product included interactive and gamified elements rather than being a purely content-driven website.

That meant frontend behaviour, transitions and feedback were important parts of the experience.

Working on these interfaces helped me understand that animation is most useful when it communicates state or reinforces an interaction rather than existing purely as decoration.

Working with APIs#

The frontend consumed REST endpoints for application data.

This gave me practical experience handling asynchronous states such as:

• loading
• success
• empty results
• failure
• updates following user actions

These patterns became foundational to the React work I did in later roles.

What I learned#

Plume was an important step in moving from building individual React components to understanding how a production frontend fits together.

It strengthened my experience with reusable UI, API integration and maintaining consistency across a larger product.