Newsletter about frontity.org

[SantosGuillamot]

Yes, I agree that the placeholders and the Privacy Policy shouldn't change. Regarding the layout, I'd prefer using classes, it looks clearer to me.

[SantosGuillamot]

I'm blocking it until we have the design of the checkbox.

[luisherranz]

Thanks Mario. Could you please specify the Gutenberg inner blocks that will be used for the editable content?

[SantosGuillamot]

Oh yes, I forgot to post that sorry. I've updated the opening post.

[SantosGuillamot]

The designer has updated this, so I'm unblocking the issue.

[luisherranz]

Thanks Mario.

Some feedback about the editable content:

• I don't think placeholders are necessary, they are not going to change.
• I don't think the Privacy Policy is necessary, it is not going to change.
• The title, description and thank-you message are fine, but it's going to be hard to retrieve from the HTML with that layout. It's easier if that information is in the node itself. For example:
  • Using classes:

    <p class="title">Join the Frontity newsletter</p>
    <p class="description">Stay up-to-date on new releases and features, tutorials, and community news.</p>
    <p class="thank-you">Thank you! You have been subscribed to the Frontity newsletter. You will receive a welcome email shortly.</p>

  • Using children order (1st title, 2nd desc, 3rd thank-you):

    <p>Join the Frontity newsletter</p>
    <p>Stay up-to-date on new releases and features, tutorials, and community news.</p>
    <p>Thank you! You have been subscribed to the Frontity newsletter. You will receive a welcome email shortly.</p>

[SantosGuillamot]

In order to test if the logic of the old implementation could work, and check the best way to connect Gutenberg and React, I created this draft Pull Request #75 . It works so I guess the migration is possible. I share it in case it's useful as an starting point.