Skip to content

Discussion: evolving the JAMstack branding design #292

@philhawksworth

Description

@philhawksworth

When the team at Netlify first created the branding for the jamstack.org site, its needs were rather different. In the time since then, jamstack has grown to include:

  • Dozens of community meetup groups
  • JAMstack Conferences
  • Adoption into the parlance of many services and organisations
  • References in technical writing
  • A community slack

...and much more.
As the category scales, so too should the identity.

This issue exists to:

  • Share the criteria and requirements for an updated logo and branding for JAMstack.
  • Share some of the design iterations and thinking
  • Invite feedback
  • Show the current work in progress

Logo mark requirements and considerations

  1. Logo artwork needs to be versatile, and hold up at a variety of sizes and applications (digital, print, embroidery, screen printing, etc)
  2. Logo color considerations:
    • Logo needs to work in flat color (no gradients or halftones)
    • Logo needs to have both a two-color version with a one-color alternate.
    • Logo should also support knockout applications (white logo on dark backgrounds)
  3. Logo needs to have both a jewel (think) and the wordmark (think the world "Apple").
  4. Logo needs to be designed to allow for three variations when considering the jewel of the logo and the wordmark of the logo:
    • Jewel to the left, wordmark to the right (horizontal version)
    • Jewel centered above the wordmark (vertical version)
    • Jewel alone, independent of the wordmark (simple "favicon" version)
  5. Jewel of the logo should allude in some manner to a stack of three components
  6. Logo needs to be vector shapes only, to support SVG format for web / digital and EPS format for print applications.
  7. Logo should feel modern, as JAMstack is a modern approach to building web applications
  8. Logo should feel at home alongside jamstack ecosystem logos as well as logos for enterprise services like AWS.
  9. Logo shape should not be confusingly similar to other logos in the general ecosystem
  10. Logo colors should be fairly unique in the space. (In our ecosystem research, blues, greens, purples, and reds seemed to be the most widely used among ecosystem partners.)

Metadata

Metadata

Labels

discussionA request for input from the community

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions