My name is Chrissie Brodigan, I work on website strategy, design, and implementation for mozilla.org and mozilla.org/firefox. As part of Mozilla's Creative Team, I report to John Slater and am based in San Francisco.

If you're looking to fire up a new website or blog, or maybe merge some of your older content into mozilla.org, I would love to help you.

I also lead the Creative part of the One Mozilla website project

List of Services I Provide . . .

• Launch campaigns & editorial content for you on mozilla.org
• Build a website for your product, project, or team on mozilla.org
  • Information architecture
  • Content strategy/user experience
  • Competitive analysis
  • SEO
• Update content/design on mozilla.org/mozilla.org/firefox
• Create a new blog on blog.mozilla.com/blog.mozilla.org
• Conduct user research before launching a campaign
• Design user experience & flows that inform how you design your site

Build a New Website

File a bug under "websites" component "mozilla.org" and assign it to me (cbrodigan@mozilla.com).

Include the following information:

• Goal - what you want to accomplish (e.g. I want to launch a new product on mozilla.org or I want to create a blog for my team)
• Deadline - where you need this project to launch
• Requirements - things that you known you require to make your project successful (e.g. L10N, must have the download Firefox button or another download button)
• Inspirations - list of URLs for websites or projects that inspire you or convey similar goals/tactics that you would like to model

I'll work with on that bug to achieve a few things:

• Information architecture - where your content will best fit in on mozilla.org
• Define other creative needs and help you file bugs to get copy, graphics and other branded assets
• Project manage implementation - the flow of getting your design and copy coded

Update an Existing Website

File a bug under "websites" component "mozilla.org" and assign it to me (cbrodigan@mozilla.com).

Include the following information:

• Goal - what you want to accomplish (e.g. I want to launch a new product on mozilla.org or I want to create a blog for my team)
• Deadline - where you need this project to launch
• Requirements - things that you known you require to make your project successful (e.g. L10N)

Merge a site into mozilla.org

File a bug under "websites" component "mozilla.org" and assign it to me (cbrodigan@mozilla.com).

• Goal - what you want to accomplish (e.g. I want to move my project from an external domain or internal sub-domain onto mozilla.org - be sure to include the link to your site)
• Deadline - where you need this project to launch
• Requirements - things that you known you require to make your project successful (e.g. L10N)

Start a Blog

File a bug under "websites" component "blog.mozilla.org" and assign it to me (cbrodigan@mozilla.com).

Include the following information:

• Goal - tell me a little bit about the blog you want to launch (e.g. My team "Market Insights" would like to launch a new blog)
• Deadline - where you need this blog to launch
• Requirements - things that you known you require to make your blog successful (e.g. must be easily translated into multiple languages, must use X plugin to achieve y)

Information Architecture

When launching a new website, I'll work with you to determine a URL as well as the ways in which users will discover your content (e.g. item in Tabzilla, organic search, a static link from the home page of mozilla.org)

Tools:

• Domain Name Strategy
  • If you are developing a property that is a discreet application (e.g. Mozillians, AMO, SUMO), then we'll launch you on a sub-domain like yoursite.mozilla.org
  • If you are launching a property that is a set of static web pages, then we'll launch you on inside of a cozy sub-directory like mozilla.org/yoursite

User Research

Before Launch

• Analyze competition, especially around keywords that you would like your content to "own"
• Define who your users are (e.g. developers, general users, academics)
• Determine how to best get your content to the right audience
• Define success metrics (e.g. # of downloads, # of page views)

After Launch

• Review metrics, how is your content performing?
• Review search experience & traffic patterns, how does your content look in Google? is there a high dropoff rate?
• Create & launch a survey (Lforrest is the go-to person for this on /firefox, I can help on mozilla.org)
• Create & launch A/B testing (Lforrest is the go-to person for this on /firefox, I can help on mozilla.org)

User Experience/User Flow Design

Before Launch

• Create visual flow diagrams that map how users will accomplish the task at hand (e.g. download Firefox)
• Create use cases that detail the reasons users show up and what they are each looking for
• Set goals for your website that we can track with analytics & surveys

Post-Launch

• Audit flows & run user testing (we currently do this in a few ways: usertesting.com, eye-tracking, and surveys)
• Review success metrics
• Iterate on the flows and design (fix what isn't working)