> GitHub Pages does something similar: If you request /path, it will serve up /path.html. [This would] does not lock me into anything at all. This is how I dec

> GitHub Pages does something similar: If you request /path, it will serve up /path.html. [This would] does not lock me into anything at all. This is how I decided to configure my nginx as well for my web page, but note that it still locks you into something: you will still end up seeing links out there that reference /path without the extension and you will need to set up all future web servers to find the right resource on that URL. (Even if that is by adding files to the file system rather than writing web server configuration.)