HTTP Redirect https://enola.dev/... "logical" IRIs to documentation

[vorburger]

For this (or this) it would be cool if e.g. https://enola.dev/datatypes would redirect to e.g. https://docs.enola.dev/models/enola.dev/datatypes - kind of thing.

Note that GitHub pages redirects drops the path, e.g. https://enola.dev/concepts/uri/ => https://enola.dev/ but not https://docs.enola.dev/concepts/uri/.

It perhaps could even take the request headers into account and redirect a GET on https://enola.dev/emoji with Content-Type for Turtle (or whatever) to https://docs.enola.dev/models/enola.dev/emoji.ttl (note the .ttl extension which would be automagically added).

The simplest may be to hack a small web server e.g. in Go and have it running on something like Cloud Run?

Maybe this could be called tools/spielberg, as in, the (re)director... 🎦

[vorburger]

Note that GitHub pages redirects drops the path, e.g. https://enola.dev/concepts/uri/ => https://enola.dev/ but not https://docs.enola.dev/concepts/uri/.

This isn't GitHub pages' doing, but an HTTP Redirector's; currently that's Google Domains's. It had "Path Forwarding" switched off. I've just enabled it.

Right now (just 1' after enabling it), https://enola.dev/concepts/uri/ still redirects to https://enola.dev/ instead of https://docs.enola.dev/concepts/uri/, like before; but perhaps Google Domains needs a moment to dig this?

[vorburger]

Right now (just 1' after enabling it), https://enola.dev/concepts/uri/ still redirects to https://enola.dev/ instead of https://docs.enola.dev/concepts/uri/, like before; but perhaps Google Domains needs a moment to dig this?

This works now, but... that won't cut it.

What we need is https://enola.dev/emoji => https://docs.enola.dev/models/enola.dev/emoji/