Store content without the need for a page

It would be great to have the ability to store content in the CMS without the need for it to have a page template in the frontend. Kind of like a module, partial, or pure data. I would find this particularly useful in multi-language sites when a structure field can become difficult to manage across translations and creating the template just to redirect incase the page is accessed becomes laborious.

I imagine this could be enabled via a new page status, like ‘Data’ for example, so you could keep the publishing workflow with ‘Draft’.

Can you elaborate how you would use this?

A current example is an ‘About’ page with a ‘Team’ section on a multilanguage website. The individual team members don’t have pages, but we need to store their name, position, photo, and short bio. As only the position and bio need translations, storing these in a structure field is a pain from a content management perspective. Adding a team members means adding them in every language, often with the same data. Deleting a team member means removing them from every structure in every language. Not ideal.

Alternatively I can store the data as pages which is better because they’re added in all languages and necessary translations can be provided via the page fields. Adding and removing a team member is also easier. However, I still need a frontend template for this page, make sure it isn’t accessible, in the sitemap, etc… If I need to do this in multiple parts of the site it can be quite annoying. It’s also quite confusing for my client to see this as a “page” in the CMS with the open link button and whatnot. Having a page status that removes those requirements would be lovely.

Here’s the forum post that provoked this feature request: https://forum.getkirby.com/t/storing-data-in-draft-pages/33303

I can relate. For repeating content linked from different pages/blocks on multi-language pages, I always use pages to keep the data in sync between translations, even when the content isn’t accessible through the frontend by itself.

Structures would be the obvious solition and I wonder if making it possible to activate that they should sync their structure in translations would solve this whole thing without introducing another new concept.