FlasGist stores its blog data as Gist on Github. The heavy lifting is done via python-requests asynchronously. It uses the Github Gist API to access this data. Right now it uses youtube and flickr embed for the media, but I will convert those to API calls also. Github repositories are listed on the software page via the github API also.
##FlasGist works like this
###I create a starred gist on github
###I save the starred gist on github; it shows up on github
###A user hits my blog; flasgist makes an API request, gets the starred gists from github, and displays them
If the user clicks a specific link, the content for that starred gist is returned from github and rendered as markdown or html
This precludes me from having to implement content management functions such as content creation, editing, updating, and deleting. In addition, I get versioning and forking of content for free - this is beneficial for both annotation of existing content and attribution of content that I did not create, but rather may have extended.