Invisible container pages#23

It would be great to have an option like hide: true for pages to use them as invisible containers. You can not use read: false for those because of the child pages.

Currently quite a lot of hacking has to be done to achieve this. You have to use CSS to hide it from the topbar breadcrumb, from pages sections, from section headlines, …

Alternatively the isReadable() method could be optimized. Currently it doesn’t have any effect on the breadcrumb in the topbar and pages section headlines. And while there’s an Add-button you get an error when trying to add a page.

In my opinion a page with read: false should not be linked in pages section headlines and not appear in the breadcrumb. It should also be possible to add children to the page.

To expand would be very useful as sort of “kirby db” container/bucket for data. Often times when i have some kind of collection like “events” or “authors” these events themselves might not be routable pages and are just shown as pieces of data somewhere. Or if you want to make global media pool. And also for plugins.

The main problem being if get to such page it will render default template not erorr template so basically to handle this i have to use default and handle it on every such hidden page.

Another handy thing would be if these “buckets” were not taking space in the content namespace at all. Something like they would start with __events and have no draft/published state. The reason is purely namespace clashes when something is named the same way. For example plugins that wrap APIs like (shopify) might use this instead of virtual pages.

@iskrisis FYI Ahmed recently worked on this feature: https://github.com/getkirby/kirby/pull/3621