Provide Final Copy For Content Pages

RESOLVED FIXED

Status

RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: bensternthal, Assigned: tpalmer)

Tracking

Details

(Reporter)

Description

5 years ago
This bug tracks completion of copy for content pages (everything outside the HP).

I suggest linking to a google doc of the copy rather than discussing in the comments.

It will be much easier to understand what is "Final" if its in a doc.

Comment 1

5 years ago
(In reply to Ben (:bensternthal) from comment #0)
> This bug tracks completion of copy for content pages (everything outside the
> HP).
> 
> I suggest linking to a google doc of the copy rather than discussing in the
> comments.
> 
> It will be much easier to understand what is "Final" if its in a doc.

Can you clarify what this is for? It doesn't sound familiar and I don't know what "HP" is. Thanks.
(Reporter)

Comment 2

5 years ago
Matej.. apologies it looks like you are the default assignee for bugs in this product / component and I did not notice until now.

This should be assigned to Troy... and it is now!
Assignee: Mnovak → troy

Comment 3

5 years ago
Ah, excellent. Much less confused now. I'll stay on CC in case anyone needs me to review anything. Thanks.

Comment 4

5 years ago
(In reply to Matej Novak [:matej] from comment #1)
> (In reply to Ben (:bensternthal) from comment #0)
> > This bug tracks completion of copy for content pages (everything outside the
> > HP).
> > 
> > I suggest linking to a google doc of the copy rather than discussing in the
> > comments.
> > 
> > It will be much easier to understand what is "Final" if its in a doc.
> 
> Can you clarify what this is for? It doesn't sound familiar and I don't know
> what "HP" is. Thanks.

HP = homepage. :)
(Reporter)

Updated

5 years ago
Depends on: 971804
(Reporter)

Updated

5 years ago
Depends on: 971806
(Reporter)

Updated

5 years ago
Depends on: 972480
(Reporter)

Updated

5 years ago
No longer depends on: 972480
(Reporter)

Comment 5

5 years ago
We have entered the content from the google doc into the production website. I am therefore resolving this bug.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED

Comment 6

5 years ago
A couple of general things to note:

Looking at the gdocs, there seems to be some inconsistencies in capitalization. Only main page headlines use Title Case. All other headings, subheads, etc. use Sentence case.

I also noticed reference to "OEMs" — we refer to them as "phone manufacturers." Please make sure that gets updated.

I'm not sure if we refer to "carriers" as well, but they should always be "operators" instead.

Thanks.

Comment 7

5 years ago
+1 for Matej's comments. Ben, will those updates be made, or should we file a separate bug?
(Reporter)

Comment 8

5 years ago
Best thing to do at this stage is to review the live site

http://mobilepartners.mozilla.org/

Copy from those docs was entered and some has already been updated with feedback from  stakeholders. 

I would suggest filing a bug per URL/page in this product/component with your changes.

https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=mobilepartners.mozilla.org

Matej I will email you credentials via email.

If the above does not work for you please let me know and we can figure out a different workflow.

Comment 9

5 years ago
I've started to go through the site and I'm finding a number of little typos and inconsistencies, which means I'm copying and pasting a lot of text to make revisions. It would really be a lot easier if I could edit the gdocs directly. Would that be possible?

Comment 10

5 years ago
(In reply to Matej Novak [:matej] from comment #9)
> I've started to go through the site and I'm finding a number of little typos
> and inconsistencies, which means I'm copying and pasting a lot of text to
> make revisions. It would really be a lot easier if I could edit the gdocs
> directly. Would that be possible?

I'm definitely up for making this easier.  The only issue is the copy in gdocs is probably not consistent with the website now, since we have all been making edits in the website since Tue.

If you want to create a new google doc, and just put in changes.  I can help update those changes on the website.  Would that possibly work?  I may not be fully understanding the workflow you are having to work with, so I'm open to suggestions...
(In reply to Patrick Hundal from comment #10)
> (In reply to Matej Novak [:matej] from comment #9)
> > I've started to go through the site and I'm finding a number of little typos
> > and inconsistencies, which means I'm copying and pasting a lot of text to
> > make revisions. It would really be a lot easier if I could edit the gdocs
> > directly. Would that be possible?
> 
> I'm definitely up for making this easier.  The only issue is the copy in
> gdocs is probably not consistent with the website now, since we have all
> been making edits in the website since Tue.
> 
> If you want to create a new google doc, and just put in changes.  I can help
> update those changes on the website.  Would that possibly work?  I may not
> be fully understanding the workflow you are having to work with, so I'm open
> to suggestions...

Yup, that works. I'll put all my revisions into a gdoc and send out the link. Thanks.

Comment 12

5 years ago
(In reply to Matej Novak [:matej] from comment #11)
> (In reply to Patrick Hundal from comment #10)
> > (In reply to Matej Novak [:matej] from comment #9)
> > > I've started to go through the site and I'm finding a number of little typos
> > > and inconsistencies, which means I'm copying and pasting a lot of text to
> > > make revisions. It would really be a lot easier if I could edit the gdocs
> > > directly. Would that be possible?
> > 
> > I'm definitely up for making this easier.  The only issue is the copy in
> > gdocs is probably not consistent with the website now, since we have all
> > been making edits in the website since Tue.
> > 
> > If you want to create a new google doc, and just put in changes.  I can help
> > update those changes on the website.  Would that possibly work?  I may not
> > be fully understanding the workflow you are having to work with, so I'm open
> > to suggestions...
> 
> Yup, that works. I'll put all my revisions into a gdoc and send out the
> link. Thanks.

Matej,

We're considering holding back launch this morning, and waiting for your copy.  Do you have an idea when you might get the bulk of it done?

Cheers,
Patrick
(In reply to Patrick Hundal from comment #12)
> (In reply to Matej Novak [:matej] from comment #11)
> > (In reply to Patrick Hundal from comment #10)
> > > (In reply to Matej Novak [:matej] from comment #9)
> > > > I've started to go through the site and I'm finding a number of little typos
> > > > and inconsistencies, which means I'm copying and pasting a lot of text to
> > > > make revisions. It would really be a lot easier if I could edit the gdocs
> > > > directly. Would that be possible?
> > > 
> > > I'm definitely up for making this easier.  The only issue is the copy in
> > > gdocs is probably not consistent with the website now, since we have all
> > > been making edits in the website since Tue.
> > > 
> > > If you want to create a new google doc, and just put in changes.  I can help
> > > update those changes on the website.  Would that possibly work?  I may not
> > > be fully understanding the workflow you are having to work with, so I'm open
> > > to suggestions...
> > 
> > Yup, that works. I'll put all my revisions into a gdoc and send out the
> > link. Thanks.
> 
> Matej,
> 
> We're considering holding back launch this morning, and waiting for your
> copy.  Do you have an idea when you might get the bulk of it done?
> 
> Cheers,
> Patrick

I'm working on it now and should be done in the next couple of hours. I just want to make sure I catch everything. I was looking at Troy's Additional Content gdoc and I there are some bits of copy there that I haven't seen on the site yet (like the Partner With Us section, for example). Is there somewhere else I should be looking?

Comment 14

5 years ago
(In reply to Matej Novak [:matej] from comment #13)
> I'm working on it now and should be done in the next couple of hours. I just
> want to make sure I catch everything. I was looking at Troy's Additional
> Content gdoc and I there are some bits of copy there that I haven't seen on
> the site yet (like the Partner With Us section, for example). Is there
> somewhere else I should be looking?

Partner with Us is seen only when you haven't registered.  So, click "sign out" in the upper right, and then click "market" on the first page.

Cheers,
Patrick
(In reply to Patrick Hundal from comment #14)
> (In reply to Matej Novak [:matej] from comment #13)
> > I'm working on it now and should be done in the next couple of hours. I just
> > want to make sure I catch everything. I was looking at Troy's Additional
> > Content gdoc and I there are some bits of copy there that I haven't seen on
> > the site yet (like the Partner With Us section, for example). Is there
> > somewhere else I should be looking?
> 
> Partner with Us is seen only when you haven't registered.  So, click "sign
> out" in the upper right, and then click "market" on the first page.

Thanks, got it. The only issue is that the copy on the site is different from what's in the gdoc. Which is correct?

Comment 16

5 years ago
(In reply to Matej Novak [:matej] from comment #15)
> Thanks, got it. The only issue is that the copy on the site is different
> from what's in the gdoc. Which is correct?

Troy's document was copied over to the site, and the site has since been updated.  So please consider the site as the canonical source at this point.
(In reply to Patrick Hundal from comment #16)
> (In reply to Matej Novak [:matej] from comment #15)
> > Thanks, got it. The only issue is that the copy on the site is different
> > from what's in the gdoc. Which is correct?
> 
> Troy's document was copied over to the site, and the site has since been
> updated.  So please consider the site as the canonical source at this point.

I just want to make extra sure about this one because the copy is totally different.

From Troy's doc:

Partner With Us
With Firefox, we changed browsing forever by putting users first and offering a new level of choice, innovation and trust online. Now we’re doing it all over again with Firefox OS.

By partnering with us, you’ll be helping to shape the future of the Web and offering the best mobile browsing experience for people everywhere.


On the site:

Partner With Us
As a brand, Firefox is a global leader in web recognition, trust and security. By partnering with us, you too can benefit from these great attributes.

We've made it very easy and straight forward to take the Open Source B2G operating system, and brand it 'Firefox OS'. Register below and build a Firefox OS phone.
(Reporter)

Comment 18

5 years ago
Can you add the google doc you are referencing to a comment here?
(In reply to Ben (:bensternthal) from comment #18)
> Can you add the google doc you are referencing to a comment here?

Sure thing: https://docs.google.com/a/mozilla.com/document/d/190C3k165MF9de2kC9FBZAuA1DdZ9XFpJYylInMcLt1w/edit

Comment 20

5 years ago
I'm worried we may have had a mixup at the hospital, and took home the wrong baby...
(Reporter)

Comment 21

5 years ago
Ah ok.

I have not seen this doc.

There are a few "special" pages that are not editable in the CMS. For example the /market page which displays different copy depending on the users login state. On these pages the content is coded into the template.

I can update these template(s) with the copy from this doc.
(In reply to Ben (:bensternthal) from comment #21)
> Ah ok.
> 
> I have not seen this doc.
> 
> There are a few "special" pages that are not editable in the CMS. For
> example the /market page which displays different copy depending on the
> users login state. On these pages the content is coded into the template.
> 
> I can update these template(s) with the copy from this doc.

Sounds good. Just let me know which copy I need to look at in the doc vs. on the site.

If it's just "Partner with us" and "Register," then it's good to go.
(Reporter)

Comment 23

5 years ago
Correct just these two.

For register we had some copy provided by legal. I will be able to merge these two without issue.
(In reply to Ben (:bensternthal) from comment #23)
> Correct just these two.
> 
> For register we had some copy provided by legal. I will be able to merge
> these two without issue.

Perfect.

Here's my doc with the rest of the edits: https://docs.google.com/a/mozilla.com/document/d/1Aip7Br4UJU3bPHGR51rDvTh7ZXwXsoP3fTQLfAsdMpk/edit

I tried to indicate what I changed in each instance, but probably best to just copy and paste as you go to be sure you catch everything. If it's not in the doc, it's fine as is.

One thing that stood out was this email address: fxos-cert@mozilla.org

It's mozilla.org rather than mozilla.com — just want to make sure that's correct.

Please let me know if you have any questions about anything.

Thanks.
(Reporter)

Comment 25

5 years ago
I updated /market in a pending PR. Note I thought I could merge registration copy but it does not mesh well with what came through from legal. For now I recommend keeping what we have currently - this was approved by Jishnu yesterday and the copy from troy does not explicitly state what we do with the collected information.

Patrick - I would be happy to make the changes suggested by Matej in this document or we can split them up. Let's co-ordinate in IRC.
(In reply to Ben (:bensternthal) from comment #25)
> I updated /market in a pending PR. Note I thought I could merge registration
> copy but it does not mesh well with what came through from legal. For now I
> recommend keeping what we have currently - this was approved by Jishnu
> yesterday and the copy from troy does not explicitly state what we do with
> the collected information.

Are you only referring to the Register copy? Can we use the Partner with us copy that Troy provided?
(Reporter)

Comment 27

5 years ago
Correct.

Partner with us copy has been added to that page and is pending a code merge.

https://github.com/mozilla/fxoss/pull/113

Comment 28

5 years ago
Matej - insane amount of detail caught here.  THANK YOU for spending time on this...

Ben - updates have been made.  We're good from my end.
You need to log in before you can comment on or make changes to this bug.