Modern Front-End Applications
Find a project and return to the same shortlist.
The problem.
A reader looking for infrastructure work should be able to narrow the list, inspect a case and come back without running the search again. A colleague opening their link should land on the same project.
Role I designed and built the responsive project browser, case-study viewer and public metadata in this Next.js portfolio.
Approach I connected the filter, project viewer and browser history. Opening a project preserves the result set for navigation, while its public address works independently in a fresh tab.
Next.jsReactVercelTailwind CSSTypeScriptExplore the portfolio

How it connects.
Server rendering / responsive systems / accessible interfaces
- 01PUBLIC ALIAS
- 02SHARED ADDRESS
- 03PROJECT VIEWER
- 04ARCHIVE RETURN
Implementation evidence.
Carry the shortlist into the reader
Opening a result brings its filtered project order into the dialog. The reader can move to the next match or copy the current case’s direct link.
Coming in through a shared link
A shared link opens a standalone case study with its own title, walkthrough and project archive link. Older links still open the case inside the archive.
A case survives a reload
The viewer resolves the project from its public URL. A regression test opens a shared address, changes projects and checks the new address.
Outcomes
- A shared link opens the intended case study directly.
- Returning from a case preserves the reader’s filter and keyboard position.