1.1 Introduction

Content management systems have always relied upon relational database systems as their data store. And rightfully so. Databases excel at storing and retrieving data. But what about other types of data stores? For example, what if the backbone of your content management system was a Git repository? So that when someone pushed to the repository, your CMS automatically updated itself with the latest content? Hi, my name is Jeremy McPeak, and in this course we will build an application that uses a repository hosted at GitHub as a data store. But first, why build an application like this? Well first, it simplifies our application. We no longer have to manage users or permissions, because all of that is controlled by whoever controls the repository. So we can completely omit the entire membership system. But it also simplifies our UI. The content is managed outside of the application. So we no longer have to have an admin panel and a bunch of forms for creating, updating, and deleting content. But there are other advantages that come from Git itself. Most notably is that we now have a built in file history. And we can revert changes at any time. Now to build this application, I am using C# and ASP.NET 5. Now even though ASP.NET 5 is open source and cross platform, don't let my tech choice discourage you. The ideas and concepts I present in this course can be applied to any language and technology. So when you're ready, queue up the next video and we will get started.