Hey, thanks 
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: https://gumroad.com/l/piwiksuite, 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. 
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
5 Likes
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.
4 Likes
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
4 Likes
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) 
So Iām definetely with you on that one
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:
-
Better searching - so I can type āhuxleyā into the search bar instead of āwriters/aldous-huxleyā
-
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)
-
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).
-
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
<?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ā¦
-
I agree with you, that a better search would be great!
-
Thereās a plugin for that: https://github.com/storypioneers/kirby-wysiwyg
-
Thereās a plugin for that, too: https://github.com/flokosiol/kirby-subpagelist
-
I donāt agree with this. I like the YAML-Style because you can define your fields super fast without any
()$=={}hassle.
1 Like
re: 2. yes, but itās still buggy and a native version would have more support and development.
re: 3. I hadnāt seen your plugin, I like it! But, what Iām talking about is a built-in way to develop custom views (or templates) for the panel on the fly, without the need to build a plugin.
re: 4. YAML would still fly, but an additional PHP option would be great for when more complicated logic or access to variables was needed.
I generate one blueprint on the fly on my site. Those pages uses data from an external API and I want the page and the blueprint to be dynamic to that.
I simply replace the blueprint file with new data. I would like it to be even more static and renamed from .php to .yaml.
@Christopher the widgets actually worked well, I thought I shared code further up the thread you shared. However, I had struggled to get the custom fields to get recognized from both /site/fields as well as /site/plugins/pluginName/fields because I wasnāt very familiar with the methods @bastianallgeier used to combine them into the other existing fields and overwrite them.
yup, I got everything to work as well, though my requirements were very basic (essentially putting static HTML into a box that appears on the panel) so I canāt speak to custom fields etc.
re 1.: This would be really nice. The search is currently very basic.
re 2.: I donĀ“t want native WYSIWYG. I think itĀ“s bloat (only my opinion). But I use the visual markdown editor by Jonas to make it easier for my clients.
To explain this: I donĀ“t think, that WYSIWYG really exists, without editing in the real page. There are many Problems with this therm, because itĀ“s nearly never the thing you will get on your page (or it will be a really complicated editor).
With kirby every text is stored as markdown, so not everything is possible. Perhaps IĀ“m comparing this to editors of other CMS too much, where you can change nearly everything, including the font. I thinks that this it not a thing, a web designer (and also the client) wants.
Another Problem is, that these editors can be really ugly when copy pasting text from Word or other programs. At a website there is a clear design and the formatting options of markdown are enough in most cases.
But what I do like are editors, which highlight and format the markdown text, that you see what the markup archives. (like visual markdown). Perhaps even as the plugin mentioned by @flokosiol. But I donĀ“t like calling them WYSIWYG.
I think, that kirby and the panel should be a solid basis for everyoneĀ“s needs, but it should only be a basis, which everyone can configure for the special needs and add things with plugins.
I tried that editor but for me it was very buggy. I like the idea but not the result. At least until something really works outstanding, just keep it as a plugin and continue with current Markdown in the core.
Some editors use lots of javascript as well and make the admin really slow. That is not what I want. WordPress has a slow admin. Donāt take Kirby there too.
Much of the bugs felt random.
- Sometimes it was loaded to the textarea, sometimes not.
- Sometimes it was loaded to the first textarea but not on the second.
- Sometimes it did not resize the textarea and sometimes it did.
With the built in markdown Iāve never had any problems with anything.
I once asked to have a live preview when writing the markdown but I donāt know if anyone liked that idea. Like this forum.