
Department Page for Refrigeration Manufacturer
Static HTML Department Intranet Page
Frontend Developer • Systems Analyst • Technical Writer • UX Collaborator
A Senior UX Engineer who's been building for the web since the internet was full of animated GIFs.
These days it's Drupal, JS, decoupled stacks and whatever new thing everyone is talking about (*cough cough, AI)
It's my own personal Way Back Machine. A slightly nostalgic, slightly sarcastic tour through decades of web development.
Because if you didn't save screenshots of the things you built, did they really happen?
25+ years of it.
Scroll, please. I have evidence.
My first step into web development was building a department page for the refrigeration company where I worked around the year 2000. It was simple HTML, a few images and an enthusiastic attempt to make the page feel “on theme” by adding snow in the background.
Refrigeration. Get it?
The resolution of this screenshot: courtesy of the year 2000.

Static HTML Department Intranet Page
I knew HTML. How hard could running a business be?
2002 was a year of taking big leaps and starting my own web development company. I built the website, created the branding and even printed business cards to make it official. The logo has a spider web. Because... the web.
Confidence: 100%. Business plan: questionable.

Static HTML site for my personal web development business.
These client sites were built during the time of table layouts, graphical navigation and “what if this text was also an image?” design decisions. The sites were simple and very much matched the early-2000s internet vibe.
Consistency was a suggestion, and the spacing system was hope.

Static HTML site for local sign making business
This was the era when hosting companies started saying “hey, anyone can build a website now.”
Using an early Do-It-Yourself site builder and (possibly?) WordPress on the backend, I created this small online store for skincare products. I handled product photography, image touch-ups and payment integration with PayPal which, at the time, was the obvious answer for small online businesses.
Bold AND italic, making a confident statement.

A small e-commerce site for herbal skincare products.
Drupal was my first big shift away from static HTML. I started building with a CMS that could actually do some of the work for me.
These sites relied on contributed themes to move quickly, and, wow, did it ever feel amazing to change the theme color and call it "branding".
Blue, green, or yellow. Design system complete.

Drupal 7 Site for New Employee Orientation
Not exactly for the web, but in 2010 I designed the cover for a church phone directory using Photoshop. The design featured a dozen or so portraits of churchgoers arranged like jigsaw puzzle pieces, creating a playful, connected collage.
Physical phone book. Landlines. A simpler era.

Design for printed phone directory cover
I started a tech blog to document the Drupal and frontend problems I was solving and share those lessons with other developers. And when responsive design arrived, I built a training tool to help people figure out this “new” way of building websites.
Parts of the blog and training tool still exist. Which is either impressive or hilarious.
Once helpful resources. Now historical artifacts with excellent nostalgia value.

A collection of old tech posts
My 2013 WordPress creative blog was a combo of music reviews, outdoor stories, personal essays and random musings. The blog is gone, but the screenshot survives to remind us that Photoshop can turn your hair into a weird collage of waves, vines and musical notes.
Total creative chaos.

Creative Writing Blog built in WordPress
At the healthcare organization I worked for, every internal event was promoted with a custom advertisement on the company intranet. Each one was carefully designed in Photoshop, a shocking amount of effort for a graphic that ended up around 500px wide on the homepage.
A time of experimental fonts. Accessibility, what??

Promotional/Advertisement designs to attract attendees to technology seminars
My one and only venture into mobile app development. I designed the UX/UI and built the app using MobileSmith, a platform advertised as “no code” which actually meant “some code, if we're being honest.”
The app stores were involved. Therefore, it was a real app. But it was mostly a very fancy shortcut menu.
Back when every company needed an app. For reasons.

Healthcare Mobile app for Android and iOS
And suddenly, every website had to look good on a phone. What.
Between 2013–2018 I built responsive Drupal 7 websites with clean, modern themes that could still hold their own today.
As was popular to say back then, these were built with “HTML5 and CSS3”.
So. Many. Carousels.

Drupal 7 Site for securely sharing sensitive documents with external teams
From 2015–2019 I wore many hats beyond web development, including dev-ops tasks like Linux server upgrades, database migrations, and application replacements. These projects were incredibly intensive, often tedious but necessary. Because nobody notices infrastructure. Until they do.
Welcome to the glamorous life of enterprise web ops.

Upgrade multiple Red Hat Linux Servers to latest version
Sometimes you don’t get to replace the old system. Sometimes you put a shiny new frontend on it, and pretend everything is fine.
The apps that collected other apps

Custom Front-end for Sharepoint
At some point, every enterprise org has a “Java app for that” phase. After nearly a decade of development, our company had a lot of Java applications doing variations of the same thing.
Together with a team of developers, I replaced 40 of them with a single Drupal 8 site for managing time-off requests.
Java, we hardly knew ye.

Replace Java-based apps with Drupal 8 solution.
In 2019, I ended my 16 year career in healthcare IT and began working for a digital agency. I met React and static site generators like Gatsby and Next.
My hobby wine-making site became a playground to experiment with components and modern frontend tooling in a real project I could share publicly.
React + wine = interactive fermentation.

A personal, hobby wine-making site
It seemed like a great idea. Build a reusable component library, document everything beautifully, and use it on future projects.
Seven components later, I found that component libraries are less of a side hussle and more of a lifestyle.
It's still open source. You're welcome.

A small component library built with big ambitions