07 Case study / 2026

300519

Personal memory archive

A personal archive bringing together memories, a travel map, special dates and a film diary, with a two-person member area and a romantic interface.

Live project Private repository

How it was built

Challenge

Bring photographs, shared places, special dates and film notes into one personal archive that is comfortable to use on a phone.

Engineering

The HTML, CSS and JavaScript interface is served through GitHub Pages. Supabase manages content, membership and private media; OpenLayers powers the map, while separate modules handle the calendar and film diary.

Outcome

Memories, map, calendar, films, a historical sky and a time capsule form six distinct sections. A two-person member area, profiles and comments sit alongside light/dark appearances and offline access to public pages.

Engineering decisions

The choices and their reasoning.

01

Separate public content and member access

Published content is available to visitors, while member operations are restricted to two accounts and multi-factor authentication. Private storage media is delivered through expiring signed URLs.

02

Manage the archive in one place

Places, albums, dates and films are edited through management tools after sign-in. Film entry imports IMDb metadata and posters; profiles and comments use the same membership system.

03

Keep the interface clear on a phone

Large headings, short navigation labels and separate tool panels share a common design language. Plum, wine and dusty rose colors accompany a remembered appearance choice and keyboard-accessible menus and galleries.

The resulting workflow

Find a memory or place → explore its map, album and dates → add to the archive from the member area.

Current content and media depend on Supabase access. Offline use covers previously visited public pages; member pages and expiring media URLs bypass the service worker cache.

Source-grounded flow

The architecture of a feature.

Public pages use the network first and fall back to their cached version offline. Member pages, write requests and external media URLs bypass the worker. This excerpt comes from the publicly served service worker.

Data flow verified in the sourcePage requestPublic GETPrivate / externalNetwork + cacheDirect network

Scroll the diagram horizontally on narrow screens. Page request · Public GET · Private / external · Network + cache · Direct network

Annotated source excerpt

Inside the implementation.

sw.js · 83–94Formatted for readability
self.addEventListener('fetch', event => {
  const request = event.request;
  if(request.method !== 'GET') return;
  const url = new URL(request.url);
  // Supabase, signed media, auth and all private pages bypass the worker.
  if(url.origin !== self.location.origin || privatePage(url)) return;
  if(request.mode === 'navigate') {
    event.respondWith(networkFirst(request));
    return;
  }
  if(staticAsset(url)) event.respondWith(staticResponse(request,event,immutable(url)));
});

Source revision: b2f8ebf ·

From the actual commit history

Development log.

  1. Made the dark appearance the default with a plum, wine and dusty rose palette.

    b2f8ebf
  2. Added a remembered light/dark appearance across pages and offline font support.

    6fcfc2f
  3. Rebuilt the shared portfolio typography, name-led opening and section cards.

    2f6dfcf

Dates are displayed in the Türkiye time zone.