Worksaimon-islam-portfolio-nextjs

Saimon Islam Portfolio

I built a photography portfolio for Saimon Islam: a single-page site with albums, an image lightbox, achievements and a contact section, plus an admin area where the owner adds and edits albums, images and achievements…

Role
Full Stack Developer
Timeline
Mar 2025
Main stack
Next.js & Firebase
Saimon Islam Portfolio — Next.js & Firebase project screenshot

Overview

I built a photography portfolio for Saimon Islam: a single-page site with albums, an image lightbox, achievements and a contact section, plus an admin area where the owner adds and edits albums, images and achievements himself. It runs on Next.js with Firebase.

Problem

A photographer needs a portfolio that looks good and can change often. Hard-coded pages mean asking a developer every time a new album or award needs to go up, and large photos slow a site down.

Approach

I built a fast single-page site with a dark and light theme, then added a small admin area. The owner signs in, creates albums, adds images by pasting a Google Drive link, and records achievements. The site reads everything from Firebase, so new work appears without a code change.

Outcome

Public page
1
Admin screens
10
Content types
3
Commits
47

What I built

  • Single-page portfolio with home, work, achievements, about and contact sections
  • Albums and image galleries with a full-screen lightbox
  • Achievements section the owner can update
  • Dark and light theme with a toggle
  • Contact form validated with Zod and React Hook Form
  • Admin login with Firebase Authentication
  • Admin screens to add, edit and delete albums and images, and to manage achievements
  • Google Drive links converted automatically into displayable image URLs
  • Responsive layout and Vercel Analytics

Architecture

System architecture

Diagram: a Next.js site using Firebase and Google Drive.
Photos stay in Drive. Firebase holds the albums, image records and achievements. Open full size ↗

Content update flow

Diagram: sign in, add, link and publish.
The owner adds work through a form. No developer or deploy is needed. Open full size ↗

Page structure

Diagram: home, work, achievements, about and contact.
A single page that tells the story in order. Open full size ↗

Engineering decisions

  1. 01An admin instead of hard-coded content

    Albums, images and achievements live in Firestore. The owner updates them himself, and the site stays current without a developer.

  2. 02Photos stay in Google Drive

    Originals are not copied into the app. A small helper turns a Drive share link into an image URL, so storage costs stay at zero.

  3. 03One page, not a maze

    A photographer is judged by the work. A single scrolling page gets visitors to the albums quickly, with a lightbox for a closer look.

  4. 04Admin routes behind sign-in

    Every admin screen needs a Firebase login. Public visitors only read, and cannot change content.

Need something similar?

Tell me what you are building and I will reply within one working day.

Start a project
↑↓ navigate↵ openesc closeCtrl K toggles this menu