Ability to setup redirects

[scottgonzalez]

Either as a per-post config in the post metadata or as a per-site config in the root of the repo.

[jzaefferer]

Per-site config sounds good to me. The current format works well enough: https://github.com/jquery/infrastructure/blob/67da0243a68896f6921e058f449b95ac222a0ae5/modules/jquery/manifests/wp/qunitjs.pp#L21-L26 - if this becomes a feature here, it can be just a list of pairs containing "[from] [to]". Or JSON or XML, doesn't really matter. But one location is definitely better then per-post.

[gnarf]

👍 we definitely need something like this.

[arthurvr]

I'm 👍 on a per-site config.

If we want to remove a page from a specific site now and setup redirects, what's the best way to handle that?

[gnarf]

'Right now' we need to add am nginx redirect rule in our puppet config. I
can show you the way. Or just request @jquery/infrastructure to set them
up when you need them.
On Jun 6, 2015 09:35, "Arthur Verschaeve" notifications@github.com wrote:

I'm [image: 👍] on a per-site config.

If we want to remove a page from a specific site now and setup redirects,
what's the best way to handle that?

—
Reply to this email directly or view it on GitHub
#61 (comment)
.

[gnarf]

Can anyone own this / get it done? I'd really like to not have to add redirects for everything to our puppet/nginx configs.

[gnarf]

I'm hoping that this would populate a list of redirects / alternates in the wordpress databases/plugins somewhere. Whatever format works best.

[gnarf]

#69
jquery/jquery-wp-content#368

[gnarf]

v2.3.0 of grunt-jquery-content adds the redirect.json via #69