Link field: `query` support for pages/files

Original discussion: https://github.com/getkirby/kirby/issues/5279

yes!! This!

Example case:

I use a page structure to store artists with a picture and a bio. It’s used to feed an artist-list block. I don’t want the artists page to show up in the link field page chooser because the pages can’t be rendered on their own.

Same issue here when using pages only as containers that should not show up in the frontend. For editors to not link to one of these pages, they need to know more then necessary about the site internals.

These container pages are required to display the tree view, so maybe it’s possible to visually indicate that they can’t be selected but hold child pages that can be selected?

This would require two options: hiding complete trees and deactivting tree-nodes for selection…

Does Kirby need an option at page blueprint level to indicate if a page is public facing (has a url that can be visited via the fronted)?

As great as the link field basically is, as much it is a source of bugs and trouble without the ability to filter pages and files – desperately neededed in every project I build!

Would also be consistent, if in the link-field the options for page would be similar to pages-field (if they make sense).

For me it turned out to be a perfect viable way to hide certain items based on the icons with CSS. Not clean, but it works and is a great way for now.