Extensions

For projects that aren't part of the core GitHub platform or product, we use extensions to signal our involvement.

Extensions

When a design is neither a GitHub product (revenue generating, involves logging in, has a private repo, etc.) nor a part of the GitHub core identity, the design is considered an extension of our core brand. This includes, but is not limited to, open source projects and GitHub events.

For these projects there is only one rule. The footer must include the phrase:

[verb] with <3 by GitHub, Inc.

For example:

Built and tested with <3 by GitHub, Inc.
Presented with <3 by GitHub, Inc.
Sponsored with <3 by GitHub, Inc.

Typically it’d look something like this:

Beyond this, the design should have its own personality. Boxen, git-scm.com, and Hubot are great examples.

Why do this?

We shouldn‘t beat people over the head with our brand. Our brand, our ethic, should be conveyed through how we handle things. It should be subtle.

Open source projects belong to the community, not to GitHub. We may be shepherds of the project, but by the nature of open source, they should be able to stand on their own without us. Having the single reference to GitHub in the footer says “This project is maintained by GitHub, but it’s yours to enjoy.”

The same goes for events. Events provided by or sponsored by GitHub are about the people, not about GitHub. Our identity should take a backseat to the identity of the event, unless it is specifically targeted at promoting the company.

Domains

When these designs live as GitHub Pages sites, the url should follow the typical Pages convention: project-name.github.com. This allows us to not worry about getting special domains for these projects. It also means we won’t be buying hundreds of domain names for one-off events.