My Panel Wishlist

On my wishlist: possibility to change template via the panel …


To conceptualize this further: What would you like to happen with the data? I assume it would stay the same for fields with the same name. What about fields that do not exist anymore in the new template/blueprint? Threw the data away or keep it in the context file for the case that you want to switch back? What about fields with the same name, but different form types (e.g. textarea in the old, select in the new)?

1 Like

I’d rather keep the data of fields that do not exist in the new template, in case I wanted to switch back. As regards fields with the same name, I don’t know what would work best without breaking anything. That would depend on the content, so maybe keeping the original content but validate upon saving?

1 Like

Sometimes you have very complex page structures requiring many different content fields in the panel. In those cases, it’d be great to be able to group the fields, e. g. by using tabs.

(I know there are section headers and dividers available as “field types”, but this is not the kind of grouping I’m thinking of.)

It could be done with some javascript by dividing the form based on headers or any other field. As tabs, or as an accordion with some “panels” collapsed by default.
But yeah, there is no container div for such “groups”, so the js may be a bit tricky and fragile.

1 Like

I created a replacement for the headline field that groups all content until the next headline field in an accordion. There’s no special instructions or syntax. Simply create a headline for each content group / section you want and it should work. Let me know if you find any issues.


The new hooks in Version 2.1 are great. Thanks, Bastian!

+1 for the “dashboard widgets” mentioned in the first post by BenSeitz. :+1:

I always add quick screencasts / tutorials to any admin panel explaining the workflow for all content types for my clients (which is easy to do in Wordpress in Joomla for instance).

With Kirby right now, I have to edit the panel/app/views/dashboard/index.php directly, which feels just a little too hacky.

Panel Widgets are already possible, I’ll try to find the link …

Hey, thanks :smile:

I’ll try it out - have you used this / is this ready for prime time? This thread seems to suggest otherwise Plugins: Combine fields, widgets, methods

This plugin by @DieserJonas actually uses panel widgets:, also Kirby 2.1 has seen some changes:

Optional widgets. Widgets can now return false to not appear in the dashboard. This is great to ask for user roles and show/hide widgets accordingly.

OK thanks I’ll make sure to try this out. :+1:

cmd+enter works. Boom!

my wish: image cropping added to the image preview. cropped images is generated like a thumb and served instead of original. so original can be restored. would be a major help for some of my less experienced end-users.

1 Like

My wishlist:

  • Give the header a fixed position and put the save button on it, so that you have it in your viewport no matter how long your page form gets
  • A video preview would be great

I don’t want crop in the image preview

I don’t want the image preview to turn into an image editor. I think the thumb automatic resize and crop is fine. Else it’s so easy to to add to much UI panel stuff like…

  • Flip
  • Rotate
  • Color adjustments
  • Brightness
  • Frames

…and so on. I don’t want Kirby to turn into Photoshop. Even if starting with just a few editing functions, I think it’s easy to spend too much time on that instead of awesome core functions. We already have plenty of tools for image manipulation.

What I think is a bad example

I just saw that WordPress developed a favicon editor:

My first thought was… why?? Of all the things they could do with a 100 developers they deside to develop a favicon editor? After reading that I went back to Kirby.


I’m all for keeping Kirby core lean, but I wouldn’t dismiss any feature as “useless”. Anything is perfectly fine as contributed modules, they won’t bloat Kirby.
A big difference between Wordpress and Kirby is that the former tries to empower non-technical people to create their own website, while the latter I think is more intended for “web builders” to create websites for end users/clients (or their own website). For the people Wordpress targets, a favicon editor is fine and makes sense (the similar contrib plugin “All In One Favicon” has 200,000+ active installs, even though it hasn’t been updated in 2 years…)

I think our goal as website builders is primarily to make things easier for users/editors, not for ourselves. If there is really a need for color adjustments or Word import that makes sense for their workflow, then let’s do it (in contrib).

Back to the topic, I would actually love to see more cropping features for Kirby:

  • in core with an option to position the crop ; at least top, right, bottom, left. I believe the “top” option would be the most useful, to avoid cutting heads in pictures of people.

  • a crop module with real-size preview. Much easier for editors than cropping in a graphic app, with much more reliable results (users never follow guidelines, right?).
    Example from a Drupal site I built:

  • a focal point module, very useful in this age of responsive images with multiple sources at different height/width ratios. You just move the focal point to the most important part of the picture, and you’re guaranteed it won’t be cut when the thumbs are created. I’ve worked on many websites at Le Figaro with such a solution. For a newspaper/magazine site, cutting heads in photos is a big no-no :wink:


Focal point is (or rater, should become) a biggie if #perfmatters, but of cause we can always try to learn our clients and editors Photoshop, to take care of both mobile and desktop crops and what THAT even is, instead (haven’t been working out too well, the last 5 times I’ve tried though) :stuck_out_tongue_closed_eyes: So I’m definetely with you on that one :+1:

You don’t need to learn them Photoshop. I made a quick search for image cropping online and maybe this is good for that need (untested)

It even use some magic formula to find the best composition. There are many others working different. Some enhance colors, some give rounded corners as well.

Lots of comments here!

My wishlist:

  1. Better searching - so I can type “huxley” into the search bar instead of “writers/aldous-huxley”

  2. Native WYSIWYG text editing (I don’t want to tell clients that they need to learn markdown, the whole point of using Kirby is that I can quickly build something tailored to their needs)

  3. A way to create alternate views for different types of pages. For example, for pages that serve more as sections than actual pages (like this), it would be ideal to remove the “page settings” tools, and display subpages in a paginated form (like the ‘edit pages’ area).

  4. Smarter blueprints - the possibility to use a PHP file instead of YAML to define fields. This could be similar to something like form helpers in codeigniter:

// site/blueprints/writer.php

$blueprint_settings = array(
  'title' => 'Writer'
  'pages' = 'false'
  // (or)
  'pages' = array (
    'template' => 'fiction, nonfiction, poetry'

echo kirby_field('title', 'text', 'Author Name');
echo kirby_field('cover_image', 'select', 'Cover Image', array('options' => 'images', 'width' => '1/2'));

if ($user->role() == 'admin') {
  echo kirby_field('bio', 'textarea', 'Bio', array('help' => 'You are an admin and can edit the bio'))

foreach ...

// etc..

The above was only thought out on the spot, and may be difficult to implement.

In the end, if the panel were as flexible to build out as the front end…