Implement ABP newsletter signup form

[ire]

Implement ABP newsletter signup form in accordance with the ​Specification

Link to the English version of Backclick documentation can be found ​here.

[ire]

Default Confirmation Email

[ire]

@all : It looks like we will also have to create a new confirmation email template. When the user signs up, they receive an email telling them to confirm that they want to subscribe. I've attached a screenshot of what this currently looks like.

As you can see, it looks pretty bad :( I don't think we should launch this new newsletter signup page without also fixing this as well.

[jeen]

Thanks for bringing this to our attention. Agreed, we should not launch without an email template. Marsha and I are working on this now, and will add it to the issue on GitLab, but this shouldn't block you for now.

[jeen]

Hi Ire,

I have attached the email template designs, let me know if these work?

[ire]

Replying to jeen:

Hi Ire,

I have attached the email template designs, let me know if these work?

Thanks Jeen! This looks good to me. I'm going to create a separate issue for the email template so any discussion on that can happen there.

[ire]

@all: Issue #6215 - Create custom email template for ABP Newsletter

[ire]

In codereview, On 2017/12/21 16:07:57, saroyanm wrote:

I assume we are planing to update the privacy policy to reflect the backclick
privacy policy and link to that header, right ?
Also, make sense to check to which website the update will land, because we also
used to have extended Privacy Policy in ​http://eyeo.com, with Privacy Policy
information like "talent tracker".

@wspee @jeen Could you help answer this?

[jeen]

Yes we will be adding it to the eyeo.com privacy policy as per the ticket on [GitLab here](​https://gitlab.com/eyeo/web.eyeo.com/issues/2)

[wspee]

Replying to ire:

In codereview, On 2017/12/21 16:07:57, saroyanm wrote:

I assume we are planing to update the privacy policy to reflect the backclick
privacy policy and link to that header, right ?
Also, make sense to check to which website the update will land, because we also
used to have extended Privacy Policy in ​http://eyeo.com, with Privacy Policy
information like "talent tracker".

@wspee @jeen Could you help answer this?

To not have to go through translations (this would add ~1-2 Month currently) we decided to add the backclick related changes the eyeo.com privacy policy (the form is not part of abp.org) instead, see:

​https://gitlab.com/eyeo/web.adblockplus.org/issues/1#what-to-do
​https://gitlab.com/eyeo/web.eyeo.com/issues/2

The newsletter sign up form links to the eyeo.com privacy policy see:

​https://gitlab.com/eyeo/spec/merge_requests/110/diffs#14aa898ad23db081e78a168a4f41e7aad0e7c32c_0_70

Both changes (in conjunction) have been LGTMed by Judith.

[ire]

Thanks @Jeen and @Wspee . So I will link to https://eyeo.com/en/privacy from the signup form instead

[jeen]

@ire correct!

[saroyanm]

I'm not sure why we have chosen Backclick, but I'll strongly discourage to consider any service provider in future(with hope that we will find alternative to current one) who doesn't provide documentation and support in English, even comments in the code are in German, that's a dangerous practice.

[saroyanm]

Replying to saroyanm:

I'm not sure why we have chosen Backclick, but I'll strongly discourage to consider any service provider in future(with hope that we will find alternative to current one) who doesn't provide documentation and support in English, even comments in the code are in German, that's a dangerous practice.

Never-mind, I saw in the IRC channel that they have English documentation, but non of our Developers were aware of it's existence.

[ire]

@wspee: Backclick has a feature to create a blacklist of emails we don't want to be allowed to subscribe to the newsletter. Would you like us to support it in our template?

For context, this feature is currently supported in our template and doesn't require much more/any development effort to include it. But, if we won't use it we should remove it from the template for less clutter.

[juliandoucette]

P2 because comms would like to send a newsletter next week.

[wspee]

Replying to ire:

@wspee: Backclick has a feature to create a blacklist of emails we don't want to be allowed to subscribe to the newsletter. Would you like us to support it in our template?

For context, this feature is currently supported in our template and doesn't require much more/any development effort to include it. But, if we won't use it we should remove it from the template for less clutter.

What blacklist? Are you talking about the eRobinson feature?
​https://www.backclick.de/confluence/display/BC5EN/Basics+on+eRobinson+lists

[ire]

Replying to wspee:

Replying to ire:

@wspee: Backclick has a feature to create a blacklist of emails we don't want to be allowed to subscribe to the newsletter. Would you like us to support it in our template?

For context, this feature is currently supported in our template and doesn't require much more/any development effort to include it. But, if we won't use it we should remove it from the template for less clutter.

What blacklist? Are you talking about the eRobinson feature?
​https://www.backclick.de/confluence/display/BC5EN/Basics+on+eRobinson+lists

Yes I'm referring to the eRobinson feature

[wspee]

Replying to ire:

Yes I'm referring to the eRobinson feature

Hmm normally this is used to exclude receivers that would hurt the delivery of the newsletter, not sure why a user would want to use it?!

Is it perhaps a backclick quirk and normally used to handle opt-outs? If not I would say remove it? @Jeen?

​https://docs.aws.amazon.com/ses/latest/DeveloperGuide/e-faq.html#e-faq-bn

[ire]

Replying to wspee:

Replying to ire:

Yes I'm referring to the eRobinson feature

Hmm normally this is used to exclude receivers that would hurt the delivery of the newsletter, not sure why a user would want to use it?!

My question was to ask if *we* want to support it.

If we are planning on using it, we would need to have something on the frontend to let the user know that the reason they cannot sign up with the particular email address is because it is part of this blacklist/eRobinson list.

If we are not planning on using it, we would remove this logic from the template.

[jeen]

I would say we don't need to support this, so let's remove the logic from the template.

Replying to ire:

Replying to wspee:

Replying to ire:

Yes I'm referring to the eRobinson feature

Hmm normally this is used to exclude receivers that would hurt the delivery of the newsletter, not sure why a user would want to use it?!

My question was to ask if *we* want to support it.

If we are planning on using it, we would need to have something on the frontend to let the user know that the reason they cannot sign up with the particular email address is because it is part of this blacklist/eRobinson list.

If we are not planning on using it, we would remove this logic from the template.

[ire]

Replying to jeen:

I would say we don't need to support this, so let's remove the logic from the template.

Alright. Thanks!

[ire]

Closed on Gitlab ​https://gitlab.com/eyeo/web.adblockplus.org/issues/1