This is a great solution for the fields in body. It would work there as I have setup extensive Fields in my CMS to cover a range of in-depth Blog Posts and some posts may not require all of them.
Unsure how it applies to Hero Image though as I cannot link the Hero Image layout element to a CMS Collections Field because it is a background image sourced from Assets.
Is my understanding correct here?
If I could link a Collections to my Hero Image, I’d be set. My planned usage is a unique Hero Image per Blog Post. Your solution wouldn’t appear to scale well with 100 + blog posts (100 + images with conditional visibility set to a CMS Value Field?)
My ideal workaround would be to find a way to create my own Hero Image Layout using Images linked to CMS and have Button overlay the image. I’m struggling there - definitely feel like a newbie.