Based on Sebastian Eberleins suggestion here: https://github.com/getkirby/ideas/issues/143 - German editors - Multilangual Setup with German and English Editors start a new page in German, then translate to English. English is set as the default l

After adding a translation in a secondary language it is not possisble to reset the translated field in the panel and let it fallback to the primary language again. Leaving it empty is saved as an empty string, rather than null because it could be i

The roadmap shows plan to add an immutable ID's to pages. It would be finally nice to have a way to do internal linking by using the "link" button on the text/textarea/writter fields. It was such a relief when finally the "open in the new tab" was

It would be nice to have a mark to strip formatting on selected text in a writer field. See screenshot attached for an example.

This is mostly relevant for Kirby 2 licenses as there is just a long list of of "Kirby 2 Professional License" at the moment. Things to put in there: * Which project/domain a license belongs to * what the actual license key is * if the site is stil

To my understanding, one has to setup a plugin to override default translations in a single-language setup (which isn't the documented usage). This allows to fine-tune a bit more the Kirby Panel to one's use-case. Having the ability to do this from

This was once discussed in the old Ideas repo and addressed in a subsequently postponed draft PR: Currently, if a single-language site's default language

I wonder if this interesting new situation - blocks and layout - should not also merit consequences for the way Kirby is treating permissions. As yet, in websites where I am not using blocks and layouts, Kirby is a CMS where I as the developer very

Having an option to create a new page that is a sibling of the current page would make the operation of filling in sites way less tedious. Right now we need to constantly go back to the parent page to create a new sibling. Maybe this is something

We have a blank.yml template in our project: yml title: Blank options: read: false We use it to simply create "pages" in the content folder that serve as folders to better organize files (since having everything under content/* doesn'

Let's say I have the following field blueprint: yml myField: type: files uploads: parent: site.page("my/page") template: foo In the panel, this will list files from the page where the field exists, but upload files to my/page.

I think IDs like e449f739-7f9f-46b4-836f-9c534f7bf88c are unnecessarily large. I know they are UUIDs, but is that really needed? Also, you can't safely use them as id attributes because they shouldn't start with a number - you'd have to escape t

The possibilty to duplicate the home and the error page is not needed, I think. So maybe this should be disabled for these blueprints by default. Or am I overlooking something?!

I want to add IDs to a structure. Obviously, I don't want the panel user to care or be aware of that, so I want this to be hidden. I could use the autoid, but it would be an overhead for my overly simple