-
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
Should the Post Content block be editable? #25394
Comments
THe block itself should be editable (in FSE templates for instance) but maybe it can require a two steps edition (select, click edit...) in the context of the "Query" block. This needs some design thoughts. |
Let's start by locking editing. I'd like to get FSE into a state where display is working well before opening up edit of content too much. |
For now, I am going to remove 'needs design' as if it's going to not have the 2 steps I think that makes sense to remove. It can be added back in. |
No. In my opinion the Post content should not be directly editable.
For an example of how things can go wrong see bobbingwide/fizzie#43 (comment) |
Noting that the same "click to edit" flow might be useful to consider here #29337 |
Closing in favor of #32317 which explores the flow for 'locking' the Post blocks. |
Currently the
Post Content
block when inserted is editable and a user can edit the content and save the changes to the respective post. This feels a bit weird and might confuse a user about what flows should follow.While it can be convenient for some to use this, it might be better to have the post content
locked
and have a single clear flow on where to edit a post's content.Related to the ongoing work on FSE the Milestone:5 about Query block. #24762.
The text was updated successfully, but these errors were encountered: