Other way around: repo.new would redirect to github.com/repositories/new.
Imagine a webapp whose landing view page is very heavy-to-load because it’s a view of your library of documents. Like, say, Google Docs. Now imagine there’s a thing you can type instead of docs.google.com (i.e. https://docs.new) that’ll let you skip past that library view, straight to a blank new document view, so you can immediately start typing. That’s the idea here.
> Other way around: repo.new would redirect to github.com/repositories/new.
Look at that!, it does redirect to github.com/new/
I guess that will be useful for some people? It feels a little bit like mystery meat though; how do I discover these super useful shortcuts?
If I am someone who would benefit from learning a quick-to-type shortcut for performing an action, say because I create these things all the time, what does this offer over a bookmark or autocomplete in the address bar?
You still need to login in your account then, which can took a significant amount of time especially with 2FA. Then the time gain is so marginal it's insignificant.
Not if your app is structured in the way where you can use the create flow in the context of an ephemeral session, and then get asked to log in when you go to save.
But yeah, in general, apps don’t do that much, and I wouldn’t see many being pushed to do so just to add such a shortcut.
Maybe the case here is where the login will be automatic (e.g. OpenID Connect based)? So, in the case where you’d be using some random workstation, but you happen to be authed to it anyway, by e.g. creating a temporary browser profile and logging into the sync on that. But in that case, the browser sync would still give you access to your bookmarks....
Okay, maybe it was never about browser address bars at all. It seems like a lot of these blurbs on the registrar page are talking about how these things are equivalent to certain API calls you can make to these sites. So maybe the point here is to create memorable API endpoints, such that you can now do something like (not saying this works, but it might):
sort -n mydoc.csv | http sheets.new
...where the API endpoint accepts your IO-stream as a POST or PUT request, and returns a URL of the generated document.
This would make more sense, because you don’t really have access to your browser’s bookmarks from a terminal; and you might want random agents that you write, which aren’t “logged in” in any particular sense (like a CI bot) to use these shortcuts as well.
You know how, when you've just recently pushed a new branch to master, and then you go to GitHub, it'll auto-suggest creation of a new pull request with the correct source and destination repos/branches automatically selected, and all you have to do is confirm to send it?
That's what I think pr.new should do. I'd definitely use that one a lot.
I use docs.new and sheets.new several times a day. It saved me a couple of clicks per action, but subjectively it made so much smoother to stay within Google's ecosystem.
Imagine a webapp whose landing view page is very heavy-to-load because it’s a view of your library of documents. Like, say, Google Docs. Now imagine there’s a thing you can type instead of docs.google.com (i.e. https://docs.new) that’ll let you skip past that library view, straight to a blank new document view, so you can immediately start typing. That’s the idea here.