Unify feature URL formats

There are 4 different URL formats for features currently:

• http://pages.gitlab.io/,
• https://about.gitlab.com/gitlab-ci/,
• https://about.gitlab.com/features/review-apps/
• https://about.gitlab.com/solutions/cycle-analytics/.

These should be unified somehow.

From https://gitlab.slack.com/archives/product/p1487090836002060.

/cc @regisF

assigned to @regisF

changed milestone to %Make www-gitlab-com better - iteration 1

@amara

What do you think if we dropped /solutions and just use /features/?

Yes, I agree that we should do that. I just haven't had time focus on changing those. I also suggest that GitLab Pages: https://pages.gitlab.io/ go under /features as well.

@mitchellwright if we were to change the URLs that mention features, is there an impact on existing funnels?

@amara do you agree to use /features for all features, even gitlab-ci?

I just need to be notified when we make the change so I can make an annotation in Google Analytics so that people are made aware of what the change was.

@regisF yes, I agree for gitlab-ci as well since it is a feature.

Right now, it has more of a products page URL structure and since you cannot purchase it as a standalone product we don't want to give the wrong impression.

@amara but even that - we are not able anymore to buy individual "products", thus we don't need special treatments for those pages. I think they can all follow the /features/X structure. For instance, Geo is a feature now, part of EEP.

Yes, @regisF I agree they should all follow /features/X

I've made a list of the features page we have:

• https://about.gitlab.com/features/file-locking/
• https://about.gitlab.com/features/gitlab-geo/
• https://about.gitlab.com/features/premium-support/
• https://about.gitlab.com/features/time-tracking/
• https://about.gitlab.com/features/review-apps/
• https://about.gitlab.com/solutions/cycle-analytics/
• https://about.gitlab.com/solutions/issueboard/

Not really features per se:

• https://about.gitlab.com/high-availability/

@amara am I missing something?

Yes, you're missing:

CI: https://about.gitlab.com/gitlab-ci/

Pages: http://pages.gitlab.io/

@amara

good call.

For CI, it would make sense to have about.gitlab.com/features/gitlab-ci.

For GitLab Pages, it makes sense to keep the current domain name. The idea would be to make it more discoverable then (at the moment, how we reach it?).

If we do rename all those links, we need to make sure to redirect properly then. The easiest solution is to simply keep the page and indicate in the body this page has moved to X.

For GitLab Pages, it makes sense to keep the current domain name. The idea would be to make it more discoverable then (at the moment, how we reach it?).

If the goal is to achieve unity then we should change the domain for this page as well. Currently, you can reach GitLab Pages from /features and /products this is the way to reach almost all feature landing pages currently. Let's tackle discovery in another issue since that is a larger challenge.

If we do rename all those links, we need to make sure to redirect properly then.

Yes, we should make sure we redirect properly. We did a redirect for the pricing page and that seemed to work well, in that we did not have to maintain the current page and then drive traffic to another page. But I'm not familiar with the best strategy for redirects. @mitchellwright do you have any advice on this?

mentioned in merge request !5132 (closed)

We need to identify all the pages that we want to change the URL on. Then we need to identify the new URL that the page will live at. Then we need to create a 301 redirect from the old URL to the new URL. Happy to help with this however you all need.

@mitchellwright where do we create those redirects?

@regisF you'll have to have a developer help you with that.

closed

This is now fixed.