Split the Blog into a separate repository
One of the conclusions from the Mexico Summit Blog Sync was that blog posts should be split out of the www-gitlab-com repository, and only be pulled in during the build process (a la the documentation).
This has a few benefits:
- We can have separate processes for the blog and the rest of the site, e.g. the blog would require two approvals before being merged. One of the problems we have right now is that content team members aren't seeing blog posts before they go out, which is a problem from a marketing standpoint.
- The blog post issues and merge requests would be hosted in this project to keep both projects lean and simple.
- We would have more granular control over permissions (e.g. everyone on the content team could merge a blog post and then
www-gitlab-com
would receive a webhook and build the site with that new blog post.)
But also a few drawbacks:
- Images are not currently differentiated, so we don't know if images are used in blog posts or if they're in the handbook/promotional website. This would mean either that new blog posts would need to have images hosted in the
blog-posts
repository and we would treat older posts as legacy or we would need to move all blog post images to the new repository. - Previewing of the blog post in-context would become more difficult.
cc: @axil @cabargas @marcia @erica @ernstvn @SeanPackham @afolson @amara @evhoffmann @rebeccad @inem
Related: #1055