SO.Sherlyn Olalo, home
All projects

Websites

Corporate Website

A corporate site for a global AI data processing company, with eight content sections and a protected admin dashboard the team updates themselves.

The Lifewood corporate site showing the glassmorphism hero section with teal accents, followed by the service showcase cards.

Year

2025

Role

Front-end Developer

Client

Lifewood internship

Stack

Next.js 15, React, Tailwind CSS, JavaScript

Internship build, no public deployment.

01

The problem

Lifewood needed a digital presence that communicated their expertise in AI data processing to enterprise clients and potential talent. The website had to showcase their global scale, service offerings and company culture while maintaining a premium, modern aesthetic that reflected their position in the AI industry.

02

What I built

A full corporate website with eight key sections: hero and feature showcase on the homepage, company story, service descriptions, case studies, careers, global presence map, and contact forms. The admin dashboard gives the team control over dynamic content without touching code.

What the brief actually needed

  • Scroll-reveal animations

    Entrance animations guide users through the narrative without feeling gimmicky, built with a single reusable Reveal component.

  • Glassmorphism design system

    The frosted-glass aesthetic with teal accents creates visual depth and consistency across every page.

  • Protected admin dashboard

    Non-technical team members can update open roles, testimonials and case studies securely.

Next.js 15's App Router and Turbopack made build times snappy, Tailwind's design tokens kept the dark green, yellow and teal palette consistent, and React components kept the site maintainable as content grew.

03

What I learned

This internship showed me how corporate storytelling shapes perception. The same company feels different when the website emphasises scale, culture or technical expertise. I learned to balance visual polish with performance, because animations cost something if they aren't optimised. If I revisited it, I'd add analytics to the admin panel, A/B test the hero CTAs, and integrate a CMS to fully decouple content from code.