-
Notifications
You must be signed in to change notification settings - Fork 45
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] #103529 - Introduce hotkey for "Save and Close" #173
Changes from 3 commits
a78fb41
2e9072d
bdbb8f1
62807e5
5474b94
ac5388b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -143,3 +143,9 @@ Add new content to a page | |
:class: with-shadow | ||
|
||
The new content element appears in the Page module | ||
|
||
.. tip:: | ||
|
||
If you are more comfortable using shortcuts, there are different kinds of | ||
:ref:`keyboard commands <t3editors:keyboard_commands>` you can use in | ||
the Backend Editor. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (Same as above) |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,3 +26,9 @@ display different input fields. | |
|
||
This action does not delete content. It is saved in the background and will be | ||
restored if you select the applicable content element type again. | ||
|
||
.. tip:: | ||
|
||
If you are more comfortable using shortcuts, there are different kinds of | ||
:ref:`keyboard commands <t3editors:keyboard_commands>` you can use in | ||
the Backend Editor. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Seeing this happens multiple times, There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I could do that, yeah. Is there any convention for where to place that include file? Like in "Documentation/ContentElements/Includes" or just place it in the existing ContentElements Folder next to the Index.rst? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In this repo we don't have includes yet. In the Core API docs we often create subdirectories only when more than one file is included. In your case here I would put a file like "TipHotkeys.rst" or so just into the same directory as Index.rst, yes. We can move it later when more includes happen. Thanks! :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe also use "backend forms" here, too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the hint. I will change it in this parts as well