# [Handling POST Requests in Go](http://paulcrickard.github.io/blog/8-7-2015.html)
So far, my Go server has only used GET requests in the routes. But how can we handle POST requests? It is fairly simple.
# [Improving the REST API with Go](http://paulcrickard.github.io/blog/8-6-2015.html)
My first iteration of a REST API in Go only read a GeoJSON file and served it as an endpoint.
What I really need is a way to serve database tables for reading and writing - CRUD operations.
This post will walk you though serving a table for reading only. Later posts will show editing and querying.
# [Creating a REST API with GO](http://paulcrickard.github.io/blog/8-5-2015.html)
After playing with Go for a little while, I decided it was time to do something useful.
To do this, I rely on the .NET Web API. Now, I am going to work on a Go version.
# [My New Blog Platform and Workflow](http://paulcrickard.github.io/blog/8-4-2015.html)
When I learned that you could host a website using Github I was more than excited.
After reading about GitHub Pages, I immediately looked in to Jekyll. I ignored it at the time because I
was a Git newbie and just wanted to throw up a page quickly. A few weeks ago, I saw a tweet asking which was better:
Jekyll or Hugo. Hugo was written in Go, which I am currently enamored with.
I installed Hugo, got the server running and was able to build a site with a template.
I did not however, get it running on GitHub. My repo was a mess - it had become my dumping ground.
I decided to clean up my repo and make it solely for my blog and would put all of my code in an appropriate repo.
When the time came to start blogging with Hugo, I had stumbled on to Strapdown.js.
I would have ignored it, but it seemed so easy. I had to give it a shot. Another reason I gave it a
look was because I recently started using Atom as my editor. Atom allows me to live preview markdown and has snippets.
It seemed like I could come up with a decent workflow.