A system of having immutable ID's for pages. Right now UUID's are basically slugs, which can be changed by editors. The consequence is that the stored references to these pages break. There's already a plugin that tries to solve this: https://githu

Currently it's only possible to use Conditional Fields by adding one or multiple conditions to fields. "Show this field when this other field has the value X". It's not possible

Flat-file is fast and flexible, but in the few cases when there's thousands and thousands of records to search through, we do need a database: MySQL (available in most shared hosts) - or even SQLite would do. That'll make Kirby suitable for ANY proj

It would be helpful, if the panel allowed to move pages to another parent. This would need: - a "move" option in the settings dropdown - a file browser similar to the pages field with template verification: - either only showing pages in the br

Actually it's a pain for content editors that there's no built in revisioning or backup system. A simple versioning for files to move backwards 2 or 3 steps would be awesome! A simple content lifecycle as found in plugins (publish later) would be

Let me restrict a user's access in the Panel (either per user or per role) to one or multiple pages (with subpages).

It would be awesome to be able to simply generate static websites from the Panel. Something a bit like d4l’s plugin https://github.com/d4l-data4life/kirby3-static-site-generator but built-in.

It would be great to have a way to preview all content changes immediately side by side to the Panel.

Depending on the current user role, it should be possible to disable or hide sections, columns and tabs.

The possibility for internal links (= link to another page) would be nice for the writer field.

I currently have a usecase where I work a lot with structure fields. But I find the current solution with modals rather difficult to use if you have to enter many records one after the other. With a possibility to edit the table view of the structur

It would be nice if custom buttons for textareas could be defined by plugins, e. g. following the scheme defined by the Editor field. See https://github.com/getkirby/ideas/issues/210.

Blocks are very similar to structure field and limits are useful. For example you want to use them for "slot". Or if i have two colum layout i want people to be able to add only single block to each colum (image and text). Not sure if min/max on la