Proposed Domain Sub-Division of anvil.works

When a new person starts using anvil.works [and yes I’m resolute about referencing anvil as anvil.works because I experience the platform (IDE) as Anvil.Works and the underlying infrastructure (code) as Anvil],
they intuitively go to the browser address bar and type "docs"or “app” or “forum” first because they’re used to most of the other services that they interact with having sub domains and the browser which auto-completes according to recency.

Currently forum.anvil.works redirects to anvil.works/forum and docs.anvil.works as well as build.anvil.works both lead to connection timeouts.

I do also completely understand that the underlying configs and associated scripts will need to be edited to prevent the system from accidentally swapping out the entire Forum for a users’ app…

Any ideas on this proposal are highly welcomed. I can’t seem to think of any real drawbacks that would result except for the aforementioned.

1 Like