Pages only for data

[wdebusschere]

We are building a website with a lot of data and need some guidance to be sure we are doing the correct setup.

Example:
Page Events with children
Page EventLocations with children
Page EventCategories with children.

Only the page Events will be used on the frontend (=website).
It is a good practice to prefix the pages that do not have a public page with for example data- (data-events)? Is there some more information on this?

We have everything functional, loading the data-event-locations through the controller, page blueprint: status locked,… Thank you.

[texnixe]

@wdebusschere

It is a good practice to prefix the pages that do not have a public page with for example data- (data-events)?

Never done that, it’s totally up to you how you name such pages. Might help with creating routes, though.

What I find more important is to prevent access to such pages, either via a redirect in a template or via routes.