Tools used:

• The frontend is written in React/Typescript. It uses React Router, Vite, and Tailwind
• The frontend builds & deploys via Netlify
• The backend is a REST API written in Python with Flask, and is deployed to Heroku
• The database runs on Supabase
• True random numbers for the card selection powered by the Random.org API
• Tarot card images processed with Imagemagick

Highlights:

• Every tarot pull gets a unique URL that can be shared with others
• Light/dark themes controlled by device theme (with favicon variations)
• Dynamic emoji show current moon phase, and the moon phase at the time of each tarot pull
• Page transitions created with the new browser standard View Transition API

Tools used:

• Eleventy static site generator, running on Node.js
• Automatic build & deploy via Netlify

Highlights:

• Custom build configs written in JavaScript for shortcodes and other build-time goodies (code)
• Custom video embeds via the Vimeo Developer API, with thumbnail images and a JavaScript-free fallback via the html5 video tag
• Custom music player written in JavaScript for embedding music albums (demo, code)
• Custom lightbox viewer in JavaScript for image galleries based on Simple Lightbox (demo - scroll down and click any image to open lightbox)
• Custom templates written in Liquid
• Font subsetting with Python FontTools for improved site load performance

Tools used:

• The static website is built with Eleventy and deployed via Netlify, similarly to my main personal website
• Embedded interactive sketches created with:
  • GLSL (fragment shaders)
  • p5.js
  • Three.js
• The Three.js sketch features a 3D model created in Houdini

Highlights:

• A dark/light mode that initializes based on the device preference, and saves the toggled state for future visits
• Text-adventure inspired minimalist interface for project navigation
• Interactive WebGL experiments and creative coding sketches

Tools used:

• Twilio serverless function running Node.js
  • Twilio provides a phone number to receive incoming SMS, and an API endpoint for launching a function when a new message is received, as well as sending outgoing SMS messages
• WriteFreely, an open-source blog platform with an API
  • The WriteFreely instance, hosted on my server, provides the front-end blog site, as well as an RSS feed and ActivityPub stream
• ImgBB, an image hosting service with an API

Highlights:

• I wrote a bridge that takes incoming SMS text and image messages and posts them to the WriteFreely blog
• It also replies via SMS with the blog URL once the new post is created
• There is no authentication required to post, but you need to know the phone number, which is shared only by word of mouth
• Can accept messages with multiple attachments, and will include all image attachments in the blog post
• Text-only posts are also supported
• When the Twilio phone number is called, it plays an audio message with instructions for posting to the blog

Tools used:

• JavaScript front-end
• RESTful API microservices built with Flask
• Custom integrations with external vendor APIs and enterprise software products:
  • IBM Aspera Orchestrator
  • AWS Elemental MediaConvert
  • Rev Transcription and Caption API
  • SyncWords API
  • 3play Media API
  • Emotion Systems Engine
  • TeleStream Vantage and ContentAgent

Highlights:

• I built a custom Flask API that allowed Mediary users to interchangeably order captions from an array of vendor options
  • Each of our captioning vendors had their own unique API and configuration options. The universal caption API I built allowed a caption order to be placed to any of these vendors using a normalized payload
• I built an integration with AWS Elemental MediaConvert that allowed Mediary users to launch jobs to AWS's cloud-based media encoding service
  • Previously, all of our media encoding was done with on-premises hardware; this integration helped transiton the department's infrastructure dependencies to the cloud
• I developed a unified template for all workflows to follow, improving consistency and maintainability
• I also created detailed documentation for all the projects listed above
• My team oversaw the transition of the Mediary app and its users to fully remote, cloud-based workflows, allowing them to seamlessly continue their work at the start of the pandemic

Tools used:

• The web forum runs on Discourse, an open-source forum software with a Rails back-end and an Ember.js front-end
• We also administrate a Peertube instance to provide video hosting to the community

Highlights:

• I built a custom Discourse theme component for a collapsible embedded chat widget. This became a proof-of-concept for an official plugin by Communiteq, a managed Discourse hosting service
• I also built a custom Discourse theme component for adding an embedded livestream video to the forum during live online events. It was initially a customized player based on video.js, but now uses Peertube. This was used in conjunction with the custom chat widget to provide a Twitch-like experience
• Previously, we also ran a streaming server that used an RTMP module for Nginx to serve an HLS livestream video; this has been deprecated as Peertube has built-in video streaming

Tools used:

• The main website is a WordPress instance, which I set up with Woocommerce and Stripe integration for ticket sales
• We run a BigBlueButton instance for video calls (an open-source Zoom alternative that's tailored to online teaching)
• We also run a Matrix chat server
• SSO with Keycloak

Highlights:

• Complete educational platform infrastructure with integrated payment processing, video conferencing, and chat
• Single sign-on system allows students to move seamlessly between different services
• Self-hosted solution provides full control over data and user experience