I’ve been operating 100% of my public presence for API Evangelist on GitHub for almost five years now. I really like the public layer of my world being static, but I also like the modularity that using GitHub repos for my projects have injected into my workflow. API Evangelist runs as almost 100 separate GitHub repositories, all using a common Jekyll template for the UI, making it look like you are always on the same API Evangelist website. Any website, application, data, or API begins as a GitHub repository in my world, and grows from there depending on how much energy I give a project during my daily work.
When I first started doing all of this, I worried a little bit about the search engine optimization of my public websites. From what I could tell in 2013, my sites ranked lower after the switch, but since I’m not in this for the numbers game, I shrugged it off. However, in 2017 the numbers look different, and some of the projects I’ve been cultivating on GitHub actually rank pretty high, even with minimal optimization on my part. This isn’t just the web front-end for my projects–I am also seeing the GitHub repositories themselves showing up pretty prominently in search engine results. https://goo.gl/MrXoA8 #DataIntegration #ML
