-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: shortcut for new, blank Notebook #274
Comments
I assume you know this, but just stating here for others... the 'Create notebook' button on that New popup is the default button, so hitting enter would get you into your new notebook (no need to click). It doesn't answer your request directly, but I usually hit the new button and just hit the enter key... |
Just thinking about how many sites have a ".new" like And consider this like a p4 wishlist kinda thing. |
Thanks for pointing that out, Yuri. I assume that if you ever want the screen back, you will need to hunt for that option in your user settings and re-enable it? |
Note that the GitHub.new page also has a 'popup'... |
New plus enter is pretty smooth as clicking the create is hard as it jumps out of the way onload. I would like a alt + click on new to skip the loading of the templates and open a new blank notebook. |
FWIW |
Is your feature request related to a problem? Please describe.
It used to be that you could visit https://observablehq.com/new and get a new blank notebook.
Now you get this handy popup which shows you possible templates to use. Great.
However, I find myself always creating a new blank notebook so even though I have the /new url bookmarked, I have to do that click to choose the blank template.
Describe the solution you'd like
I would like a short hand url that creates a new, blank notebook without having to choose a template.
Perhaps https://observablehq.com/new/blank
Describe alternatives you've considered
I could just bookmark a blank notebook and fork that, but many clicks vs a bookmark.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: