WIP: Move all blog posts to the blog-posts repository.

This is a crazy idea from the Blog Sync at git-push-mexico.

For drawbacks to this approach: www-gitlab-com#1054

cc: @marcia

@connorshea will this project get cloned by the www-gitlab-com build script?

@SeanPackham in theory, yeah.

How will we enable review apps with this method?

• Can we guarantee that all the posts will build and will have the same URL as before?
• How about relative paths in blog posts linking to other pages of about.gitlab.com? Will they work?
• How can we make sure that .gitlab-ci.yml will, in fact, pull this repo? What is the process here? First we move all the posts and setup CI later?

We're discussing the possible action of separating the entire blog site apart from about.gitlab.com.

This would solve the following problems:

• The blog would build faster with Jekyll + incremental builds - faster to publish, faster to update, more predictable building times
• The website would build faster without having tons of blog posts to render
• We'd have the entire idea-to-production workflow in one repo (issue tracker, MRs, Cycle Analytics, etc)
• We'd have MR approvals, so DevRel owns the blog with LeadGen and we know when a post is coming. What currently happens is, some posts get merged without anyone knowing about them, so we loose track of certain things, such as standards and possible CTAs.

Did I forget to mention something else?