I have read the Bubble manual, but I still don’t understand certain aspects about groups and hierarchy, and how they relate to data. I’m hoping someone can explain.
What is the point of page hierarchy?
Why, from a data manipulation perspective, is it “better” to group elements together? What is it about conditionals that makes the group relationship better than the cell relationship?
Why do some conditionals and workflows only seem to work when they are in groups? What is it that groups do to the elements inside them?
Hello, answering these questions is almost a book.
The way I learned, best practices in programming or problem-solving are not universal, and there is no one-size-fits-all solution.
Therefore, the answer to most of these questions will vary depending on the specific situation, and trial and error may be necessary to find the best approach.
What do you mean by “page hierarchy”? Element tree on the left of bubble editor? Or something else?
In Bubble groups has 2 main goals:
group and manage elements (for example, you can have a condition to hide/show group instead of making this condition on each separate element inside of the group).
group can store some data (a Thing from DB) and elements inside can reference that Things attributes (fields).
I’m not sure I understand any of the three questions here…
Can you give some specifics as to what you’re actually asking?..
What is the point of page hierarchy?
I don’t know what you mean by ‘page hierarchy’?
Why, from a data manipulation perspective, is it “better” to group elements together? What is it about conditionals that makes the group relationship better than the cell relationship?
I’m not sure it is… (nor am I sure I understand the question)… ‘grouping’ elements together has more to do with layout that data… although it might make things very slightly easier in the editor to access data if elements share a parent container that has the same content type (maybe you save one click here… although I’m not even sure you do).
I don’t understand the second part of this question about conditionals?..
Why do some conditionals and workflows only seem to work when they are in groups? What is it that groups do to the elements inside them?
I don’t understand this question either… can you give an example of what you mean?
“What is the point of page hierarchy?
What do you mean by “page hierarchy”? Element tree on the left of bubble editor? Or something else?”
This is something that I read in the manual, that elements exist in a hierarchy. A hierarchy, to me, implies that some parts of the page are less important than others, or different things happen to them, so I am trying to understand what it means here.
"What is it about conditionals that makes the group relationship better than the cell relationship?
wdym by “cell relationship”?"
I have watched people describe best practice as grouping elements so that conditionals reflect the group rather than the cell, which suggests that the group relationship is better, so I am wondering why that is.
" Why do some conditionals and workflows only seem to work when they are in groups?
Could you share some examples?"
I had a conditional on a header that didn’t work until I put the elements into a group, but I couldn’t understand why creating a group and putting the elements into it, but changing zero conditionals should make a conditional that hadn’t been working start to work.
I’m trying to understand what relevance it has, in case it will help me understand things better. It is important enough to put in the manual, so I am worried that I am missing something.
I guess you are referencing this: The element hierarchy - Bubble Docs. There is a short but pretty decent description with an image about the hierarchy. If you’d like to learn more - google for “how browser works”.
Could you share the video? Cause “cell” is usually mentioned in terms of using Repeating groups (which is a container that can have a list of things, each thing in a separate cell).
Without knowing how it was organised in your app it’s difficult to give you an answer
“Relevance to what exactly? Responsive design? Or data? Or what?”
I’m not sure. It seems that the fact the page is hierarchical is important, hence the manual entry, but I don’t know what it means to me building things - or maybe it doesn’t?
