Change blog category: "GitLab news" to "company"

Rakefile

@@ -78,7 +78,7 @@ namespace :lint do
                     'open source',
                     'culture',
                     'insights',
-                    'GitLab news'].freeze
+                    'company'].freeze
       count = 0

source/handbook/marketing/blog/index.html.md

@@ -289,7 +289,7 @@ title: "This is the post title"
 author: Firstname Lastname
 author_gitlab: GitLab.com username
 author_twitter: Twitter username
-categories: GitLab news
+categories: Company
 image_title: '/images/blogimages/post-cover-image.jpg'
 description: "Short description for the blog post"
 twitter_image: '/images/tweets/post-screenshot-image.png' # optional
@@ -357,16 +357,29 @@ otherwise you'll create another category, which is something we don't want to do
 - `open source` – stories from or about our community, users, or the wider open source community
 - `culture` – posts about remote work, working together, or GitLab culture
 - `insights` – industry, data, newsjacking, developer survey, etc.
-- `GitLab news` – company or product announcements, policy changes, events, etc.
+- `company` – company or product announcements, policy changes, events, etc.
 We're working on improving category pages and tagging, but for now you can find posts under the same category by navigating to
 `https://about.gitlab.com/blog/categories/category-name/`. Dashes will be automatically added
 to multi-word categories and all of them will be lowercased in the URL. For example, the
-category "GitLab news" will be available under `https://about.gitlab.com/blog/categories/gitlab-news/`.
+category "company" will be available under `https://about.gitlab.com/blog/categories/company/`.
 Note that there's a CI test that checks for wrong or missing categories. If one of
