Component name: Portal vs Console

[ecv]

Going on six months in, I still think of cloud.datum.net, the thing we call the portal, as the console.

My fingers want to type console.datum.net, or console.cloud.datum.net. This is cognate with

• console.cloud.google.com
• console.aws.amazon.com

Now, pattern alone is not a great reason to emulate. And I don't have a problem with the basename cloud alone.

I am merely like an octopus, my fingers have something of their own intelligence, and they continue to write console.datum.net every other time I want to go to cloud.

Opening this issue to discuss. RFC.

Pro-'Console'

Google and Amazon call it that. Muscle memory is real. That's it really.

Against 'Portal'

Note

I know we're not calling it the portal anywhere except the repository name, what follows is for historical colour commentary while I wait for a build to complete.

Back in the middle '90s, when the Internet was first understood to be both cool and profitable, everyone wanted to be your browser's Home Page. Yahoo, Netscape Navigator, Altavista – These sites were called portals, and they were all sites that tempted a new Internet user to set as their browser home page, thus proving infinitely sticky.

A portal is a specific thing to me: a one-page web site, meant to load with each new window, with a search bar, the weather, a smattering of news story current events, a stock ticker, and a Directory of Topics one might Browse the Internet for. It was your 'onramp' to the 'information superhighway'.

It's nearly thirty years out of date and not a thing that I expect to encounter in 2026.

Against 'Cloud'

'Cloud' means something else to me.

[scotwells]

I'm with you on thinking of it as a console and not a portal, datum-cloud/console has a nice ring to it.