Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Brand Guidelines: Updates #38

Open
Ruv7 opened this issue Nov 28, 2016 · 8 comments
Open

Brand Guidelines: Updates #38

Ruv7 opened this issue Nov 28, 2016 · 8 comments

Comments

@Ruv7
Copy link

Ruv7 commented Nov 28, 2016

We have announced the brand guidelines in our newsletter and posted within the repo. Let's work on documenting and implementing those pending updates so that we can get this to the next level.

Flagging this for: @faricacarroll @spoorthyv @cameronoelsen @ellisonbg - Farica and or Spoo - can you take the lead on this?

ps. for reference here is the writeup in the newsletter: https://newsletter.jupyter.org/jupyter-newsletter-9-november-22-2016-80b9e4db1f3e#.mmz3v48er

@faricacarroll
Copy link
Contributor

These are some of the suggestions I noted down from the Team Meeting.

  1. Creating a square logo for Powered by Jupyter
  2. Including a file icon in the Brand Book
    • Spoo made some preliminary designs. He still needs to make a more formal proposal on GitHub. He is not sure if the brand-book is an appropriate place for this.
  3. Adding Pantone colors for print in brand book
  4. Including cm/in for print in logo sizes
  5. X and Y relationship in logo proportions
    • Put everything in terms of X instead of using 2 variable
  6. Changing contact email address to google groups
  7. Creating a variant logo that powers Jupyter Kernel
    • Start by making a version for the R kernel since they are already using a version of this that violates the brand guidelines
  8. Make a theme for NB for presentation
    • As a side project, not necessarily incorporated into brand book

@Ruv7
Copy link
Author

Ruv7 commented Nov 28, 2016

Great, thanks for documenting this! If anyone has anything else to add for suggesting additions/revisions feel free to respond in this thread.

@Ruv7
Copy link
Author

Ruv7 commented Dec 2, 2016

Notes from design meeting held today:

  • item 1 is done, we need to add to the guidelines, Farica to add
  • item 2 - beyond scope of brand guidelines which are by design more universal/generic
  • item 3 - Farica to take on
  • item 4 - Farica to take on
  • item 5 - Spoo to take on
  • item 6 - Spoo to update
  • item 7 - Cameron to reach out to Thomas RE: - https://irkernel.github.io/
  • item 8 - good idea, outside of the scope of the brand guidelines, we will pursue that outside of this project

@cameronoelsen
Copy link
Contributor

Just reached out to Thomas and am now waiting for a response regarding the IRKernel website.

@spoorthyv
Copy link
Contributor

Can someone implement item 5 and 6 for me? The brand guideline keeps crashing my adobe illustrator for some reason so I can't edit the file. Here is a mockup of item 5
group 3

I just changed the main variable from X to H and switched the Y to 1/15H.

Also for item 6 can someone change the email address to [email protected]?

@cameronoelsen
Copy link
Contributor

item 7 PR is in and waiting to be merged - IRkernel/irkernel.github.io#36

@spoorthyv I will make those changes for you!

@cameronoelsen
Copy link
Contributor

5.) and 6.) are fixed in Pull Request #40

@flying-sheep
Copy link

hi @cameronoelsen, thanks for the PR! good idea simplifying the site layout, too.

about item 7: i wanted to look this up, but you don’t specify anywhere what your actual guidelines are. what kind of deriviate logo would be OK? what parts of the logo can be used, how may we use the jupyter logo’s visual language for a own logo?

furthermore the “powered by” badge explains where it is to be used. this description (and therefore the badge) doesn’t apply to language kernels (like IRkernel), for reasons discussed here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants