I have a use-case in a older project v7 and v8, where I am estimating a migration to v13 and further to v16/V17. I the projects they have some protected content - or partially - as the pages are not protected nodes and they are accessible, e.g. to set heading and summary, but not rest of page content unless logged in. If not logged into is shows an error box with some text and link to login.
This is often see in online news papers, where it requires a subscription, but sometimes some articles are free.
Currently I don’t think it is possible to use protected content as a requires selecting a login and error page and if not logged in, the user is redirected to the login page.
This feature hasn’t changes much during the years and now with Delivery API and headless options, I think it could be better (and maybe need to be refactored a bit?)
In this concreate use-case I wonder is something like partial protected content would make sense, so content node is set as protected content, but eventually not doing any redirects and based on this handle rest in code.
In this project this error box is handle via a custom setting on content node “Login not required” (so by default this is shown on pages if not logged in).
Has anyone used protected content in such use-case? Perhaps hijacked the route or override core features for e.g. specific routes or content types?