Add temp workaround for legacy domain

[derrickmehaffy]

Adds a function that checks for node_env and if it's legacy it sets the base key to /documentation/ else it just sets the base to the vuepress default /

Also added a replacement for the landing meta-refresh

---

@pwizla / @Mcastres The new landing meta-refresh might make testing locally a lot harder as the vuepress default link it provides in the terminal when you use yarn dev is the base link; meaning when you click it locally you are going to be redirected to the resource center.

We have a few choices here:

• We create a simple landing page (which would make @Mcastres happy since it gets rid of the legacy meta-refresh)
• We modify whatever core vuepress package that provides that link and inject some different ones (this is the most complex as I have no idea where it comes from, probably webpack)
• We keep the existing meta-refresh but that will make it impossible to deploy in one of the two "versions"

The issue here and why all the vercel links are broken right now unless you are on a specific set of branches is because of that base key. Right now we have to set the base as /documentation/ because we are using the https://strapi.io/documentation but with the new URL structure https://docs.strapi.io/ there is no suffix so the base is just simply /

---

I've set this as a draft til we figure out what we want to do or unless someone can find a hacky way to read the NODE_ENV in the landing README.md file and adjust the meta-refresh link.

fix #306

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/strapijs/documentation/RRjKW2wpnvsaGE61dnTfZy7Q19xz
✅ Preview: https://documentation-git-vercel-workaround-strapijs.vercel.app

[derrickmehaffy]

You can see the example of what will happen when you click on the 2nd vercel link ^^^

You go straight to the resource center.

[pwizla]

Thank you very much for this PR and for taking care of this subject, @derrickmehaffy

I'd suggest we book a quick call soon to discuss it, as I don't fully get:

• what would be the drawbacks of getting rid of the meta-request?
• why getting rid of it would imply creating a "landing page"?

Since I have a limited understanding of meta / SEO stuff, I think a call would be more efficient :-) Thank you!

[derrickmehaffy]

Thank you very much for this PR and for taking care of this subject, @derrickmehaffy

I'd suggest we book a quick call soon to discuss it, as I don't fully get:

• what would be the drawbacks of getting rid of the meta-request?
• why getting rid of it would imply creating a "landing page"?

Since I have a limited understanding of meta / SEO stuff, I think a call would be more efficient :-) Thank you!

Sure I'll set one up, @Mcastres you want in on this also?

[derrickmehaffy]

@pwizla / @Mcastres per our call I've opted to not redirect the root landing page to the resource center and instead we will just add a top level menu link to it while keeping the main redirection to the dev docs.

[pwizla]

LGTM