So I’m testing out Kirby. And the first thing I noticed about the page editor is that the save button is all the way at the bottom. So if I want to edit a post that’s quite long I have to scroll all the way down, press save. Scroll all the way up if I want to edit something at the top. Which makes sense since you’d scan an article from top to bottom.
Which essentially results in this annoying up-down-up-down-up-down dynamic. It would make a lot more sense to make if the save page button was in the left in the sidebar, that way no matter if you were up or down, you can just save the page.
Or even better, a keyboard shortcut, and auto-saving would be great!
I think there is a keyboard shortcut. ALT+Enter or something like that???! Move your mouse over the button and keep it there for a moment without clicking and the combination should be displayed …
Ah yes, it says “meta+enter”. I have tried all the various combinations of Alt, Ctrl and Windows+Enter but none of them do the trick. I Was thinking more of a generic shortcut like CTRL+S.
I know this is a shortcut in most browsers, but it is not often used, and in this case it wouldn’t make much difference, saving a dynamic editing page doesn’t seem all that useful.
Ah yes, I don’t know what you guys mean with panels yet. But that does sound like a good idea. If it stays in the viewport. Thanks for that info. I do hope that happens at some point
Yes, true, it doesn’t always seem to work, to me in most cases it seems to be connected to the use of structure fields.
edit: Maybe it’s just because you need to have focus on a form field to be able to use the shortcut. So when you add a new structure item, you don’t have focus and therefore the shortcut does not work …
Currently testing this on a new project; I can’t see any downsides and just wonder why I didn’t think of this earlier , probably I tend to use the shortcut rather than clicking a button. But on mobile it would be great as well.
I think a better solution than this „css-hack“ would be to place the save button by default („by code“) inside the topbar. So in my opinion a pull request is not the right way to go … @bastianallgeier?
The “save” button is bugging me for a while now combined with a fixed sidebar. I’m actually working on it right now and my solution is a bit different. Up there in the topbar is a bit problematic because of the language switcher for multi-lang sites. In general I’d invest in the custom panel css for now, because this will definitely be handled in the next version