👋 Excited to see these great issues popping up!

• Once this is done, should we deprecate the existing Post Comments block?

We can start with a soft deprecation, i.e. supporting the old block but deprioritising it (e.g. hiding it from the inserter). In other words, we don't need formal deprecation notices yet. The fact that it's a dynamic block means that, later on, we have some flexibility to determine how existing Post Comments blocks should be rendered.

• As explained previously, there are already working blocks for the Post Comment Author, Post Comment Date, Post Comment Content that are used for the Post Comment Block. I guess we could work on the existing ones right? Or would it be better to create new ones for this purpose?

If the old blocks' usesContext: [ 'commentId' ] directive is compatible with the new blocks' intended implementation, I'd say it's worth reusing.

• It seems to me that, while working on the Block Elements, we should keep in mind that they should also work fine for the Post Comment Block right?

Yes, as I mentioned above — unless supporting both becomes an unreasonable burden!

• Once the Comments Loop block is finished, should we even deprecate the Post Comment Block and create a setting in the loop to select just an id?

IMO, it depends on what the benefits are, or what the use cases could be for this. It feels lower priority to me.

• I feel that, as already pointed in other issues, it would be better to have two different blocks for the Comment Author and the Comment Author Avatar. However, right now in the posts, the Avatar is just a setting in the Post Author block. Is there any reason to not create two different blocks?

It's probably the trade-off between the flexibility of more granular blocks (Author + Avatar) vs. the user-friendliness and polish of dedicated multi-functional blocks (Author with integrated Avatar). With the ongoing improvements in layouts and alignments, the balance may soon tip towards granular blocks. I suggest experimenting with both and seeing what feels right. :)

@SantosGuillamot One design update we might consider: the new Dimensions and Layout panels will be useful on blocks like Avatar, but potentially all of them.

With the ongoing improvements in layouts and alignments, the balance may soon tip towards granular blocks.

Probably worth getting a theme dev's input here (cc @kjellr), but I suspect that the flexibility afforded by separate blocks for author name and author avatar will be more useful in general.

Probably worth getting a theme dev's input here (cc @kjellr), but I suspect that the flexibility afforded by separate blocks for author name and author avatar will be more useful in general.

Yeah, the current iteration of the Post Author block is pretty inflexible and limiting for theme authors. There was a lot of talk about its issues (and the idea of splitting it into sub-blocks) in #24952. This is one of the reasons the block was left out of 5.8.

Author with integrated Avatar -sounds like a good default block pattern or a block with inner blocks.
The post author block is really just waiting for a decision to be made, so that work can start.

@SantosGuillamot these three blocks don't have design, so I'm going to label them with Needs Design:

• #35008
• #35009
• #35010

@SantosGuillamot One design update we might consider: the new Dimensions and Layout panels will be useful on blocks like Avatar, but potentially all of them.

I agree it makes sense for most of these blocks 🙂 . I can see that the Dimension panel was integrated in this Pull Request and there is another Pull Request to create a unified Layout panel. Do you know which is the best place to understand both panels better and how to integrate them in the blocks?

I believe the Group block has already implemented the Dimensions panel, so that might be a good place to look?

To clarify, it probably only makes sense for the Layout panel to be added to container blocks in this context, IE the comment query loop and the comment template. But obviously we can only do that once the feature has been added – my apologies, I thought it already had been.

The post comment block is in the theme category, but the inner blocks are in the design category, is that correct or should they all be in the theme category?

Personally I think the inner blocks are more aligned with the other blocks in the theme category.

But without wanting to open a can of worms, could there be an argument for a dedicated "Comments" section? There are quite a few blocks here...

As we work through these, I'd like to drop all the "Post" prefixes and just settle on "Comment Content", "Comment Author", etc.

Perhaps this is obvious but I'd like to clarify:

If a user submits a new comment, we would still require a full page reload in order to show that new comment, correct? As opposed to creating a sort of "optimistic update" and showing the just-submitted comment without a reload.

If a user submits a new comment, we would still require a full page reload in order to show that new comment, correct?

Do you mean like creating a comment in the front-end and show the results in the editor?

If a user submits a new comment, we would still require a full page reload in order to show that new comment, correct?

That's correct Michal.

Do you mean like creating a comment in the front-end and show the results in the editor?

I think he means rendering the comment in the browser after submission.

I think he means rendering the comment in the browser after submission.

yup, that's what I meant. Thanks Luis!

There has been some progress during the last weeks and I'd like to make a quick summary update. These are the issues we have worked on, and the status of each of them:

• Comment Date block: It has already been finished and merged! Thanks @carolinan for the Pull Request.
• Comment Author block: @c4rl0sbr4v0 has been working on this Pull Request which is almost finished. It's already in review and only some minor changes may be needed. You can check the video in the opening comment to check how it looks like.
• Comment Avatar Author block: @c4rl0sbr4v0 has been working on this other Pull Request which is almost finished as well. There is a discussion about the width-height aspect ratio, but the code is almost finished.
• Comment Content block: @DAreRodz has been working on this Pull Request and, again, it is almost finished. The code is already done and just a full code review is needed. Apart from that, there is an open question to decide if we should include more typography options or not to keep consistency between blocks.
• Comments Query Loop block: This is probably the most complex issue and @michalczaplinski has been working on it in this Pull Request. There was some discussion to reduce the scope of the Pull Request, as it could get really long, and the first version should be ready soon.

Feel free to add anything that I'm missing, and you can find more information in each Pull Request 🙂

A new update on the Post Comments blocks. This was the progress made during the last couple of weeks:

• Comment Query Loop block & Comment Template block: These blocks are the wrappers for the rest of the block elements. An initial version of them was merged in this Pull Request made by @michalczaplinski, and he is working on the next steps on this other Pull Request.
• Comment Content block: @DAreRodz  finished this Pull Request and it has already been merged.
• Comment Avatar Author block: @c4rl0sbr4v0 finished this Pull Request and it was merged as well.
• Comment Reply Link block: @DAreRodz worked on this other Pull Request and it was merged too.
• Comment Edit Comment Link block: Another Pull Request where @c4rl0sbr4v0  worked on and was merged.

For now, we will keep working on the aspects left in the Comment Query Loop block and start working on the blocks related to the Comments pagination. Feel free to add anything missing 🙂