You mean like /now/index.html. Yeah, that could work! Thanks!
But "/now.html" feels "cleaner" to me. I know others might disagree.
If this now thing could support just "/now.html" or even "/now" redirecting to "/now.html", that would be swell! Maybe they already do support it? Hoping to learn from the community if these alternative paths are supported.
/now is cleaner in practice, because it's shorter, matches a (nascent, proposed) "standard", and hides the implementation details.
File path /now/index.html is a fine way to expose your content at /now ... Most webservers will default to config that allows this.
You could replace it in the future with a gigantic web app that is wired into your brain implant to retrieve realtime status. If you use /now.html, you would have to fight the framework to lie about the implementation details, instead of just not specifying them in the first place.
You could also configure your webserver to serve /home/carbonatom/webstuff/dereks-idea/now/new-version-2025.html as /now, if you like. These are the kind of implementation details that a good URL will hide (even if the specific example is a terrible case, the equivalent does happen sometimes!).
What do you want out of support? Listings on the nownownow.com site seem to be done manually, so it shouldn't matter what you make the path if that's what you're going for.
But "/now.html" feels "cleaner" to me. I know others might disagree.
If this now thing could support just "/now.html" or even "/now" redirecting to "/now.html", that would be swell! Maybe they already do support it? Hoping to learn from the community if these alternative paths are supported.