1205858 - add new default "Contact Us" tab to /contact

Status: RESOLVED FIXED

(www.mozilla.org :: Pages & Content, defect)

Description

[Jennifer Bertsch [:jbertsch]]

Hi-

We want to elevate the ways in which folks can find information about contacting Mozilla on /contact.

Please add a new default tab to the left of Spaces titled "Contact Us".

This new tab will have the following new content:
I'm having problems with using Firefox https://support.mozilla.org/ 

I want to donate to Mozilla [note:  getting tracking url from Foundation]

I'm a reporter with a press inquiry [needs new form, Justin will provide form fields]

I have questions about copyright trademarks and Mozilla https://www.mozilla.org/foundation/trademarks/policy/ 

I need information for an academic paper [note:  hide until contact information is found]

I want to hold an event in a Mozilla space https://wiki.mozilla.org/People:MozSpaces_Guidelines

I want Mozilla to sponsor my event https://bugzilla.mozilla.org/form.dev-engagement-event 

I have a question about using Mozilla logos https://www.mozilla.org/styleguide/identity/mozilla/branding/

Plus the existing content under "Contacting Mozilla"

We'll remove "Contacting Mozilla" from the bottom of these pages.

Comment 1

[Jennifer Bertsch [:jbertsch]]

URL for Donate link https://sendto.mozilla.org/page/contribute/givenow-seq?preset=2&ref=Donation_Form&utm_campaign=Donation_Form&utm_source=mozilla.org&utm_medium=referral&utm_content=contact_us_page

Comment 2

[justinokelly]

Form fields for press inquiries:

Name
Title
Media organization
Subject of inquiry
Deadline

Comment 3

[Jennifer Bertsch [:jbertsch]]

Thanks for picking up this one, Schalk!  Let's chat about what the map view should look like for this new state of the page when you are ready.

Comment 4

[Jennifer Bertsch [:jbertsch]]

Here's the email address for Research Requests:  [e-mail]

This one is now ready to be worked on.

Thanks!

Comment 5

[Schalk Neethling [:espressive]]

