Separate release posts from blog posts
Release posts are different from the marketing blog post in many ways. For example:
- Release, patch release, and security release posts all do not go through the editorial team for review and publishing.
- Release posts include information from data files
- Release posts trigger the releases.rb to generate content for https://about.gitlab.com/releases/
Releases posts are also a blocker for removing the blog from the www-gitlab-com repository in their own repository Based on this and the discussion in this issue (blog-gitlab-com#19 (closed)), we need to separate release posts from marketing blog posts. UPDATE 1/10/20: Even with monorepo approach to www-gitlab-com, we still needed to separate release posts from marketing blog posts.
To do this, we need to make the following updates to www-gitlab-com:
-
creating a new blog instance for release posts within middleman !37470 (merged) -
update all blog logic throughout website !37470 (merged) -
update all URLs for release posts !37470 (merged) -
create redirects for all old release post URLs !37470 (merged) -
update release post documentation in the handbook and repository !37528 (merged) -
update the Disqus integration for those pages
Cheat Sheet for blog post authors
If you have a blog post MR in progress when this is deployed, you will have to make some adjustments to your MR. Here is a cheat sheet on how to do that. https://docs.google.com/document/d/1GdQuaYGd89tV5O8YEx7pVIIBqhrYvaY7h6gMDjVVjU0/edit?usp=sharing