MozillaZine

Mozilla Branding and Visual Identity Proposal

Thursday October 23rd, 2003

Steven Garrity has written a proposal for the branding and visual identity of the Mozilla Foundation and its products. The document, which does not necessarily reflect current mozilla.org thinking, recommends dropping the red Mozilla dragon head, clairifying the names of the various products, bumping the version number up to 2.0 when the switch to standalone applications takes place and making the icons more consistent. The Mozilla branding strategy and the Mozilla trademark policy give some insights into the Mozilla Foundation's plans for the Mozilla brand but note that both documents are currently under review and are likely to change in the future.

Thanks to Slashdot for alerting us to Steven's proposal.


#19 Re: Interesting

by MarkHB

Friday October 24th, 2003 7:38 AM

You are replying to this message

Re: "How much quickly could the suite be churned out if development just *stopped* on the seamonkey suite and focused on the new components that are recommended in the suite?" I've heard this before, and two things about it strike me. First, unpaid developers work on what they wish, so there is no way to "command" that work shift to the birds from seamonkey. Second, I'd like to point out that some of us out here in userland prefer the all-in-one monolithic process over the Birdland separated apps (and in my case, I mean "prefer" at the conceptual level -- it's not that there are particular things I don't like about the birds, it's that I like having all the apps in one process space).

Re: "I definitely agree with the look and feel of the OS idea. As long as the core technology and rendering remains the same across the board and is completely cross platform, the user interface that delivers that to the user should be irrelevant to the actual browser program... which would mean that it *can* be changed to fit the needs of each OS." The whole raison d'etre of XUL is that there aren't enough programmers interested in maintaining platform-specific front ends to keep parity. Perhaps it could be possible to define default skins on a per-platform basis, but even those need committed maintainers.