Closed Bug 1058936 Opened 12 years ago Closed 2 years ago

Open Standard Newsletter Signup

Categories

(Websites :: The Open Standard, defect)

Beta
x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: bensternthal, Assigned: rex)

References

Details

User Story

I mocked up how this should work with the correct hidden fields, please see the below link for a working example.

http://jsfiddle.net/2wcqowzs/4/

This fully works and if you enter your email address a short time later you will get a confirmation email. Note right now it's using the 'affiliates' newsletter.

Please code so that the 'newsletter signup' module in the footer can easily be commented out, it's possible we wont have the newsletter for launch.
This bug tracks adding the newsletter signup for voices. We will be collecting: - email - country information - language (en for launch) This newsletter will be daily however it will not be ready for launch.
Blocks: 1046397
Depends on: 909934
This bug handles implementing the newsletter signup in the footer. The behavior should be close to https://www.mozilla.org/en-US/firefox/new/ I will add info about where/how this form gets submitted once I collect that information.
Assignee: nobody → rex
No longer depends on: 909934
User Story: (updated)
There will need to be 3 new check-box fields added to the signup form based on Anthony's vision: Daily Weekly Special announcements Each of these will correspond to a new field in basket + ExactTarget: OPEN_STANDARD_DAILY_FLG OPEN_STANDARD_DAILY_DATE OPEN_STANDARD_WEEKLY_FLG OPEN_STANDARD_WEEKLY_DATE OPEN_STANDARD_SPECIAL_FLG OPEN_STANDARD_SPECIAL_DATE These should all fire the same welcome email "Open_Standard_Welcome" that will have conditional content based on what frequency(ies) they choose. The basket change that may need to happen is that only 1 welcome email should fire based on one - or all 3 - subscription flags. I.e: 3 welcome emails shouldn't be sent for each individual flag - likewise, only one subscription confirmation email should be fired. Anthony should confirm if we should only show 1 option at launch, or all 3. I'll file the dependent bugs for the welcome email (creative & ET work), confirmation email (creative + ET work), and then the implementation of the daily, weekly and special announcement emails (creative + ET work). Ben, should the basket work pieces for the signup form be in this bug, or separated out? There's also the need to make sure that the moz.org/newsletter privacy policy opt-in language is appropriate for this email comm. I'm cc'ing Mika to chime in here.
Flags: needinfo?(udevi)
Flags: needinfo?(acabrera)
Summary: Newsletter Signup → Open Standard Newsletter Signup
This is the correct bug for the reqs to implement the form on the open standard website. Can you let me know what the 3 newsletter names are that we will send to basket? I am looking for the exact values for the newsletters field.
I think we should just launch with the one option, the Daily Newsletter.
Flags: needinfo?(acabrera)
Newsletter will launch a few weeks after live date (exact date TBD). We will comment out the form for now.
No longer blocks: 1046397
Blocks: 1080156
Blocks: 1080157
No longer blocks: 1080157
Depends on: 1080157
Depends on: 1080163
Depends on: 1080918
I reviewed http://jsfiddle.net/2wcqowzs/4/ and the disclaimer and privacy link are correct.
Flags: needinfo?(udevi)
Mika - just an FYI we punted this to be post launch. The singup form will not be present on the site when we launch next week.
Question on the daily newsletter concept (which I know is post-launch). Will you get metrics on how many people opt-out? The sign-up flow that I saw doesn't say that it's daily. So as a user, if I signup and then receive the welcome email that it's daily, I might want to unsubscribe (or elect another option). Is there a plan in place to (1) measure drop off (2) recapture those users by offering a weekly option
No longer blocks: 1080156

The Open Standard Website is no longer active

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.