Closed
Bug 1254265
Opened 9 years ago
Closed 4 years ago
Mozilla Foundation email signup form on mozillians.org?
Categories
(Participation Infrastructure :: Phonebook, defect)
Participation Infrastructure
Phonebook
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jdavis, Unassigned, Mentored)
Details
(Whiteboard: [iam-RFE])
Feature idea:
Could be cool to have the Mozilla Foundation newsletter signup on the footer of mozillians.org? (ie like the "Get Mozilla updates" on mozilla.org/en-US )
Or the "Get community updates" like on /contribute ? (If that newsletter is going to be resurrected)
Likewise an email newsletter opt-in as part of the mozillians.org registration flow for the right corresponding newsletter.
Comment 2•9 years ago
|
||
We could have this as a profile option.
Actually we were thinking to spin off the email settings in your profile (list of emails associated, primary email selection, in what language you want to be contacted etc) as a profile edit section.
Managing subscription and subscription options (e.g.for groups, locales etc) would be a really nice addition there.
What do you think Jess?
Flags: needinfo?(pierros)
Reporter | ||
Comment 3•9 years ago
|
||
I LOVE that idea, Pierros!
The FxAccounts team tried to do something similar within the FxAccounts setting page, but I'm unsure if they got it to work seamlessly vs. linking the user directly to their email preference center page. I know some options were to 1) link to it externally, 2) display it as an iframe, 3) recreate the email preference center within the settings page itself.
I think you've got what you need (ie familiarity with Basket code & documentation) to explore the options and see what magic you can create in mozillians.org. I say go for it! :D
![]() |
||
Comment 4•4 years ago
|
||
This is an RFE specific to mozillians, which is decom'ed.
If this is found to pertain to people.mozilla.org then please open a new issue.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
Whiteboard: [iam-RFE]
You need to log in
before you can comment on or make changes to this bug.
Description
•