Automattic / Automattic/jetpack

Mailchimp Block: Consent text and customize option

Open
#16,823 2 comments 0 reactions 0 assignees View on GitHub
[Block] Mailchimp [Plugin] Jetpack [Pri] Low Enhancement
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

It's pretty common to have a subscription form in a confined space like a footer, for example:

![Screenshot 2020-08-13 at 12 13 07](https://user-images.githubusercontent.com/908665/90128572-01336b00-dd5f-11ea-8552-b996be2cbecb.jpg)

As you can see above, the lengthy consent text from the block makes it look tall and unpleasant. I had a look at [the Mailchimp's support page](https://mailchimp.com/help/add-a-signup-form-to-your-website/#Form_options) where we can see examples of their embed forms, and I didn't see the consent text around the form as default. That makes me wonder if we can remove it so that it could be more compact.

If we really have to have it then, can we shorten it? Can we provide a font size option for the text? Or can we change it to a notice that only appears in a confirmation step? I almost think an extra step would be better than the current state :)

Also, it'd be good to provide customize options just like the subscription block as well.

Lastly, the message that appears after adding an email doesn't look good either. We should remove the background on the text.

![Screenshot 2020-08-12 at 21 21 17](https://user-images.githubusercontent.com/908665/90132708-33949680-dd66-11ea-863a-249485cf7f11.jpg)

cc @apeatling @ianstewart @alaczek

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named. Start by locating the Mailchimp Block implementation and its existing customization controls, then review the consent text and post-submission message against the screenshots. The requested behavior needs agreement before implementation; done should be defined by an accepted scope and corresponding UI changes.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.