Sometimes I opt to use pages instead of fields for storing data. There a many reasons for this, the main one being keeping track of data in structure or block fields can be a pain in multi-language contexts. Previously these pages have been “unlisted” and I’ve made sure they’re not accessible via the frontend, don’t show on the sitemap, etc… but I was wondering: is there any problem with just leaving these pages as Draft and not allowing the status to be changed?
One downside would be that you cannot take advantage of the publishing workflow the different page statuses provide. If you leave pages as drafts, you cannot (temporarily) hide them without deleting them.
I think it would be fine to have a toggle on the page for show/hide given the context I’m often using this in (team members, locations, etc…). An additional page status of “Data” would be nice, not everything stored in the CMS should need a page. I know you can manage this manually, but the more multi-language sites I do the more laborious the task becomes.
Yes, but as you write yourself, the toggle would have to be set for every translation, plus Kirby needs to read the content file for filtering instead of just the folder name in the file system.
Or something that is not a page but a sort of module or partial, 100% agreed.
1 Like
Good point! Might be better to just use Draft/Unlisted for now and deal with the template side as usual. Do you know if there’s Nolt entry for that feature request? I can’t find one and wouldn’t even know how to best word it!
Do you know if there’s Nolt entry for that feature request? There used to be one that has been merged into another one that doesn’t really seem related to me (or only indirectly).
I had a crack at it: https://kirby.nolt.io/693