So, we have developed over the past five blog posts, a basic overview of how the first stage of the project is supposed to work. We have lots of content and want to focus in on a few pieces of content. From this content we allow the user to select content of their preference and then by using different relationships we offer them related content without the need for them to search further. Then rinse and repeat until the user is over.
Now we need to start selecting the tools and writing the code to achieve our goals. We need to create a program that is easily accessible to other users, is able to traverse the Steem blockchain with relative ease, and can eventually handle additional tasks that we may desire in the future and scale accordingly.
From this description, it seems fairly obvious to start out with a web application. This reduces the amount of effort on the user end in that they don't have to download any dependencies or executables but rather simply enter some URL into their favorite browser. It also allows for flexibility in terms of availability and avoids any potential versioning issues that come with users having the code on their side.
But for those who do want the code, I'm going to show pretty much everything I write on this blog and will open up a Github page so that anyone can share and modify the codebase. Everyone likes free and open-source software so I will give the people what they want.
In terms of languages and frameworks used, I'm going to stick with my favorite framework Rails and use 
So there's the framework and language I'm using. Kind of a short blog today. But next time we'll start jumping into some code and exploring that. Don't worry if code doesn't make that much sense to you. I'm going to go nice and slow and talk about things in depth. There are several reasons to take such an approach:
So, that's the plan. Next, we will set up a Git repository and begin exploring the Radiator API and start seeing different pieces of information we can uncover through different commands.
