Independent Learning / Frontend Fundamentals
Easybank Landing Page
An early responsive landing page built outside university coursework to get more hands-on practice with HTML, SCSS, JavaScript, and frontend implementation.
My university classes did not spend much time on frontend craft, so I took on this project for fun and to close that gap myself. I followed a YouTube tutorial and implemented the Easybank landing page while learning how HTML structure, SCSS, and JavaScript work together in a responsive interface.
This is not presented as an original product concept or a client build. Its value in the portfolio is as a clear point in my progression: a focused practice project that helped me become more comfortable turning a visual design into a working web page.
01 / Motivation
Build the frontend practice I was not getting in class.
A guided project provided enough structure to concentrate on browser layout, styling, and responsive behavior rather than product scope.
Independent learning
I chose the project outside coursework because I wanted more direct experience building polished web interfaces.
Guided implementation
Following a tutorial gave me a reference process while I learned how the code produced each part of the page.
Contained scope
A single landing page kept the work focused on frontend fundamentals instead of backend or application architecture.
02 / Practice Areas
Connect structure, styling, and behavior.
The page was a practical introduction to the layers that make a static design work across different browser sizes.
HTML structure
Page sections and content needed a clear document structure before layout rules could be applied consistently.
SCSS organization
SCSS provided a way to organize the growing set of styles while learning responsive layout techniques.
JavaScript behavior
JavaScript connected the page's interactive behavior to the visual interface instead of leaving it as a static composition.
03 / Progression
Use a tutorial as a starting point, not a finish line.
The project belongs in the portfolio because it shows an early stage of the frontend path that led to larger independent and full-stack work.
Visual translation
I became more comfortable breaking a finished design into sections, layout relationships, and reusable styling decisions.
Responsive thinking
The implementation reinforced that the same content needs intentional behavior at desktop and mobile widths.
A visible baseline
Keeping the project makes later portfolio work easier to understand as growth rather than a disconnected set of finished outcomes.