-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation: Make Navigation a static block #24371
Conversation
Size Change: +360 B (0%) Total Size: 1.16 MB
ℹ️ View Unchanged
|
Here's a first pass at making Navigation a static block. I like the amount of red—it's a big simplification. Unfortunately, though, there's a problem: any existing dynamic Navigation blocks that are out there will not render properly in the frontend until the user re-saves the post that the block is in. This is because we're deleting the We either have to:
Thoughts? @talldan @draganescu @adamziel |
This was discussed during the Nav sync in #core where we decided:
|
I thought it was important for that block to be dynamic in order to adapt to changes to the permalink structure...? |
Yes, we'll need to keep Link dynamic for this reason. Do you think Navigation should remain dynamic as well? |
What do you mean by Navigation here? I personally don't know enough here to share an informed opinion. I know initially, @mtias was in favor of a fully dynamic block. |
@youknowriad Rob meant we could use a combination of static (navigation) and dynamic blocks (link) to have both:
|
I figured that if a block can be static then it should be static. Since Navigation merely renders a container Happy to keep both Navigation and Link dynamic if we think that's better. The argument about compatibility with the Classic Editor holds less water when we're talking about Navigation because it's not common that you would insert a Navigation block into a post or page. What do you think? |
It makes sense for me 👍 I just wanted to make sure we were not regressing on the dynamic behaviors. |
Not sure I see much value in keeping an empty container static when it doesn't really provide useful semantics. I always thought a potential static fallback for a navigation block should instead be a semantic link to a site's sitemap (new feature in 5.5!)or something to that effect. |
At any rate, this PR is stale! Closing it for now. |
Work in progress.
Implements part of #24364.
Makes Navigation a static block and Navigation Link a mostly static block.
Tasks remaining:
save()
.rgb*
attributes.