-
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
Add indicator for modified post meta in pre-publish flow #62329
Comments
If we were to show the meta changes in the pre-publish flow as a panel, what would we put in it? This is what two of the other panels look like expanded: We could just include the modified meta shown in the following Posts panel from #62982: I don't believe the "Posts" heading would work in this case. Perhaps it should say "Meta"? Other aspects of the panel would also need to change, including:
Maybe it could look something like this: |
@jarekmorawski I feel like you had some good instincts in past conversations around bindings and such. Since some of the work I've provided here has not sailed through smoothly, I wonder if you would have time at some point in the 6.7 phase to revisit something like this issue with a fresh perspective? Past Figma work. |
I've opened this new issue trying to gather all the context related to the save workflows and post-meta/post-data. I think it is important to take one step back and think about it more broadly. |
What problem does this address?
Follow up to #61811
While we are now indicating to users when metadata has changed to published posts, we do not yet do so when a post is still in pre-published state.
We should determine what this UX should be and any revisions that would be needed to accommodate this in the pre-publish flow.
What is your proposed solution?
One idea: We can consider integrating information about the post meta in the pre-publish check as another collapsed panel next to suggestions related to tags and categories, as observed in this comment.
We should also consider surfacing this information whenever a draft is saved.
The text was updated successfully, but these errors were encountered: