What problem does this address?

Since the move to saving Navigation items to a custom post type (wp_navigation) there is no longer a way to access the inner blocks data of a Navigation block.

This causes problems for users who wish to manually copy the inner blocks and use in a pattern or on another site.

Moreover, users are forced to use the Navigation block directly as the only way edit a give Navigation Post.

What is your proposed solution?

In the short term we should enable the content field on the Navigation Post type edit screen. As the inner Navigation blocks cannot currently function without a parent Navigation block, this should be forced to default to a code view. This will ensure there are no errors but will still allow power users to access the block grammar HTML.

In the longer term we should investigate

• using Isolated Template revising the Navigation Editor to edit Navigation Posts.
• finding a way for "inner" Navigation blocks (e.g. core/navigation-link) to function without having to be a child of a Navigation block