Closed
Bug 785187
Opened 14 years ago
Closed 14 years ago
Developer Portal - Design and branding
Categories
(Marketplace Graveyard :: Developer Pages, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: smartell, Assigned: smartell)
References
Details
(Whiteboard: [devhub-v1])
Before launch, Creative needs to review the design and branding on these pages to confirm they are in-line with our style and current brand artwork for Marketplace.
Some things we can address right away are the unofficial wordmark being updated to its final form. I'll add a link to the file once completed.
Comment 1•14 years ago
|
||
Thanks for filing this, Sean. This early alpha version of the Developer Hub is inheriting its branding from the main Marketplace code.
I'm happy to change the logo. When do you expect to be able to provide it? We need some rudimentary branding for next Thursday's release. Thanks!
Assignee: nobody → smartell
Comment 2•14 years ago
|
||
Pushes happen on Thursdays at 2. Any changes need to be done well before that. (New design is scheduled for Aug 30th at 2pm)
| Assignee | ||
Comment 3•14 years ago
|
||
I'll supply the wordmark today. This will be called Firefox Marketplace and will use the same branding as the Marketplace itself, so we'll need to call out Developers within the content, not the branding. We're not going to make a subbrand for devs here.
| Assignee | ||
Comment 4•14 years ago
|
||
Looking at the site, can we delay this launch? Who do we have to talk to about that?
There are many concerns with this site and I think we need to address them. examples:
- wordmark and calling out developers in the main content, not the branding
- inconsistency with pages https://marketplace-dev.allizom.org/developers/docs/devtools vs. https://marketplace-dev.allizom.org/developers/docs
- not loving everything in boxes for a site like this. boxes were in the Marketplace style, but that has changed (shorlander revamped the look and feel) and this is a documentation site, not a marketplace
- it is not responsive / responsiveness is broken.
Comment 5•14 years ago
|
||
You'll want to speak to @clouserw, but this is only an internal milestone, nothing public is happening with this push so there's plenty of time to fix this up.
Comment 6•14 years ago
|
||
Andy is correct, the release is an internal milestone and is understood as such from a product standpoint. I'll still happily apply your wordmark, and work with you on visual design in the next iteration.
| Assignee | ||
Comment 7•14 years ago
|
||
Awesome. Thanks folks. I'll look into how we can play around with the layout/design a bit.
| Assignee | ||
Comment 8•14 years ago
|
||
Curious, if we're making https://marketplace-dev.allizom.org/developers/, what are we doing with https://developer.mozilla.org/en-US/apps
Do we even need this new site, or can we just expand on the MDN page?
There is also http://www.mozilla.org/en-US/apps/partners/.
Should we not possibly combine all of these onto http://www.mozilla.org/en-US/apps/?
Comment 9•14 years ago
|
||
(In reply to Sean Martell from comment #8)
> Curious, if we're making https://marketplace-dev.allizom.org/developers/,
> what are we doing with https://developer.mozilla.org/en-US/apps
The developer hub and MDN are offering different value to the users: the devhub is a marketplace-oriented, relatively tightly scoped "one stop shop" for apps developers, while MDN is a vast knowledge base. We're working on establishing an information architecture that reflects this better.
> There is also http://www.mozilla.org/en-US/apps/partners/.
>
> Should we not possibly combine all of these onto
> http://www.mozilla.org/en-US/apps/?
I don't think that'd be good from a branding perspective: If the marketplace is separate (and Firefox-branded), then the developer piece for that marketplace should not live under mozilla.org. It'd make much more sense for mozorg/apps to forward to the marketplace instead.
Comment 10•14 years ago
|
||
We received updated branding, closing this for now. Let's reopen individual bugs as the need arises. Thanks!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•