One post before I crash, or, <title>Bad HTML pun</title>

Starting a small business on a small budget meant that at the beginning, I was doing a lot on my own, and that included the website. Before the more widespread use of WordPress and other relatively seamless platforms and plugins, this was a bit more of a challenge. In ye olden days I coded the website  in HTML, and it was . . . pretty basic. 

Having the website built manually had pros and cons. Pro: we kept it simple, and it cleanly reflected exactly what we wanted. Con: it was not fancy, and none of it was automated. Every single exhibit and artist page was created manually. The “current show” and “upcoming show” sections had to be changed each and every time. It was a hugely time consuming task to keep it up to date on a regular basis. 

In 2007, we had switched to a monthly exhibitions schedule, and we wanted our website to accurately reflect our curation. With the increase of popularity in social media, we wanted our site to be engaging. It was getting to be way, way too much work, especially on top of everything else. Now can you understand why I had that breakdown? We quoted out a website redevelopment, and it was going to cost upwards of a year’s salary to have a site redesigned for us and automated with the features we needed, which, needless to say, was totally and completely out of our small budget.

Cue Sierra Bravo and its community-minded staff . Sierra Bravo (now the Nerdery) was a quickly growing web development and marketing company in Bloomington, Minnesota. Apparently we weren’t the only nonprofit in this situation, and they were getting floods of requests for discounted websites and other marketing assistance. While they didn’t have the staff capacity to do all these websites for free, they did have another great idea: get an army of volunteer developers to do it. 

Cue the first annual Overnight Website Challenge! 

Here’s how it worked. Groups registered in one of two buckets: developer teams or needy nonprofits. The developer teams were self-organized teams of implementers. Later, each team would be paired with a nonprofit. The aforementioned needy nonprofits registered online with information about their organization, constituents writing testimonials on their behalf. They told the tales of why they needed a new website and how important it would be for their respective communities. Ten nonprofits and ten teams were selected from the applicants and registrants. Then, everybody was to gather together into teams to redesign and redevelop their website in a twenty-four-hour overnight challenge event. The developer teams won prizes, and the nonprofits would receive new websites.

It sounded crazy. It sounded perfect. 

Altered Esthetics signed up to compete with other nonprofits, and Little Brothers, Friends of the Elderly, the nonprofit I was working at for my day job, also entered. Both of our organizations had loads of testimonials. Next thing you know, we were all sitting together in a giant room full of nonprofits and web developers. It was a giant happy community nerd party. 

Quotes50.jpg

We had a great group of developers, many of whom I am still in touch with today. They took the ginormous laundry list of things I was doing with the website and helped craft an automated website built with a Ruby on Rails platform that would do everything I was doing and more. True to the event, we stayed up overnight working out the design elements and background infrastructure of what was to be Altered Esthetics’ first professionally designed website. 

“Getting a new website” sounds like a simple step, but it was so huge for us in so many ways. We had a platform we could make updates to, allowing us to embed videos and text in a very streamlined way. We created artist profile pages and forms so artists could submit works online, instead of emailing them as they were doing previously. They could create a simple user profile with a representative image. As we reviewed submissions for upcoming exhibits, we could approve images that would then automatically be processed to create online galleries with show images. This online gallery was a huge asset, especially for artists that were out of state but were still interested in seeing the art. 

As the site was going from development to live, we hosted a little data-entry party at the gallery. Board members, interns, and volunteers joined in, and we put all of the back data onto the site—shows from 2004 to 2007—so that when the gallery went live the archive would be fully intact.

Do you like an artist’s work from a particular exhibit? Click into their profile and you could see what other exhibits they were in. Do you want to submit work yourself? Create a profile and submit an image to any show for the upcoming year. It was all automatic, clean, and, even better, on a platform we could train others to use easily. 

Of course, there were things to learn. Having a user-based system meant we’d have to filter out spam accounts and help with duplicate removals, password resets, and other such things. But having a more professional website up and running was a night-and- day change for our young organization and freed up my time to focus on other things, like grants and infrastructure. 

I’m excited to report that the Overnight Website Challenge still exists and is even growing. The Nerdery has expanded the event to additional cities in the Midwest. It’s awesome to see a web-development company helping make the world a better place, one needy nonprofit at a time. 

Websites are important, and nerds are the best.

schumacher_ItsNeverGoingToWork_3DMockup.jpg

This post is adapted from It’s Never Going To Work: A Tale of Art and Nonprofits in the Minneapolis Community. Book includes illustrations by Athena Currier©2019 Jamie Schumacher.

It’s Never Going To Work is a light-hearted, illustrated book that offers real-life insights on founding a community space and nonprofit. It provides tools, tips, resources, and camaraderie to community organizers and anybody attempting something new.