Context Navigation

Changes between Initial Version and Version 1 of Ticket #45537, comment 11

initial	v1
1	1	> Is there any reason why we can't use Gutenberg on the posts page by default? Can we make a patch to do that instead?
2	2
3		@youknowriad Trying to understand the context around this I found ~~https://core.trac.wordpress.org/ticket/~~17470. The content editing UI is hidden on the empty `page_for_posts` page in an effort reduce user confusion, since themes typically don't display the post_content of that page.
	3	@youknowriad Trying to understand the context around this I found #17470. The content editing UI is hidden on the empty `page_for_posts` page in an effort reduce user confusion, since themes typically don't display the post_content of that page.
4	4
5	5	Is there a good way to disable post_content editing when loading Gutenberg for that page? If not, that seems like a reason to continue disabling Gutenberg by default, but adopt the change proposed in this ticket to allow filtering (at least for now).