Engagement/Brand and Identity Guide: Difference between revisions

Jump to navigation Jump to search
removed
(added copy)
(removed)
Line 84: Line 84:


=== Initiative Wordmark Lockup Examples ===
=== Initiative Wordmark Lockup Examples ===
== When to Build a Website (And What To Do in the Meantime) ==
As illustrated in the brand assets table above, the guideline is against building standalone websites or dedicated URLs on Mozilla’s domains for a project until it reaches the Initiative stage. If you have a specific need for a website, especially something like standing up a webapp that is required for community members to participate or contribute to your project (or a technical issue like that), then that absolutely makes sense. If you think yours is in that bucket or has another really good reason, reach out to us.
At early stages, projects are prone to pivot strategies, or just be discontinued. It’s also a time when we want to encourage closer branding with Mozilla. Even early stage Experiments will have access to blog about their progress, set up wiki pages, and use many of the same resources as mature Initiatives. The recommendation is to leverage those resources until the technology, community, value propositions, and messaging strategy around it have matured to the point that a dedicated URL and website have a clearly definable and justifiable purpose.
Once you’re at that point and you’re ready to build a site, there are several ways to do it. You may work with the marketing team directly, or maybe an outside vendor will be involved (which we're happy to help you find - we have a list of trusted partners). In any case, when you’re ready to tackle it, the marketing team is willing to help you understand your options and point you in the right direction. Just drop us a line: marketing-request@mozilla.com.


== FAQ ==
== FAQ ==
90

edits

Navigation menu