ANYA GUPTA

Coding AreaCode512, HTML CSS

Tools Used: Glitch, Adobe Illustrator and Photoshop

Initial Instructor: Cat Ploehn

Timeline: 3 months

Completed in 2024, (ongoing, ever evolving.)

Active since May 2024, and a continuous work-in-progress (often changing weekly), I run areacode512.glitch.me, a project I began to document the live music scene of Austin, Texas. I focus on documenting D.I.Y, or “Do-It-Yourself” spaces, as well as local artists and creatives, all with the intent of highlighting community creativity.

D.I.Y, or “Do-It-Yourself” spaces refer to spaces originally intended for one purpose, but repurposed by their owners to serve as a space to host live music or events. I document many of these locations across Austin and bordering cities, finding underserved creators who self-initiate events (despite little resources) with the goal of sponsoring community around live music. I love the enthusiasm organizers often hold when curating and sponsoring their events. I love to contribute to the event environment by providing documentation of the energy and experience one had at the event. I first designed this website, for private viewing, with the conclusion of my Introduction to Interaction design class in Spring of 2024.

I needed four major changes to the website before publishing publically:

1. Adding a photo page for people to publically access their photos

2. Adding some form of tip jar for individuals to easily compensate me when commissioned, or if they simply appreciate my work!

3. Adding a booking page, directing people to my contact information for further inquiries

4. Adapting the website for both mobile and desktop: People see images on Instagram (phone), and will likely view the website through the phone primarily!
The photo page was to be utilized primarily by small local bands, creatives and organizers, to source images from their events and utilize them for advertising, free of cost.

My goals with the photo page were the following:

A) Provide easy access to the photos for download, with buttons showing the event name and date

B) Cycle buttons in and out: if a month has passed, the button should be removed and stored in archive.

C) Users should have some way to access the larger archive if they wish to see photos from more than a month ago.

D) A unique way of displaying the button information that is not just buttons flat on a page

E) Information should be present regarding providing credit, or even compensation if photography is used on a larger scale (i.e. for larger artists documented that often have a budget for marketing) F) MUST BE RESPONSIVE! Accessible on both mobile and desktop!:

It occurred to me that each of the sections of the lens was a long rectangular section when viewed from above, similar to how a button would look. I loved the idea of being able to stack buttons and create a longer or shorter lens as time passed. I coded this concept using old events, and documented it’s responsive nature.

Want to read about the process in detail? Visit my Notion Blog!