This was originally written and posted on the Interactive Engagement tech blog for WNET.
I’ve learned a lot since I started working at IEG in August 2014, from building better WordPress themes via MVC to the ins-and-outs of git (how I got by before, I’ll never know). The greatest tool that I’ve embraced in my tenure is Sass. For those unfamiliar, Sass is a CSS preprocessor which takes giant complex stylesheets and neatly organizes them into tiers. There are so many features which will make your development process cleaner, faster, and happier. Read more
Back in October of 2014, I had a bit of a dry spell at WNET. There weren’t as many new projects coming in, and I was still green to the way our more complex web properties work. Instead of sitting around and reading the various internet news aggregates, I decided to attack a problem I knew about even before starting my job that August.
The Interactive Engagement Group (IEG) website was a flat, two-page piece of brochure ware. It was built to appease the powers-that-be, but was in no way indicative of the type of amazing work that the department was capable of doing. I wanted to take this project head on and lead the way to a beautiful, responsive, and informative website that would not only show off what we could do, but show off the expertise of our team. To do this, I needed buy-in from my boss, head of the technical team, and from the head of our department.
To Get Buy In, I Came Prepared
Though I talked about why I thought it was important with my boss and with the developer team, I knew I would need a lot more than a “good idea” to get department funding to build the site. I put my professional writing skills to work and wrote a content strategy. Read more