Clarification for parent and ancestor hierarchical relationships

[colorful-tones]

What?

Attempting to offer clarity on the usage of parent and ancestor hierarchical relationship in InnerBlocks nesting.

Some notes:

• Try to downplay the usage of "child", because I think it is confusing. Especially in headings. Although, I still left a few references.

Why?

Hierarchical relationshiops can be hard to explain.

How?

Change wording.

Testing Instructions

Just a docs change and compare the diff is probably best.

Testing Instructions for Keyboard

Not applicable.

[github-actions]

Warning: Type of PR label error

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Accessibility (a11y), [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: .

Read more about Type labels in Gutenberg.

[colorful-tones]

concise and sometimes verbose

I think that is an oxymoron. 🙃

[colorful-tones]

I'm also wondering if replacing some of the "context" uses with "inheritance" might help. I think the term "context" might get easily confused with Block Context. 🤔

[fabiankaegy]

Thanks for taking a stab at this documentation :) I have raised a few concerns and tried to leave some suggestions. (May be a little messy though)

In general I am not a fan of using the hierarchical relationships reference in this documentation but have left some more detailed notes inline :)

Let me know what you think!

[colorful-tones]

@fabiankaegy All your suggestions were great, and I appreciate the feedback. I had already rewritten some of the content because I'm also writing documentation for ACF Blocks InnerBlocks, and many of these concepts are bouncing around in my head for the best way to try and explain them. I read through your comments. I generally agree with all of your observations. I took another broad pass at the overall approach. I would love another round of feedback. Thanks!

[fabiankaegy]

I really like the updates you made now :)

[fabiankaegy]

Haha that was perfect timing. I saw you had pushed a new revision and just finished reading it

[ndiego]

This looks great. Thanks! 🚢

[gziolo]

Excellent job rephrasing the subtle differences between these two options. The cool part is that folks can even use both parent and ancestor for a given block if they want to.