Skip to content

Comment Template: Consider using block placeholders when editing a template with no page context #37143

@gziolo

Description

@gziolo

What problem does this address?

At the moment we show a list of the latest comments for the Comments Query Loop block when there is no post selected during editing the site. However, for all other theme blocks, we show placeholders in the same view:

Screenshot 2021-12-02 at 13 19 14

I found out that the current approach aligns with how the Query Loop block works, for example when editing in the archive template:

Screenshot 2021-12-02 at 13 21 17

Aside: Please note that the numbers used in the Pagination block don't match with the list of posts rendered (there is a single post only).

My biggest concern here is that when there is a ton of comments that include threads the Comments Query Loop block might dominate the template editing view. It also creates this disjointed experience where the data used doesn't necessarily is going to be present on the frontend in the same form.

What is your proposed solution?

Let's consider using block placeholders for nested blocks used inside the Comments Query Loop.

Metadata

Metadata

Assignees

Labels

Needs Design FeedbackNeeds general design feedback.[Block] Comment TemplateAffects the Comment Template Block[Block] CommentsAffects the Comments Block - formerly known as Comments Query Loop

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions