Closed
Bug 965087
Opened 12 years ago
Closed 12 years ago
Better Titles For 3 Main Pages
Categories
(Marketing :: Copy, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bensternthal, Assigned: matej)
References
Details
Attachments
(2 files)
There are 3 main pages linked to from the HP and presumably will be the main navigation.
Note these in the sitemap: https://mozilla.box.com/s/9m11br0zb2pi09z6x0v5
1.0 I want to know more about FFOS Features and Roadmap
2.0 I Want To Build A Device
3.0 I Want To Build A Branded Device
These names are not very nav friendly and would like help coming up with what we should use. Patrick can advise / answer additional questions you may have.
Comment 1•12 years ago
|
||
I have a few ideas.
1) In the overview copy on the homepage, link the "I want to know more about FFOS Features and Roadmap" links and sub-links from the overview copy instead of just making it a link with nothing else. Then make the "Build a Device" and "Build a Branded Device" as two main CTA boxes. I will attach a screenshot of what Microsoft is doing for their OEM website that has yet to be released.
====
2) Since three nav items is few, we could add few key sub-links in each hierarchy to get that content one click from the homepage. This is similar to what developer.mozilla.org does on their homepage.
About Firefox OS Build a Device Build a Branded Device
================ ============== ======================
sub link 1 sub link 1 sub link 1
sub link 2 sub link 2 sub link 2
... ... ...
====
Comment 2•12 years ago
|
||
Comment 3•12 years ago
|
||
(In reply to Chris More [:cmore] from comment #2)
> Created attachment 8367398 [details]
> Microsoft OEM website screenshot
We could do "Learn", "Build", "Brand"... Or something of this nature. The titles we have now I'm not married to.
Comment 4•12 years ago
|
||
(In reply to Patrick Hundal from comment #3)
> (In reply to Chris More [:cmore] from comment #2)
> > Created attachment 8367398 [details]
> > Microsoft OEM website screenshot
>
> We could do "Learn", "Build", "Brand"... Or something of this nature. The
> titles we have now I'm not married to.
I like that!
Comment 5•12 years ago
|
||
Then it's done.
Assignee | ||
Comment 6•12 years ago
|
||
I love it when I don't have to do anything in a bug.
Nice work!
Can we resolve?
Comment 7•12 years ago
|
||
(In reply to Matej Novak [:matej] from comment #6)
> I love it when I don't have to do anything in a bug.
>
> Nice work!
>
> Can we resolve?
Matej, if you are also blessing this, then I think we can resolve. ;)
Assignee | ||
Comment 8•12 years ago
|
||
"Brand" may be a little misleading since it may sound like you're branding something. WDYT?
Comment 9•12 years ago
|
||
If we make the 3 items on the homepage more CTAs than just nav items, we could have a bit of text below the "brand", "build", "learn" than just the text itself.
Comment 10•12 years ago
|
||
(In reply to Matej Novak [:matej] from comment #8)
> "Brand" may be a little misleading since it may sound like you're branding
> something. WDYT?
Brand will be about branding guidelines, getting access to logos and other assets, as well as getting licensed and certified to brand a device with "firefox OS". So in that sense they are "branding" a phone with "firefox os". Is this what you are asking?
Comment 11•12 years ago
|
||
(In reply to Chris More [:cmore] from comment #9)
> If we make the 3 items on the homepage more CTAs than just nav items, we
> could have a bit of text below the "brand", "build", "learn" than just the
> text itself.
See the posted image of the webpage copy I'm working on. Falls right in line with this suggestion (based on the OEM site posted)
Comment 12•12 years ago
|
||
Assignee | ||
Comment 13•12 years ago
|
||
Thanks for the clarification. That makes sense to me.
Comment 14•12 years ago
|
||
I just uploaded a wire frame to bug 964966 where we are tracking the design of the homepage. I will close out this bug since we agree on the names for the 3 main content areas.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•