Remove consultancy

Remove the consultancy page and references to it.

cc @klawrence

enabled an automatic merge when the pipeline for 9fbd1ed9 succeeds

merged

mentioned in commit 97d3805b

mentioned in issue #428 (closed)

@mitchellwright I've been cleaning some issues and stumbled upon mine in https://gitlab.com/gitlab-com/www-gitlab-com/issues/428.

I did a google search "gitlab consultancy" and the link that appeared was eventually a 404. Maybe set a redirect to the products page?

PS. Out of curiosity, why the page was removed? :) The reason Sid mentioned in https://gitlab.com/gitlab-com/www-gitlab-com/issues/428#note_2451258 still hold I guess?

@axil I'm not sure how to make a redirect with the way we have our website set up. Can you link me to some documentation or something?

Out of curiosity, why the page was removed?

We've got a new page going up ASAP that fills this niche. Check out the MR:

https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/7621

@mitchellwright there are two ways:

1. Easy: Use the metarefresh tag like https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/downloads/index.html.haml
2. Hard: Push an MR to the repo that holds the NGINX config file for the site

For now, I think the first will do :)

Since we now have about.gitlab.com/services to replace the consultancy page, I think we should do a 301 redirect in order to get the most SEO value out of this. @axil can you point me in the right direction of the repo with the NGINX config file for the site?

@mitchellwright yep, it's this repo which is private, you might need to ask access.

I went ahead an created an MR :) https://gitlab.com/gitlab-cookbooks/cookbook-about-gitlab-com/merge_requests/27

Thanks @axil!