Rename roadmap to "feature extensions"

[dschuff]

When this page was created along with the wasm MVP, all the listed features were in the future, so it served as a roadmap for what was to come. Now it includes all the feature extensions that have been added since, and its primary usefulness is actually for developers to look up which engine versions implement which features (including past and near-future features which have implementations behind flags). So a better name than "roadmap" or "future features" would be something like "feature extensions".

Also fixes #329

[dschuff]

/cc @tomayac @RReverser WDYT?

[tomayac]

I think "Feature extensions" works well.

Cool URIs don't change, so I suggest you also add a redirect that points the old link to the new location. Not sure what's possible based on the hosting platform, but in the worst case even a <meta http-equiv=refresh> intermediate page would do.

[RReverser]

Not sure what's possible based on the hosting platform

I can add one next week, let's wait with this PR until then. We have Cloudflare Workers on WebAssembly.org, with a bunch of existing redirects I added back when I did initial website revamp, so adding another one should be easy.

[dschuff]

I can add one next week, let's wait with this PR until then. We have Cloudflare Workers on WebAssembly.org, with a bunch of existing redirects I added back when I did initial website revamp, so adding another one should be easy.

Thanks; no hurry, this certainly isn't urgent.

[RReverser]

I've added a redirect.

[dschuff]

Thanks! I'm going to interpret the above discussion as "LGTM" and land this, I'll test it once it deploys.

[RReverser]

Yeah I was thinking of bikeshedding the name a bit, but couldn't come up with anything better than "feature extensions" either. "Post-MVP features" is the only alternative I can think of and it's a bit mouthful.

Thanks!

[dschuff]

So this seems to have gone live now, but I think there's something wrong with the redirection: it looks like https://webassembly.org/features is getting redirected to https://webassembly.org/roadmap/ (and then 404ing) rather than the other way around.

[RReverser]

Oh right, I set this redirect up while roadmap was the working link. If I set it the other way around, it would be 404-ing right away, before this PR was merged.

I'll swap the direction now.

[RReverser]

Swapped now.

[RReverser]

I'll look into some integration to make it possible to set up redirects from the repo, then it would be easier to deploy them alongside content in the same PR.

[dschuff]

Thanks!