Overall good work but there are still some issues with the blog post visibility and some minor refactoring comments I left below.

Also, as discussed internally, the unpublished blog posts should not be visible through the API for non-admin users or for unauthenticated requests.

If you first change some blog posts published_at times into the future and perform the following GraphQL query on the API (assuming you changed the posts at participatory process with ID 1):

{
  participatoryProcess(id: 1) {
    components {
      id
      ... on Blogs {
        posts {
          edges {
            node {
              id
              updatedAt
              title {
                translations {
                  locale
                  text
                }
              }
            }
          }
        }
      }
    }
  }
}

In the list that is returned from the API, we should not see any posts that are set to be published in the future, unless the user is an admin which is supposed to see those posts even from the API.

Currently I am able to see the unpublished posts through the API as an unauthenticated or normal user.

Another thing also regarding the API, I think we should add the publishedAt field for the blog posts. For reference, see e.g.

Looking good!

Just a couple more issues regarding the blog post visibility for admins + few cleanups. After these, it's good to go.

Tested this and everything works now as expected.

Could you still have a look at the one refactoring comment from the previous round which was not addressed?

This is now good to go for me!

@carolromero Let us know once you have thought it through at product if you accept our suggestion regarding the "not yet published" indicator or if you want to do some other changes in the admin panel. Just as a reminder, this was the section we discussed after the demo:

From our perspective we see it extremely important for the admin user to clearly see if a blog post is not yet published and when it is scheduled to go live from this view. Otherwise admin users may be confused why the post didn't appear on the site.

The "created at" column is not necessary from our perspective, we just left it there not to change any current functionality.

Let us know what you want to do with these @carolromero. From technical review perspective, this is now done, so we will be waiting for your further feedback regarding this.

Great work!