The post requests the ability to access variables that are parents of a slot within the slot itself, as the community member is working on a CMS and finding slots beneficial but unable to access certain variables. The comments discuss the technical feasibility of this, with one community member noting that content in slots cannot access variables outside as they may not exist, and suggesting a "nocode component" where variables are passed as props. Another community member wonders if they can accept the risk of the variable not being present, given their use case of different post types sharing common elements. The discussion concludes that global variables, in addition to instance variables, would need to be accessible across slot boundaries to enable this functionality.
Can I accept the risk that the variable may not be present?
Use case: I have three different post types. They are all blog posts to an extent but different formats. They share the same header, byline, author box, ctas, but different body and URLs
we had a long discussion with @TrySound it seems that we agree that we will need a global variables in addition to the instance variables and those global variables will be accessible across slot boundaries