-the above should change or a new category is added, don't forget to also change the
-[categories that are in the checker](https://gitlab.com/gitlab-com/www-gitlab-com/blob/8a8aef34a6a7c2c5413024bef2163935748d8701/Rakefile#L88-93).
+the above should change or a new category is added, don't forget to edit the
+following files:
+
+1. [`Rakefile`](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/Rakefile) (search for `CATEGORIES`) - responsible for the CI test
+1. [`source/includes/blog/category-nav.html.haml`](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/includes/blog/category-nav.html.haml) - responsible for the categories navbar
+1. [`source/handbook/marketing/blog/index.html.md`](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/handbook/marketing/blog/index.html.md) - the handbook which you're currently reading
+1. If a category changes, you need to replace it in all posts. Here's a one-liner command you can run:
+
+    ```sh
+    find ./source/posts -type f -exec sed -i 's/categories: old/categories: new/' {} \;
+    ```
+
+    where `old` is the old category and `new` is the new one.
+1. In case of a category change, a redirect should be added in <https://gitlab.com/gitlab-cookbooks/cookbook-about-gitlab-com> (internal).
+   This is the last step after all the above are merged into `master` and deployed. Ask a production engineer to help you.
 #### Cover image

source/includes/blog/category-nav.html.haml

@@ -23,6 +23,6 @@
       %li{class: ("active" if current_page.url == "/blog/categories/insights/")}
         %a{href: "/blog/categories/insights"}
           insights
-      %li{class: ("active" if current_page.url == "/blog/categories/gitlab-news/")}
-        %a{href: "/blog/categories/gitlab-news"}
-          GitLab news
+      %li{class: ("active" if current_page.url == "/blog/categories/company/")}
+        %a{href: "/blog/categories/company"}
+          company

source/posts/2011-11-07-new-design-is-coming.html.md

@@ -4,7 +4,7 @@ wordpress_id: 25
 wordpress_url: http://blog.gitlabhq.com/?p=25
 date: 2011-11-07 21:37:44 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/11/gitlab_issues1.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/11/gitlab_issues1.png" alt="" title="Issues" width="974" class="alignnone size-full wp-image-27" /></a>

source/posts/2011-11-08-install-guide-from-ryan-wersal.html.md

@@ -4,6 +4,6 @@ wordpress_id: 36
 wordpress_url: http://blog.gitlabhq.com/?p=36
 date: 2011-11-08 09:08:10 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 <a href="http://www.ryanwersal.com/blog/2011/10/18/installing-gitlab-on-ubuntu-server/" title="installing-gitlab-on-ubuntu-server">Install guide from Ryan Wersal</a>

source/posts/2011-11-16-new-feature-network-graph.html.md

@@ -4,6 +4,6 @@ wordpress_id: 39
 wordpress_url: http://blog.gitlabhq.com/?p=39
 date: 2011-11-16 07:32:49 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/11/network1.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/11/network1.png" alt="" title="network" width="602" class="size-full wp-image-40" /></a>

source/posts/2011-11-16-new-feature-project-activities.html.md

@@ -4,6 +4,6 @@ wordpress_id: 48
 wordpress_url: http://blog.gitlabhq.com/?p=48
 date: 2011-11-16 19:52:19 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/11/project_activities1.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/11/project_activities1.png" alt="" title="project_activities" width="602" class="alignnone size-full wp-image-49" /></a>

source/posts/2011-11-24-issue-prototype.html.md

@@ -4,7 +4,7 @@ wordpress_id: 96
 wordpress_url: http://blog.gitlabhq.com/?p=96
 date: 2011-11-24 23:51:01 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/11/11660251.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/11/11660251.png" alt="" title="issue with branch" width="602" class="alignnone size-full wp-image-97" /></a>

source/posts/2011-11-27-dark-colors-for-code-review.html.md

@@ -4,7 +4,7 @@ wordpress_id: 100
 wordpress_url: http://blog.gitlabhq.com/?p=100
 date: 2011-11-27 15:30:43 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 I prefer dark colors so i Implemented ability to switch for dark one.
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/11/11715191.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/11/11715191.png" alt="" title="1171519" width="602" class="aligncenter size-full wp-image-101" /></a>

source/posts/2011-11-27-issues-become-simplier.html.md

@@ -4,7 +4,7 @@ wordpress_id: 103
 wordpress_url: http://blog.gitlabhq.com/?p=103
 date: 2011-11-27 15:34:27 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 We decided to keep issue show page simplier.
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/11/issues_11.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/11/issues_11.png" alt="" title="issues_1" width="602"  class="aligncenter size-full wp-image-105" /></a>

source/posts/2011-11-28-merge-requests-v1.html.md

@@ -4,7 +4,7 @@ wordpress_id: 108
 wordpress_url: http://blog.gitlabhq.com/?p=108
 date: 2011-11-28 21:05:56 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 Merge requests list
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/11/gitlab_merge_requests_11.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/11/gitlab_merge_requests_11.png" alt="" title="gitlab_merge_requests_1" width="601" class="aligncenter size-full wp-image-109" /></a>

source/posts/2011-12-01-new-commit-show-page.html.md

@@ -4,7 +4,7 @@ wordpress_id: 114
 wordpress_url: http://blog.gitlabhq.com/?p=114
 date: 2011-12-01 09:54:07 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 We restyled commit page & added anchors to line numbers
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/12/commits1.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/12/commits1.png" alt="" title="commits" width="1059" height="883" class="aligncenter size-full wp-image-115" /></a>

source/posts/2011-12-07-new-access-privilegies.html.md

@@ -4,7 +4,7 @@ wordpress_id: 119
 wordpress_url: http://blog.gitlabhq.com/?p=119
 date: 2011-12-07 14:25:25 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/12/gitLab_access1.png"><img class="aligncenter size-full wp-image-120" title="gitLab_access" src="http://blog.gitlabhq.com/wp-content/uploads/2011/12/gitLab_access1.png" alt="" width="1162" height="782" /></a>

source/posts/2011-12-09-useful-dashboard-first-try.html.md

@@ -4,7 +4,7 @@ wordpress_id: 128
 wordpress_url: http://blog.gitlabhq.com/?p=128
 date: 2011-12-09 16:31:11 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 Activities (old dashboard page)
 <a href="http://blog.gitlabhq.com/wp-content/uploads/2011/12/dashboard11.png"><img src="http://blog.gitlabhq.com/wp-content/uploads/2011/12/dashboard11.png" alt="" title="dashboard1" width="1096" height="557" class="aligncenter size-full wp-image-129" /></a>

source/posts/2012-01-13-design-changes.html.md

@@ -4,7 +4,7 @@ wordpress_id: 191
 wordpress_url: http://blog.gitlabhq.com/?p=191
 date: 2012-01-13 21:43:55 +00:00
 comments: false
-categories: GitLab news
+categories: company
 ---
 We made changes to design & layout of gitlab. 
 Goal of changes is to reach bigger working area & minimalistic UI. 

source/posts/2012-03-09-diagnostic-tool.html.md

@@ -4,7 +4,7 @@ wordpress_id: 254
 wordpress_url: http://blog.gitlabhq.com/?p=254
 date: 2012-03-09 18:52:26 +00:00
 community: true
-categories: GitLab news
+categories: company
 ---
 We pushed to master new support util.
 If you have some troubles with gitlab installation - try diagnostic tool.

source/posts/2012-03-12-migrating-to-mysql.html.md

@@ -4,7 +4,7 @@ wordpress_id: 260
 wordpress_url: http://blog.gitlabhq.com/?p=260
 date: 2012-03-12 07:28:15 +00:00
 community: true
-categories: GitLab news
+categories: company
 ---
 Now mysql is officially supported by gitlabhq. 
 Follow next steps to migrate to mysql

source/posts/2012-03-27-weve-started-donation-campaign.html.md

@@ -4,7 +4,7 @@ wordpress_id: 304
 wordpress_url: http://blog.gitlabhq.com/?p=304
 date: 2012-03-27 12:51:34 +00:00
 community: true
-categories: GitLab news
+categories: company
 ---
 <p>We've started donation campaign to get support from our users. We are going to provide a better software for you with every new release.  GitLab is open source project and now it needs your help.</p>

source/posts/2012-06-01-network-graph-keyboard-navigation.html.md

@@ -4,7 +4,7 @@ wordpress_id: 401
 wordpress_url: http://blog.gitlabhq.com/?p=401
 date: 2012-06-01 18:04:23 +00:00
 community: true
-categories: GitLab news
+categories: company
 ---
 Now You can move around the graph by using arrow keys (left and right). 

source/posts/2012-06-06-merge-request-improved.html.md

@@ -4,7 +4,7 @@ wordpress_id: 407
 wordpress_url: http://blog.gitlabhq.com/?p=407
 date: 2012-06-06 08:28:18 +00:00
 community: true
-categories: GitLab news
+categories: company
 ---
 <p>We added some improvement to keep your repo cleaner. Now you can remove source branch with merge.
  Just check "Remove source-branch" before accept MR. And source branch will be removed after successful merge </p>