All projects

Engineering case study

Eneye Group International

A company platform I owned from design through deployment, with a responsive frontend and backend support for enquiries and managed data.

ReactTailwind CSSNode.jsExpressMongoDBAWS S3
Eneye Group International project interface
My role
Web developer
Project type
Company platform

01 — Context

Project overview

Eneye Group needed a professional platform that communicated its services clearly and provided a practical route for prospective customers to enquire.

I owned delivery from interface design through frontend and backend implementation, deployment, and ongoing content and feature maintenance.

02 — Ownership

What I was responsible for

  • Translated business requirements into the site structure and responsive interface.
  • Built the React frontend and reusable UI with Tailwind CSS.
  • Developed Express and MongoDB endpoints for enquiries and application data.
  • Integrated cloud media storage and maintained features after launch.

03 — Engineering

Key technical decisions

Clear separation of concerns

The React frontend, Express API, database models, and media storage each have a focused responsibility, making the system easier to maintain and extend.

Cloud storage for media

Using AWS S3 keeps uploaded media outside the application server and avoids tying content storage to a single deployment instance.

Reusable interface patterns

Shared components keep service, campaign, and company content visually consistent while reducing repeated implementation work.

04 — Problem solving

Challenges and approach

01

End-to-end ownership

The project required decisions across design, frontend behaviour, API integration, persistence, deployment, and maintenance rather than within a single isolated feature.

02

Reliable media management

Uploads and removals must keep application records and cloud objects aligned. Treating storage as a dedicated integration kept this responsibility explicit.

03

Turning broad requirements into usable flows

Business descriptions had to become a clear content hierarchy and enquiry path that works across desktop and mobile devices.

05 — Delivery

Outcome

The result is a deployed company platform with a maintainable React interface, enquiry support, managed data, and cloud-hosted media. I continued maintaining features and campaign content after launch; no verified public performance metrics are available.

06 — Growth

What I learned

Owning this project end to end improved how I define boundaries early, plan for operational needs such as storage, and treat post-launch maintenance as part of delivery rather than an afterthought.