As part of our community building and fundraising, we would like to add a link to make it easy for users to join Tor's email list. We'll need final text, a URL, and a design.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
Sarah, Arthur
Since we are going to launch this before TB8, I made some mocks with current stable UI.
Do we want something more noticeable? Or keeping the same white containers is ok?
Please, check the attachments and let me know what do you think
That's just been the two strings, right? At any rate, I pushed those to master (commit 3e7502789eca79d2e73c82b65770fc0d08527584). Setting the state to new again for the remaining things.
Trac: Keywords: TorBrowserTeam201808R deleted, TorBrowserTeam201808 added Status: needs_review to new
I made some versions with different background color and position. If it takes a lot of time and we need to have it soon, I made a version with the link at the bottom.
Is it possible to have a top - white copy one with the colors shifted? Like instead of white copy a purple one and the background is white? I really would like to keep the envelope icon tho, not sure if that is only in white.
I feel we all the bottom ones very hard to even notice they are there, I would not use them.
That's just been the two strings, right? At any rate, I pushed those to master (commit 3e7502789eca79d2e73c82b65770fc0d08527584). Setting the state to new again for the remaining things.
I have just discovered that aboutTor.properties is no longer usable in about:tor, as a result of the patch from #26960 (moved) implementing our awesome new about:tor page. So here is a patch to move the two strings to aboutTor.dtd and remove the rest of aboutTor.properties file in each locale (I will ensure that any already-translated instances of the two "newsletter" strings are moved to the new location in Transifex.):
The code looks okay, but I am not happy with the behavior yet. So, the user get urged to subscribe to Tor News which I am generally fine with. However, I think it is bad behavior to still urge someone to subscribe somewhere after they already had or after they already made the decision to not subscribe (for whatever reasons). But the current patch does that as the banner is not going away. Now, that's hard to do without knowing the intentions or the one using the browser but one can simulate that by showing the banner only on first start or a small amount of times after first start. I think we should do something like that.
From a design perspective I am not happy either as the design at the top is drawing attention away from the onboarding we developed for 8.0. I think the onboarding is one of the major improvements for Tor Browser usability but right now once Tor Browser starts I fear users are only seeing the white banner (and might get annoyed by it because it does not go away).
I agree that our new user experience should have some momentum before we distract people with the banner.
Here is the calendar for what goes out and when:
09.05 - 8.0 stable release goes out without the newsletter banner
Before 09.28 Mexico meeting - we will probably need to do a bug fixing release, so the newsletter banner will go out with that release.
The experience from Firefox that this banner is based on does include an X for the user to close it. The X shows up when your mouse hoover over the banner. Can devs confirm that with me? I want to make sure there is a way for the user to close the banner (or express 'no').
10.23 stable release - Is when our YE campaign banner will go out.
The code looks okay, but I am not happy with the behavior yet. So, the user get urged to subscribe to Tor News which I am generally fine with. However, I think it is bad behavior to still urge someone to subscribe somewhere after they already had or after they already made the decision to not subscribe (for whatever reasons). But the current patch does that as the banner is not going away. Now, that's hard to do without knowing the intentions or the one using the browser but one can simulate that by showing the banner only on first start or a small amount of times after first start. I think we should do something like that.
From a design perspective I am not happy either as the design at the top is drawing attention away from the onboarding we developed for 8.0. I think the onboarding is one of the major improvements for Tor Browser usability but right now once Tor Browser starts I fear users are only seeing the white banner (and might get annoyed by it because it does not go away).
I agree with your points here. The code currently doesn't have an X to close the banner, but we can add one. And I think you're right we should wait for a later release to post this banner.
I think we could also consider a design in the future where the newsletter link is not so prominent but integrated better with the about:tor design. For example, it could look similar to the Tor Browser Manual link. That way we could include the newsletter link permanently without distracting from the more important elements in the design (such as the onboarding, the "Explore. Privately." tagline and the search box).
I think we could also consider a design in the future where the newsletter link is not so prominent but integrated better with the about:tor design. For example, it could look similar to the Tor Browser Manual link. That way we could include the newsletter link permanently without distracting from the more important elements in the design (such as the onboarding, the "Explore. Privately." tagline and the search box).
arthur yes, I agreed. I made a version here on the first round of iterations with that option. Maybe, we can discuss it with comms people too. They have another idea about how to use about:tor.
arthur yes, I agreed. I made a version here on the first round of iterations with that option. Maybe, we can discuss it with comms people too. They have another idea about how to use about:tor.
I'd be happy with it in there more discretely like this for now and for longer term (not if there is a similar banner at the same time). Is this back to being a possibility in 8.0?
just remove that line and use this.kAboutTorHideTorNewsBanner in the two instances needed directly. Having a kAboutTorHideTorNewsBanner in the function scope and declared above is confusing and seems not worth it.
Trac: Status: needs_review to needs_revision Keywords: TorBrowserTeam201809R deleted, TorBrowserTeam201809 added
const kAboutTorHideTorNewsBanner = this.kAboutTorHideTorNewsBanner;
}}}
just remove that line and use this.kAboutTorHideTorNewsBanner in the two instances needed directly. Having a kAboutTorHideTorNewsBanner in the function scope and declared above is confusing and seems not worth it.
Good catch. Here's a revised version where I fix that and rebased to the latest master.