(In reply to justinokelly from comment #2)
> Form fields for press inquiries:
> 
> Name
> Title
> Media organization
> Subject of inquiry
> Deadline

I am guessing all of these except probably "Deadline" are required fields?

Comment 6

[Schalk Neethling [:espressive]]

(In reply to justinokelly from comment #2)
> Form fields for press inquiries:
> 
> Name
> Title
> Media organization
> Subject of inquiry
> Deadline

Do you want title to be a select drop-down like:

<option value="1">Mr</option>
<option value="2">Mrs</option>
<option value="3">Miss</option>
<option value="4">Ms</option>
<option value="5">Dr</option>
<option value="6">Professor</option>

or just a plain text input field.

Comment 7

[Craig Cook (:craigcook)]

(In reply to Schalk Neethling [:espressive] from comment #6)

> Do you want title to be a select drop-down like:
> 
> <option value="1">Mr</option>
> <option value="2">Mrs</option>
> <option value="3">Miss</option>
> <option value="4">Ms</option>
> <option value="5">Dr</option>
> <option value="6">Professor</option>
> 
> or just a plain text input field.

I assume that's job title, rather than a salutation, so it would be a text field. 

If this form is specifically and exclusively for press inquiries, we can require title and media organization. If it's a more general contact form, then title and organization should be optional (and I'd make 'media organization' a more generic 'company' field).

Comment 8

[justinokelly]

I don't need a title dropdown, thanks.

Job title helps us determine if they are a reporter or editor.

This is exclusively for press inquiries, we do not want any of these drop downs to be optional.

Thanks

Justin

Comment 9

[Schalk Neethling [:espressive]]

(In reply to justinokelly from comment #8)
> I don't need a title dropdown, thanks.
> 
> Job title helps us determine if they are a reporter or editor.
> 
> This is exclusively for press inquiries, we do not want any of these drop
> downs to be optional.
> 
> Thanks
> 
> Justin

Won't we need the person's email address as well?

Comment 10

[Schalk Neethling [:espressive]]

Attachment: contact_tab.png

Wanted to provide a quick update. Here is how the tab currently looks, please let me know if there are any changes required.

All that is left to do is a responsive issue, because there are now three tabs, hooking up the form and updating the functional tests for the page.

Let me know your thoughts.

Comment 11

[Schalk Neethling [:espressive]]

So, I am not entirely happy with the layout yet. Some suggestions:

1) Float the content below the form on the right on larger viewports and change to this layout for smaller viewports.

2) Alternative, have the three sub-sections at the bottom fit next to each other on larger viewports and change the layout resposively as the viewport or window size decreases.

Comment 12

[Jennifer Bertsch [:jbertsch]]

(In reply to Schalk Neethling [:espressive] from comment #10)
> Created attachment 8666661 [details]
> contact_tab.png
> 
> Wanted to provide a quick update. Here is how the tab currently looks,
> please let me know if there are any changes required.
> 
> All that is left to do is a responsive issue, because there are now three
> tabs, hooking up the form and updating the functional tests for the page.
> 
> Let me know your thoughts.

Thanks, Schalk!

+Holly for feedback on layout.

Comment 13

[Holly Habstritt Gaal [:Habber]]

(In reply to Jennifer Bertsch [:jbertsch] from comment #12)
> (In reply to Schalk Neethling [:espressive] from comment #10)
> > Created attachment 8666661 [details]
> > contact_tab.png
> > 
> > Wanted to provide a quick update. Here is how the tab currently looks,
> > please let me know if there are any changes required.
> > 
> > All that is left to do is a responsive issue, because there are now three
> > tabs, hooking up the form and updating the functional tests for the page.
> > 
> > Let me know your thoughts.
> 
> Thanks, Schalk!
> 
> +Holly for feedback on layout.

Jen and I spoke about the prioritization of the Press form and would like to do the following:

- add a bullet point to the 'Contacting Mozilla' list
- bullet point says something like "I'm a member of the Press and have a question for Mozilla" (not final copy)
- display Press form to user only once the link is selected. (initial state of page does not display form)

- It sounds like all the contact links have varying next steps that open in a new tab. We discussed expanding this form inline when the "I am a member of the Press..." link is clicked. However, since none of the other links manipulate the page by expanding below, I think it would be better to show this form in an overlay. I'm open to other suggestions for hiding/expanding this form. 

- We also discussed that the state of the map for this tab would show the Mozilla Spaces.

Comment 14

[justinokelly]

These sounds like good changes to me. Can I see a final mock up before we're ready to push this live?

Comment 15

[Schalk Neethling [:espressive]]

Attachment: Initial state

Comment 16

[Schalk Neethling [:espressive]]

Attachment: form expanded

Actually, showing and hiding the form inline fits with the interaction on spaces and community where clicking on a space or community link will load the content into the current page.

The other links will all open in the same window and not a new tab unless, opening in a new tab is what is required.

Comment 17

[Holly Habstritt Gaal [:Habber]]

(In reply to Schalk Neethling [:espressive] from comment #16)
> Created attachment 8667882 [details]
> form expanded
> 
> Actually, showing and hiding the form inline fits with the interaction on
> spaces and community where clicking on a space or community link will load
> the content into the current page.
> 
> The other links will all open in the same window and not a new tab unless,
> opening in a new tab is what is required.

Hey Schalk, what I mean is that we don't have any interaction that adds/hides content within a page like this. All contact links have a way of keeping form interaction separated from this page state. I've thought about this a little further and would like to discuss the following before finalizing this...

Jen and Justin, would there be any reason to put this form on a standalone page? For example, the speaker request form is located here https://www.mozilla.org/en-US/press/speakerrequest/, within /press/ on Mozilla.org. There are also other places on Mozilla.org that may want to link to the press contact form. For example, currently there is a link on the Press blog that just goes to a mailto: link (mailto: [e-mail]...). I would think it makes sense to have all inquiries point to the same place and in the same structured format that the form allows. Putting this form on a dedicated page (vs. using a mailto: link or something placed inline on the /contact/ page) would allow it to be more versatile. It would also keep the interaction the same as all the other contact links on /contact/, which open in a new tab.

Comment 18

[Schalk Neethling [:espressive]]

(In reply to Holly Habstritt Gaal [:Habber] from comment #17)
> (In reply to Schalk Neethling [:espressive] from comment #16)
> > Created attachment 8667882 [details]
> > form expanded
> > 
> > Actually, showing and hiding the form inline fits with the interaction on
> > spaces and community where clicking on a space or community link will load
> > the content into the current page.
> > 
> > The other links will all open in the same window and not a new tab unless,
> > opening in a new tab is what is required.
> 
> Hey Schalk, what I mean is that we don't have any interaction that
> adds/hides content within a page like this. All contact links have a way of
> keeping form interaction separated from this page state. I've thought about
> this a little further and would like to discuss the following before
> finalizing this...
> 
> Jen and Justin, would there be any reason to put this form on a standalone
> page? For example, the speaker request form is located here
> https://www.mozilla.org/en-US/press/speakerrequest/, within /press/ on
> Mozilla.org. There are also other places on Mozilla.org that may want to
> link to the press contact form. For example, currently there is a link on
> the Press blog that just goes to a mailto: link (mailto:
> [e-mail]...). I would think it makes sense to have all inquiries
> point to the same place and in the same structured format that the form
> allows. Putting this form on a dedicated page (vs. using a mailto: link or
> something placed inline on the /contact/ page) would allow it to be more
> versatile. It would also keep the interaction the same as all the other
> contact links on /contact/, which open in a new tab.

That is a *very* good point and suggestion Holly. I would +1 creating a simple dedicated page for this form.

Comment 19

[justinokelly]

Love that idea, thanks. The separate page could live where Media Contact does on the right hand side of the press center now.

Note that we will need this localized for the non EN-US press centers, but I will talk to my EU colleagues about that as soon as you tell me it's in a state we can share with them.

Justin

Comment 20

[Jennifer Bertsch [:jbertsch]]

(In reply to justinokelly from comment #19)
> Love that idea, thanks. The separate page could live where Media Contact
> does on the right hand side of the press center now.
> 
> Note that we will need this localized for the non EN-US press centers, but I
> will talk to my EU colleagues about that as soon as you tell me it's in a
> state we can share with them.
> 
> Justin

Sounds good to me too.  Thanks.

Comment 21

[Schalk Neethling [:espressive]]

Awesome, now that we are all on the same page :p I am going to complete this bug but, exclude the form and the press link.

I will then open a separate bug to add the link on the contact us and, the form page.

Comment 22

[justinokelly]

Liz Compton, Tim Murray and I got a chance to meet today to discuss workflow around inquiries about logos and copyright trademark issues. We came up with the following ideas we think will improve the process:

Firstly they are added to the bug and discussing whether to combine the copyright trademark inquiry line with the logo line and how to channel inquiries.

Secondly we agreed the first line should read:

I'm having problems with using Firefox or other Mozilla products

Thirdly we agreed (whether it's combined as above or not),  the eight line should read:

I have a question about using Mozilla or Firefox product logos

Fourthly we agree an additional line should be added (above 'I'm having problems etc) :

I want to give feedback about a Mozilla product (and link to this page: https://input.mozilla.org/en-US/feedback)

Fifthly we think a line should be added that says:

"I want more information from Mozilla"  and this should link to a page Greg Jost (copied on bug now) can provide)

In addition I've added Rob Middleton and Shezmeen Prasad to this bug so they are aware of the spaces/events questions that their teams own responses for and can weigh in if they see problems with how we are setting things up.

Let us know if this can be done or if this raises other questions?

Justin

Comment 23

[Jennifer Bertsch [:jbertsch]]

Hi Justin-

I'd like to move forward with getting the page live as originally requested and sort out these changes separately.

I'm not sure the input form is meant to be linked to from web pages vs from in-product user experiences.  I'll follow up directly with the team that owns that form.

Hopefully nothing here is disruptive/new to Rob or Shez as these links already exist on the page.

Ideally, if this sort of due diligence was needed, we would have completed it before coding started.

Thanks,
Jen

Comment 24

[Gregory Jost]

> "I want more information from Mozilla"  and this should link to a page Greg Jost (copied on bug now) can provide)

Hey there. I can't think of a specific page that does that. Both the current page and mock-ups have a Mozilla signup at the bottom under the links section. Could we simply have the page scroll down to the bottom when users click "I want more info from Mozilla"? Or does it have to link out?

Comment 25

[Jennifer Bertsch [:jbertsch]]

(In reply to Gregory Jost from comment #24)
> > "I want more information from Mozilla"  and this should link to a page Greg Jost (copied on bug now) can provide)
> 
> Hey there. I can't think of a specific page that does that. Both the current
> page and mock-ups have a Mozilla signup at the bottom under the links
> section. Could we simply have the page scroll down to the bottom when users
> click "I want more info from Mozilla"? Or does it have to link out?

If we don't have a good answer for "I want more information about Mozilla," I would like to leave this link off for now.  The current email program doesn't really answer that question.

Comment 26

[justinokelly]

Ah ok thanks Greg, Tim was sure you had one where you had people sign up for email newsletters, but agreed if that doesn't exist, let's not include it!

Comment 27

[justinokelly]

Re comment 23

Hi Jenn

Sure thing, none of these comments are blockers but let's not close this bug out till they are implemented (granted Liz and Tim have to conclude discussion on the first element in my today comment).

And apologies the diligence was done partly back to front by me.

Justin

Comment 28

[Rob Middleton]

WPR gets many emails requesting help for more than just firefox, Thunderbird for example.  Should the line not be specific to Firefox, but more along the lines of "I am having problems using one of my Mozilla Products"

Comment 29

[Schalk Neethling [:espressive]]

Should I go ahead and finish the initial PR and then we address these additional requests in a separate bug or, wait?

Comment 30

[justinokelly]

Hi Neethling,

Jenn and I discussed this and because my gathered input came a bit late in the day we'd like work to continue completing the original request, but keep this bug open and add the additional fixes as soon as possible this quarter after it launches. 

Justin

Comment 31

[Schalk Neethling [:espressive]]

(In reply to justinokelly from comment #30)
> Hi Neethling,
> 
> Jenn and I discussed this and because my gathered input came a bit late in
> the day we'd like work to continue completing the original request, but keep
> this bug open and add the additional fixes as soon as possible this quarter
> after it launches. 
> 
> Justin

Alrighty, will finish up this one.

Comment 32

[Schalk Neethling [:espressive]]

Attachment: communities

At small viewports we are really cramped for space. Even though this might have an l10n impact, I am wondering if we can change "Communities" to "Community"?

Comment 33

[Schalk Neethling [:espressive]]

Attachment: community

Here is the previous screen shot but, it uses "Community" as apposed to "Communities"

Comment 34

[Schalk Neethling [:espressive]]

:habber Thoughts?

Comment 35

[Holly Habstritt Gaal [:Habber]]

(In reply to Schalk Neethling [:espressive] from comment #34)
> :habber Thoughts?

"Communities" (plural) is more likely to set the expectation that there are multiple communities around the world. For this reason, "Communities" was chosen here. When this page was built we also had a discussion about this word with the community team and they preferred "communities". However, they're all part of the Mozilla "community" so I could understand why that might be considered.

How do you feel about bumping the font size down a point on "communities" for the smallest viewport size and see how it looks before opening up discussions about the word. (you may have already tried this)

Comment 36

[Schalk Neethling [:espressive]]

Attachment: Link to Github pull-request: https://github.com/mozilla/bedrock/pull/3412

Comment 37

[Schalk Neethling [:espressive]]

(In reply to Holly Habstritt Gaal [:Habber] from comment #35)
> (In reply to Schalk Neethling [:espressive] from comment #34)
> > :habber Thoughts?
> 
> "Communities" (plural) is more likely to set the expectation that there are
> multiple communities around the world. For this reason, "Communities" was
> chosen here. When this page was built we also had a discussion about this
> word with the community team and they preferred "communities". However,
> they're all part of the Mozilla "community" so I could understand why that
> might be considered.
> 
> How do you feel about bumping the font size down a point on "communities"
> for the smallest viewport size and see how it looks before opening up
> discussions about the word. (you may have already tried this)

I bumped the font size down and, whilst the size is really small, it is the best solution for now I believe. Thanks Holly!

Comment 38

[Liz Compton [:liz]]

Hi all - Here are the trademark related changes I'd like to request be implemented in the first round of changes after launch. 

Add "I'd like to report misuse of a Mozilla trademark" with a link to https://www.mozilla.org/en-US/about/legal/fraud-report/

Change "I have questions about copyright trademarks and Mozilla" to "I have questions about using Mozilla's trademarks"

Change "I have a question about using Mozilla logos" to "I'd like permission to use a Mozilla logo" and change the link to the email address [e-mail]. This email address doesn't exist yet, but I'm going to request that it be created.

Thanks,
Liz

Comment 39

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/05b7bd1e93fa4c52a2877a05e9244b84f4039081
Fix Bug 1205858, adds new default contact us tab to contact page

https://github.com/mozilla/bedrock/commit/c5aa82efb254d5d3d564b4fbba9aed4a910f7827
Merge pull request #3412 from schalkneethling/bug1205858-add-new-default-contact-tab

Fix Bug 1205858, adds new default contact us tab to contact page

Comment 40

[Schalk Neethling [:espressive]]

The new contact tab has been merged and will be in prod soon. The press inquiry page will follow and will most likely go live at the same time.

Reopening this for the string changes.

Comment 41

[Schalk Neethling [:espressive]]

The press inquiry page/form has also been merged and a link from the new contact tab to it.

Comment 42

[Schalk Neethling [:espressive]]

(In reply to Liz Compton [:liz] (please use need info) from comment #38)
> Hi all - Here are the trademark related changes I'd like to request be
> implemented in the first round of changes after launch. 
> 
> Add "I'd like to report misuse of a Mozilla trademark" with a link to
> https://www.mozilla.org/en-US/about/legal/fraud-report/
> 
> Change "I have questions about copyright trademarks and Mozilla" to "I have
> questions about using Mozilla's trademarks"
> 
> Change "I have a question about using Mozilla logos" to "I'd like permission
> to use a Mozilla logo" and change the link to the email address
> [e-mail]. This email address doesn't exist yet, but
> I'm going to request that it be created.
> 
> Thanks,
> Liz

Pull request for these updates: https://github.com/mozilla/bedrock/pull/3437

Comment 43

[Schalk Neethling [:espressive]]

Hey Justin,

Can you please provide me with a rounds up of the content updates you require? Thanks!

Comment 44

[justinokelly]

URGENT NEED BEFORE THE OTHER UPDATES I'VE ASKED FOR:

Please amend the Press form so it makes you input an email address to contact them back. It's already being used and we have no way to contact people back!

It should go under Name

Justin

Comment 45

[Schalk Neethling [:espressive]]

(In reply to justinokelly from comment #44)
> URGENT NEED BEFORE THE OTHER UPDATES I'VE ASKED FOR:
> 
> Please amend the Press form so it makes you input an email address to
> contact them back. It's already being used and we have no way to contact
> people back!
> 
> It should go under Name
> 
> Justin

Will do.

Comment 46

[Schalk Neethling [:espressive]]

(In reply to justinokelly from comment #44)
> URGENT NEED BEFORE THE OTHER UPDATES I'VE ASKED FOR:
> 
> Please amend the Press form so it makes you input an email address to
> contact them back. It's already being used and we have no way to contact
> people back!
> 
> It should go under Name
> 
> Justin

Pull request opened https://bugzilla.mozilla.org/show_bug.cgi?id=1215229#c1

Comment 47

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/6217987286a9af00a52e1750f219840e09544a61
Fix Bug 1205858, updated content for contact tab

https://github.com/mozilla/bedrock/commit/29c9c078d1bc2906625d1b9426a2827d66108ad8
Merge pull request #3437 from schalkneethling/bug1205858-content-updates-for-new-contact-tab

Fix Bug 1205858, updated content for contact tab

Comment 48

[justinokelly]

Hi Schalk,

After adding the email line to the Press form so we can contact people who contact us, I believe Liz's changes in comment 38 are what's next to implement.

Let us know when those are done?

Justin

Comment 49

[Schalk Neethling [:espressive]]

(In reply to justinokelly from comment #48)
> Hi Schalk,
> 
> After adding the email line to the Press form so we can contact people who
> contact us, I believe Liz's changes in comment 38 are what's next to
> implement.
> 
> Let us know when those are done?
> 
> Justin

They have both been merged to master and I believe we have had a push to production.

Comment 50

[Liz Compton [:liz]]

Hi Schalk - I had reason to visit the German language version of our website today and saw that this page hasn't been translated into German. What's the process to get it localized?

Comment 51

[Schalk Neethling [:espressive]]

(In reply to Liz Compton [:liz] from comment #50)
> Hi Schalk - I had reason to visit the German language version of our website
> today and saw that this page hasn't been translated into German. What's the
> process to get it localized?

Hey Liz, I would say the best person to talk to is :flod, will need info him here.

Comment 52

[Francesco Lodolo [:flod]]

I don't know why this page has not been translated so far, but I believe it makes a lot of sense to have it only in English: 
* If we localize the page in German (or, better, in a smaller locale like Irish), who's going to deal with the requests? Localized inquiries go through the /contribute channel, where local team see and manage the requests in their own languages. Having the page in English makes it kind of clear that English is needed for inquiries.
* There's a lot of content to localize in that page (the other two tabs), and I don't think that's a good investment of limited resources.

Comment 53

[Jennifer Bertsch [:jbertsch]]

(In reply to Francesco Lodolo [:flod] from comment #52)
> I don't know why this page has not been translated so far, but I believe it
> makes a lot of sense to have it only in English: 
> * If we localize the page in German (or, better, in a smaller locale like
> Irish), who's going to deal with the requests? Localized inquiries go
> through the /contribute channel, where local team see and manage the
> requests in their own languages. Having the page in English makes it kind of
> clear that English is needed for inquiries.
> * There's a lot of content to localize in that page (the other two tabs),
> and I don't think that's a good investment of limited resources.

+1 flod

Comment 54

[Liz Compton [:liz]]

That may be the right decision, but just as a point of information, I get a lot of emails to [e-mail] from Germans that have nothing to do with Legal, they're mostly looking for product support. The better solution to that may be to add the SUMO URL to the German specific page https://www.mozilla.org/en-US/about/legal/impressum/. I'm guessing that's where they get the legal-notices email address.