How Best To Stage config-like content that is not config entities

[torenware]

While posting #48, it appears that the underlying page is regular page, i.e., a content entity instance. The fix is trivial, but cannot be done with a config file.

It's easy enough to fix whatever the canonical database (in future, production) and just reflect this down. If that's acceptable procedure, it's what I would do, rather than an updater, which is overkill. But YMMV.

How do we want to handle cases like this?

[JQTNguyen]

I don't know that I follow along with the question posed here entirely, but in talking to Sean about content entry on the site in general, he conveyed that there was a desire to shift as many things away from being within Config, and doing things like leveraging Paragraphs to move as much things into Content rather than have it live in Config.

For example, in the case of #48, changing the URL Alias for the Node that had the Article/News Listing View inserted into it via Paragraphs requires no Config Export/Code Pushes vs. if we had been using a a Views Page and need to change the URL, then a Config Export/Code Push would be required in order to make sure the change didn't get blown away in the future.

I'm not sure if this explanation helps to address the question here. If not, if you would kindly rephrase it, my Daddy Brain that has been fried by my Newborn might be able to better comprehend. ;D