Skip to Content Tyler Smith Screenshot


  • Django REST Framework
  • Next.js
  • React.js
  • Express.js
  • TypeScript
  • Chokidar
  • Tailwind CSS
  • Sass
  • CSS Modules
  • PostgreSQL
  • Nginx
  • Certbot
  • Docker
  • Docker Compose
  • Jenkins

I’ve been performing at open mics and jams for over a decade, but finding information about these events has always been troublesome. I wanted to build a web site that could help the Sacramento music community find all the open mics and jams in the region.

The Challenge

There are countless open mic listing sites on the Internet, but many have serious issues.

The biggest entity in the space is OpenMic.US, which is an international network of open mic sites for major cities across the globe. To maintain such an extensive network, they depend on user-submitted events. This has led to some event information being low quality. Sometimes, the hosting venue has gone out of business entirely. The site also prompts the user with a non-dismissable dialog to get the user’s email, which feels hostile towards the users. The site’s design feels dated.

There are also hundreds of local open mic websites across the country. These are usually created by non-developers, and as a result often have issues with mobile responsiveness and slow load times. Locally operated sites also often omit important details like signup times or age restrictions. Sometimes, these sites even charge to list events.

To build a site that would be truly useful to the Sacramento music community, I would need to source the event data myself and design a site that displays important event details upfront.


I decided I would use mobile-first design on this site. I wanted the site to look and feel like an app, as many of the users would be coming from mobile devices. The desktop site has the same general feel, but uses responsive design techniques to fit larger screens.

I displayed the most important information about each event on the homepage, so users could find events they were interested in without having to click into each event individually.

For a better user experience, I also opted to list open mics by day-of-the-week instead of using a calendar. Calendars are difficult to make usable on mobile devices, and most open mics and jams are weekly events.

An app like design on mobile browsers.

Detailed Event Information

The site lists sign-up time, start time and end time for every event. The current day’s open mics are always displayed at the very top, so a musician who is free tonight can quickly find an event. Visitors can also see if there is alcohol available at an event.

Age restrictions are displayed prominently so that young musicians can participate in the music scene. House instruments are explicitly listed to show instrumentalists where they can perform without having to go through the ordeal of moving heavy gear.

The Sacramento region is comprised of many cities spanning multiple counties, so cities are displayed at the top of the event to quickly let users assess if the event is worth the drive.

Finally, the venue’s address is on every listing’s full page, along with an interactive map and a button to get directions.

Each event has details summarized before you ever click in.

Technical Approach

The site uses Django REST Framework for the back-end, Express.js + Next.js + Tailwind CSS for the front-end, PostgreSQL as the database, and Nginx as the webserver. Because there are so many services in the app, each runs in its own Docker container, then all the containers are orchestrated using Docker Compose.

Express is used in conjunction with Next.js on the front-end to allow the site to effortlessly generate XML sitemaps on the fly. To enable hot-reloading of the Express server, Express hooks directly into Next’s Webpack config for TypeScript compilation, then Chokidar is used in a boot script for cache invalidation of server modules.

The back-end is a near-vanilla installation of Django with REST Framework used for endpoint serialization. For local development, the Django app has a command for pulling all of the event data from the production API to the local development environment, ensuring that development and production are always in sync.

Nginx acts as a reverse proxy for both the front-end and back-end. In production, the host server runs its own copy of Nginx that proxys to the Nginx container. While the setup is redundant, it allows easy configuration of Certbot on the host machine for automatic SSL certificate renewals.

To keep the feedback cycle fast, every commit to the main branch is run through a Jenkins declarative pipeline. Jenkins builds development containers then runs its tests. If the tests pass, Jenkins builds production containers, puts them in a private Docker Hub registry, then restarts the services on the production server using the new images. Jenkins also has another task that backs up the database once a day, then it places the backup on S3 compatible object storage.

Performance Optimizations

Node.js is known for its speed, and this site reaps the benefits of its performance. Next.js’s server-side rendering allows users on slower devices to get content before the JavaScript has finished parsing. Because Tailwind uses Purge CSS, production the CSS bundle is very small.

The most interesting challenge was the embedded map on the individual open mic page. I originally intended to implement this as a simple iframe, however, the iframe added 2.6 megabytes to the page load and slowed the page load speed down by over a second. To increase performance, I opted to use the Google Static Maps API, which loads a map of the location as a static image. The user is prompted to tap the map to load a full interactive view, which replaces the static image with an iframe version of the map. As a result, only the minority of users who intend to interact with the map have to incur the full load time of the iframe.

Full individual open mic page.