It’s important to note right off the back what these projects are and, much more importantly, what they’re not. The project’s that end up listed here are generally incubator or “spike” projects. I’m notoriously bad at trying to learn a new technology in a vacuum – something generally needs context for me to really get immersed and put the time in necessary to figure something out. Therefore, I’m making absolutely no guarantees that the implementations represented here indicate best practices or perfect architecture. That being said, if I post a sample it’s generally because I learned something that I thought was less than obvious. Keep an eye on my blog posts for more detailed explanations . . .

  ESV Reading Plan

Synopsis

I had been looking for a good excuse to play with the REST API exposed by Crossway for their ESV Bible text and yearly reading plans. Specifically, I wanted to to try to do a completely client side interface for exposing that content on a web page in order to continue with my recent obsession with learning jQuery. Due to the (what should have been obvious) restrictions on cross-domain AJAX calls, this necessitated creating a local proxy for bridging the calls to the ESV servers which was a great excuse for learning more about WCF and it’s ability to expose a nice, clean REST interface. Since it was around the beginning of the year when I started looking at this, specifically exposing the yearly Reading Plans from the API seemed like a good test case – hence a new pet project was born!

Future Plans

I’d really like to add an interactive feature for tracking progress on a plan, but I haven’t had much time to devote to it. Potentially, I’d like to come back around to that as an excuse to mess with Azure using a storage account as the repository for storing the data.