Projects

3D Geo-Archive

Website Link

This website is a partial, interactive archive of the Modern Love column, mapping articles onto a 3D globe.

The project began out of interest in finding alternate and accessible ways to comb through large archives, including digital archives like those on the Internet Archive, as well as newspaper archives. I was particularly interested in finding different ways to comb through longrunning columns and find new articles.

I developed an interactive 3D globe visualization that maps Modern Love articles to their geographical locations. The interface allows users to explore content through spatial navigation by spinning the globe and discovering articles through hoverable points.

145 column entries (including podcasts and tiny love stories) contained geographic keywords, which were then mapped to coordinates. This filtering effect created an interesting lens into the archive - it surfaced a specific subset of stories where location plays a meaningful role in the narrative, offering a way to explore how place and relationships intersect in Modern Love stories.

I initially began by coding a 2D illustrated map of the world using D3.js before switching to a 3D globe with Three.js for easier content exploration (dragging to 'spin' the globe and ease of zooming in on the third dimension). I built a script to populate a MongoDB database by querying the New York Times API to fetch articles for the partial archive, using the Open Street Nominatim API to get a latitude and longitude, if any, from the keywords attached to the article. I originally used natural language processing of the article's contents, but keyword matching proved to be a much more accurate way of geotagging the articles if location keywords were present.

This data is served with a Node.js server to a Three.js frontend to render the articles on the globe, using a REST API built with Express.

Articles are rendered on the globe by turning the 2D latitude and longitude from the server into a scaled 3D coordinate. The interface allows users to hover over red article points to view tooltips, which contain URLs to the full article.

WB Games NY Nexus

As part of the WB Games New York annual summer hackathon, I was on a team of four engineers in creating an online gaming nexus, a centralized hub for Jackbox-esque games for the studio.

WB Games New York's annual summer hackathon presented an opportunity to create engaging multiplayer experiences for studio team-building. The studio needed a centralized platform for hosting and playing casual multiplayer games, similar to Jackbox Games, but tailored for the studio environment.

From inception, we decided to create an online gaming nexus for in-studio multiplayer team games, aka our own version of Jackbox games.

To populate the collection, I decide to engineer a web-based card game inspired by social psychology card game "Buffalo," in which teams compete in word association by drawing cards. This involved implementing a game service in C# and Blazor WebAssembly, creating the game menu for players to join games and teams, engineering the game service to serve the game (including team formation and joining, drawing cards, timeouts) and designing and implementing the user interface (including virtual cards) for real-time updates, scoring, and multiplayer capabilities.

I also redesigned the home page of the website, giving it a more modern interface for the user landing page by updating the colors, typography and homepage design. This also involved refactoring the frontend components and CSS styles.

The code is not available to the public, but feel free to reach out for more details on the project.

Confluence Validator

This app is a custom Forge solution, created to maintain documentation quality during a large cloud migration by tracking and managing content validation states.

During WB Games NY's migration to Atlassian Cloud, the IT Shared Services team faced a critical challenge: how to identify and handle potentially outdated Confluence pages before migration. Prior to my arrival as an intern, automatic archiving of inactive pages was considered, but this approach risked removing valid but infrequently updated documentation. The team needed a more nuanced solution that could distinguish between truly outdated content and stable reference material.

After speaking with team members and stakeholers to understand the problem, I decided to develop a Confluence Cloud Forge app that integrated with existing page interfaces, appearing alongside the native "last updated" feature. The app introduces two key functions: content validation and validation requests. Page owners can actively validate their content, confirming its accuracy without requiring updates, while other users can request validation when they suspect content needs review. When validation is requested, the app automatically notifies relevant team members through Slack, creating an efficient workflow for content verification.

Built using Atlassian's Forge platform, the app leverages ForgeUI components for native-looking Confluence integration, Forge Storage API for maintaining validation history, Confluence REST API for user and page management, and custom Slack webhook integration for notifications.

I originally wanted to use email (Send Grid API) or the Slack API to send notifications directly to page owners; however, limitations in the Forge API meant these integrations were not permitted. Due to Forge API limitations preventing direct email or Slack API usage, I implemented a webhook-based notification system that could be configured to route messages through team Slack channels. This workaround maintains functionality while adhering to platform constraints.

The app provides a sustainable solution for maintaining documentation quality by creating accountability through tracked validation history, enabling proactive content verification, streamlining the review process via automated notifications, and supporting informed migration decisions based on content status. The result is a tool that supported maintaining documentation's accuracy while supporting large-scale migration initiatives.

Github Link

Spotify Local Manager

While Spotify allows users to add local music files to their library, managing these files can be cumbersome. The default process requires users to navigate their file system, manually edit ID3 tags, and potentially use multiple tools for tasks like adding album artwork. Itunes offers metadata editing but the process requires more manual steps and requires then manually adding the file to a new directory to be accessed by Spotify.

The Spotify Local Manager automates the process of uploading local music files, tagging them with the correct metadata (such as artist, album, title), and embedding cover art.

Built using FastAPI for the backend, the application leverages the Mutagen library to process and modify metadata within audio files. The frontend is a React application styled with TailwindCSS. The backend supports file uploads, path management based on the user's operating system, and integrates with Spotify’s local file system.

One of the challenges was handling file path management across different operating systems (Windows, macOS, Linux). To address this, the backend dynamically determines the correct local file path based on the OS.

Github Link

PROJ NAME

content.