Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Home page updates for june #14543

Closed
Tracked by #14229
enavajas opened this issue May 2, 2024 · 10 comments · Fixed by #14552
Closed
Tracked by #14229

Home page updates for june #14543

enavajas opened this issue May 2, 2024 · 10 comments · Fixed by #14552
Assignees

Comments

@enavajas
Copy link
Collaborator

enavajas commented May 2, 2024

Hello. We are going to make the following changes to the www.mozilla.org homepage.

HERE is the figma file containing the changes. (Mozilla only)

The design + copy in the figma file is final except for the copy in the Trustworthy AI section. That will be shared with us shortly, and I will comment once we have it.

Please put this on a demo server once ready so I can share w/ the team.

@stephaniehobson stephaniehobson changed the title Changes to moz.org - add FakeSpot, update copy on footer, and add to innovation menu Add FakeSpot, update copy on footer, and add to innovation menu May 3, 2024
@enavajas enavajas changed the title Add FakeSpot, update copy on footer, and add to innovation menu Home page updates for june May 3, 2024
@reemhamz
Copy link
Contributor

reemhamz commented May 6, 2024

Can we have the team verify what URLs we should use for some of the updates too? For example, which URL should I use for Fakespot? Should we be using the AMO URL or the Fakespot landing page?

@enavajas
Copy link
Collaborator Author

enavajas commented May 6, 2024

Can we have the team verify what URLs we should use for some of the updates too? For example, which URL should I use for Fakespot? Should we be using the AMO URL or the Fakespot landing page?

Yes – I will get all of those confirmed for you.

@stephaniehobson
Copy link
Contributor

This came in via email:

... one thing to add for the Mozilla.org homepage - our fundraising team would like to use '?form=featured-section' to track donations coming from the mozilla.org homepage (so the url I believe should be https://mozilla.org/?form=featured-section).

@slightlyoffbeat
Copy link
Collaborator

slightlyoffbeat commented May 9, 2024

I'm going to consolidate a few things into here a checklist:

Ready:

  • Pocket logo always looks optically larger than the other logos. Lets make the pocket logo 44x44px with 3px padding in the image (that way we do a 1:1 swap)
  • Change the 'trustworth AI' section into a split component with an image on the right side. Copy and Image TBD.
  • Can we change the font-size for the 3x2 picto section to have text be 16px? Will make everything line up.
  • Change Monitor text to "Reclaim your private info" to shorten
  • Fakespot link should link to https://www.fakespot.com/ with campaign tags similar to what is used for relay and monitor link

Not ready:

  • final image for Trustworthy AI section
  • Final copy, link, and CTA text for Trustworthy AI section
  • Links for moco/ventures/ai section

@reemhamz
Copy link
Contributor

reemhamz commented May 13, 2024

Also, I believe it's about time we finally add Fakespot to the Products nav. Thoughts?

Screenshot 2024-05-13 at 2 43 33 PM

@slightlyoffbeat
Copy link
Collaborator

slightlyoffbeat commented May 14, 2024

@reemhamz yes! we should add fakespot to nav.

Here's the next set of updates. A few changes, but mostly minor. Refer to this doc when referring to "doc"

  • remove the three icon section with Mozilla AI, Mozilla VC, and moco
  • Update "is Mozilla a Corporation" copy section (see doc, section 1)
  • Update Trustworthy AI copy section (see doc, section 2)
  • Update Trustworthy AI copy section to use attached image
  • Make sure all external links on homepage (excluding nav/footer) use campaign params ?utm_source=www.mozilla.org&utm_medium=referral&utm_campaign=homepage
  • external nav link for fakespot should use ?utm_source=www.mozilla.org&utm_medium=referral&utm_campaign=nav&utm_content=products
  • update relay copy -- (see doc, section 3)
  • update monitor copy -- (see doc, section 3)

ai-1

@reemhamz
Copy link
Contributor

@slightlyoffbeat Thanks! I'll work on these changes shortly.
Curious, are we still going to be linking the Moz Ventures and Moz AI pages in our nav? I'm still waiting on the URLs + description of those.

@reemhamz
Copy link
Contributor

reemhamz commented May 16, 2024

Couple more questions:

  1. For Monitor, we currently have 2 copies showing for en-US vs global:
  • en-US: Reclaim your private info
  • Global: Private & secure browsing
    Is the new Monitor copy (Protect your private info from data brokers) meant to be for all locales?
  1. The new Relay and Monitor copies are long compared to the rest of the product descriptions. Is this fine?
    Screenshot 2024-05-16 at 4 17 03 PM

@slightlyoffbeat
Copy link
Collaborator

slightlyoffbeat commented May 22, 2024

Final stretch!

  • Lets change order to hide the mismatched line heights a bit. Move Relay to bottom left. Fakespot to top right. VPN to bottom middle
  • We will not be linking to ventures and mozilla AI in nav for now. Only nav changes should be adding fakespot
  • There's a typo. Space missing: MZLA, Mozilla Venturesand Mozilla AI
  • We will be linking to Mozilla Ventures and Mozilla AI in the paragraph text for the "So, what is Mozilla" section. URL is https://www.mozilla.ai/ and https://mozilla.vc/
  • Please use standard UTM params for the paragraph text links: ?utm_source=www.mozilla.org&utm_medium=referral&utm_campaign=homepage
  • Lets have Protect your private info from data broke be for all locales.

@slightlyoffbeat
Copy link
Collaborator

Reviewed everything on demo, and it looks good to me. Thumbs up from me as long as review, etc is good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants