Once we have #3 addressed, we’ll have to configure web server to make proper HTTP redirection for funny URL names and others that may create conflicts (e.g. inconsistent casing #2)

Handle cases such as:

• tutorials/What is CSS? into tutorials/What_is_CSS
• concepts/accessibility/definitions/visual impairment into concepts/accessibility/definitions/visual_impairment
• html/elements/!DOCTYPE into html/elements/DOCTYPE
• svg/properties/animVal (SVGAnimatedString) into svg/properties/animVal_SVGAnimatedString
• css/Properties/color into css/properties/color (notice "Properties" casing here)
• css/properties/flex-align into css/properties/align-items (notice casing here too)

Objectives

1. Keep original URLs in place
2. Redirect to a valid URL that removes potential confusion (ref: URL "code-points", and RFC3986 at 3.3. Path)
3. Make obvious mapping from URL into a file name in the source repository

Expected deliverables

• List, and configure for NGINX, all deleted pages to their configured redirects (redirects.txt)
• List, and configure in a format suitable for NGINX, all URLs we want to "sanitize" (sanity_redirects.txt)
• Commit NGINX configuration options into https://github.com/webplatform/docs along with directory listing configuration from Find a way to reproduce sub page listing without relying on static site generator #3

Reference

• NGINX redirect map