@ellisonbg @tgeorgeux Some of the things in here seem outdated/no longer in use. Can we make it clear what's old and what's current by having an archive folder? For example, the Galileo folder looks like it's older branding.

As SciPy / PEARC / JupyterCon are coming up, I wonder if anybody has a stash of stickers sitting around. Anybody know of some?

I've been working on updating our twitter page. Specifically the profile picture and banner image. Let me know if you have any issues and opinions.

@Ruv7

Profile Picture:

Banner Image:

Preview:

Current Twitter:

the new logo since 2015 can be found here: https://www.r-project.org/logo/

So I made a few different designs for the JupyterDay logo and narrowed it down to these two. I really like the first logo more-so than the second because of the reference to a pin (location). The second logo was more focused on the content of the event. I would love feedback on which is your favorite!

I am currently working to standardize how Jupyter's colors look when printed, starting with Jupyter orange. To do this, I have been measuring CIE-Lab values of previously printed materials, looking at how CMYK values can be calculated from the existing RGB (243,118,38) and hex code (#F37626) values, and purchasing Pantone's Color Bridge reference books to ensure accuracy.

Mathematically, C0 M53 Y85 K3 seems like the best conversion, but @ellisonbg and I have been leaning away from this because it seems a bit light and dull. Adobe products convert Jupyter orange to C0 M67 Y97 K0. The closest Pantone color, 158C, converts to C0 M62 Y95 K0. The Adobe and Pantone colors are very close to each other, and the final decision will probably be in that ballpark. We are waiting to make a final decision until we have the Color Bridge book, and can do some more comparisons on different types of printers.

This is an issue to track ongoing work by the designers at Cal Poly to create a visual brand guide that documents the visual design and usage aspects of our logo in software, print media, websites, etc. I will let the teams add information about what they are doing.

@jupyter/designers

I'm not the one saying it:

https://medium.com/@erikdkennedy/7-rules-for-creating-gorgeous-ui-part-2-430de537ba96

I thought it might be interesting for @awantulok :-)

(cf screenshot for posterity, red emphasis mine)

@cameronoelsen is going to start working on the design of stickers for SciPy.

Cf ipython/ipython#6856, Quantopian have made some custom design and we might want to get some things from what they are doing and they would be happy to help.

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

Hi all,

I'm aware you are working in a new theme as of #10 and I think it looks great, but you are not (at least from what I read) giving the user the possibility of choosing a specific syntax highlighting. Most IDE let the user choose from a variety of them.

I think both things should be separated, as some user might not want to change the appearance of the notebook but only the highlighting.

As in my university, teachers wanted to have a different syntax highlighting for the code so it could be easily disguised from text for those who are learning to code with Jupyter. I already created a plugin to do this, but it would be great to be integrated in the default package.

What do you think about this ?

The issue from @jasongrout here: https://github.com/jupyter/trademark/issues/7 got me thinking that this is quite a common pattern that I've seen. It goes something like:

• Jupyter is inherently modular and extendible
• So people extend it to new kernels/use-cases/etc
• They want a logo for their project
• So they slightly modify the Jupyter logo to adapt it to their project-specific setup

In this case it was combining the Rust logo w/ the Jupyter logo, but I've seen it with domain-specific things, color changes, etc.

Since Jupyter is itself designed to be extensible, I think it would be valuable to the community if there were guidelines for how people could gracefully (and without violating Jupyter's trademarks) build on top of Jupyter design assets for their own logos and such. For example - what if somebody designs a new language-specific kernel and they'd like to make a logo for it. It would be nice if there a repeatable pattern they could follow to generate this logo (e.g. the Jupyter logo + a designated space where a new logo would go).

This is beyond my personal design skills, but I wanted to flag it as a thing to think about. How could Jupyter take its philosophy towards infrastructure, and also apply it to design?

Beginning inspiration and mock-ups for JupyterHub sign in page:
(Screenshots)




(Balsamiq Wireframe)

(Beginning Antetype Wireframe)

In the Jupyter Notebook meeting today, we reviewed jupyter/notebook #5998 and found that

• one of the most compelling arguments for changing fonts is to create consistency across Jupyter projects
• there is not currently a consistent/singular/otherwise agreed upon approach for this across projects
• this PR is also linked to another PR asking to change fonts on JupyterLab

There seems to be a history of changing these fonts back and forth in some projects, so @afshin suggested that we agree on something and have a place to point people as to why the choice has been made to prevent changing this regularly in the future. Once a choice is made, I think it is worth adding a file to the repo to start tracking this and similar Jupyter-wide design choices.

I'm not very familiar with this problem and who at different projects might care about this, so I'd appreciate any help in getting those people involved.

I had a discussion with @ellisonbg about diagram design the other day and he suggested we come up with a unified technical diagram style, and that we ask @cameronoelsen to investigate for us. This discussion serves that purpose.

Next week, @Carreau @takluyver and I will be giving a talk at SciPy. I've chosen a simple diagram to start the discussion. Eventually I'd like to be able to animate the diagrams, but I don't think that's absolutely required right now.

Summary of needs:

• Consistent diagram styling scheme (colors, shapes, lines, widths, fonts, etc).
• Animated diagrams

Example diagram:

It's important to state, the lines, shapes, and positioning I use in my sketch above can all be changed. Also the text "send" and "receive" can be omitted if it's clearer.

Here is where all of the progress on the new Jupyter site will be held! There are now two separate threads for IPy and Jupyter.

[edit by Matthias]

https://jupyter.hackpad.com/Jupyter-Content-and-Organization-Gg50rKW9YW7
[/edit]

After checking out out the dockarea demo online (http://phosphorjs.github.io/dockarea-demo/) and talking with @ellisonbg about the where the notebook will be heading, I have mocked up an option on what the new notebook may potentially look like. I have taken some cues from material design, but have strayed away for areas where we need more complex content. Will continue to iterate based on feedback!

Not the end of the world, but seems less than ideal.

@karino has said that he'd be open to someone designing a logo for his Android notebook frontend interface, if anyone has time and is interested in working on this.

https://github.com/karino2/NotebookFrontend

(I've asked him to change the logo as the current one combines the Jupyter logo with the Android one, which IIRC is against our guidelines)

I was running 'report_dashboard.ipynb' on cell 4: %load_ext jupyter_cms throws an error:

ImportError: No module named 'jupyter_cms'

I am using conda version 4, python 3.4 on windows 8.1 64-bit.
Also, conda install jupyter_cms throws an error:

package missing in current win-64 channel

This time on brand color/design:

• http://www.entrepreneur.com/article/233843

Hi all. Similar to the conversation going on in #6, I spent a small amount of time thinking about the design and layout of notebooks and thought I'd share a little bit of my work in progress.

I wanted to reduce some of the boxes, slim up the header space to bring the content up on the page, and make the Input and Output feel a bit more like an editor and be full-width/responsive.

Feedback welcome

I can roughly do that, but it's not awesome.

  O ___ º
   /   \
  JUPYTER
 o \___/

Currently, there are tons of Jupyter logos across multiple subprojects that are all slightly different from each other. The plan right now is to consolidate all of these and create one logo for everything.

The first picture shows versions of the Jupyter logo that are actually in use right now

• A/E are the original logo
• B is the logo found on the website's header
• Everything else is found here and there throughout Jupyter

Currently there are 4 variables among the logos.

• Gradient vs No gradient (E is the only one with a gradient)
• Shade of orange (A is a lighter orange than B, C, and D)
• Size of moons (B's moons are larger than the rest)
• Color of moons (B and C have uniformly colored moons while A, D, and E have different colored moons)

The second photo shows all instances of Jupyter Logos actually being used in products right now. The last photo shows all versions of the logo I could find (including versions not being used anywhere).

What are everyone's thoughts and preferences? What parts of each logo do you like?

I am cross-linking this JupyterLab issue because those assets may ultimately end up in this repository.

cf. jupyterlab/jupyterlab#132

I like the "community call" logo that was done for the youtube videos. Who did that? And would you be willing to do the same for the Jupyter community forum? (basically just replace "community call" with "community forum"? @tgeorgeux was it you? :-)

I’m part of a group from UC Irvine, working on designing a new file browser experience. As part of this work, we’ve been doing a lot of research on the current state of JupyterLab.
While it’s mostly focused on the file browsing/managing experience, the heuristic evaluation we’ve completed could be of some use to the community, so we’re sharing it here.

At the moment, I’m linking to this as stored in my personal .github.io repo, for lack of a better place, but are hoping @tgeorgeux can help us get this stored somewhere more appropriate/permanent for use by the Jupyter community.

Here’s hoping this is helpful, and thank you for your time.

Oh, and for reference, the group consists of @jabumeri, @JDLEarley, @emilythefan, @Nastraughn, and myself.

The current brand guidelines are a PDF export of presumably a presentation, but we don't seem to have the presentation anywhere in an editable format.

I know we set up a different, non-GitHub workflow for designers to contribute, but I can't find documentation of it, or how folks are supposed to propose updates to the brand guidelines right now (#68).

I assume the logo’s font is Myriad Pro Regular, but this is stated nowhere

We are a group of graduate students studying HCI and Design at the University of California, Irvine, and we have partnered with Project Jupyter to help maximize the effectiveness of the jupyter.org website as part of our six-month capstone project. We are working directly with Tim George, Jupyter’s lead UI/UX designer, and have already begun some preliminary UX research.

We will be adding new files into this repository so that the community can keep up to date with our progress.

Hello all! At the Cal Poly hub we've been working on some branding decisions including updating brand guidelines and setting official print colors. In the process we're exploring adding in a palette of secondary colors to use with Jupyter Orange.

We'd love for anybody who's interested to be involved in the process with us. In the interest of productive work, there are a few constraints we will work within.

• The secondary colors need to compliment existing Jupyter Orange.
• We aren't working to change Jupyter Orange.
• We want to focus first on developing 3 colors: A light fill color, a dark fill color, and a color we can use for text on light backgrounds.

I'll update progress here as it's made:

• Scope secondary colors to a range that compliments Jupyter Orange
• Try multiple shades, RGB combinations, CMYK combinations, to find a set of 'color candidates' that would work with Jupyter Orange
• Of the selected colors play with Hue/Saturation/Lightness to find good matches that are easy on the eyes. Ideally a color candidate will be as close to the same base color with variation on lightness as possible. A good (good meaning works well with Jupyter Orange & White) candidate will have:
  • A good dark fill/accent color
  • A good light fill/accent color
  • A good 'text-on-light/white-background' color
• Members of the community should feel this is a good (or good enough) color.

Hey all - I was just chatting with @jzf2101 about how it'd be useful to have a business card to give to people when they wanna connect with the Jupyter community.

Do we have any business card templates that are easy for others to replicate? If not I can try to mock up and submit a PR

In developing our brand guide and trademark usage policies, it would be a good idea to understand all of the logo variations we already have. This would include:

• Color variations
• Moon sizes
• Gradient or not.
• Grey colors
• etc.

I am working to update the Jupyter brand guidelines. Here are some of the things, in no particular order, that I am looking at adding/changing:

• clearly summarize the how Jupyter logos can and can't be used, based on the trademark policy

• clarify when the typography specified in the guidelines should be used

• add square version of Powered by Jupyter logo to guidelines

• Add CMYK values to Jupyter colors

• Make collateral such as slide decks and business cards (both Jupyter-only and dual-logo) for community use and core contributor use

• update email on last slide of guidelines

Please let me know if there is anything specific I should consider about these or any other points. I have looked at closed issues on this repo to understand where current designs came from.

This repo has favicon files (lacking moons due to small display size), but they aren't mentioned in the brand guidelines. This means they can't easily be used according to our trademark policy.

I think we should mention the moonless favicon files in the guidelines and suggest using them for "small sizes" e.g. favicons or very small icons (I don't know if we want to go beyond subjective "very small" and suggest a specific display size, e.g. below 24px square).

In the past, we have been putting design assets on both:

1. A shared DropBox folder
2. This repo

The reason is that many of our designers haven't been git literate, and trying to diff/merge Illustrator files is really dangerous. The files in these two locations have fallen out of sync (they are completely different now) and the files are sort of a mess.

There are also a lot of "working" files, such as Illustrator and Sketch files that the designers use.

We need to organize and consolidate these assets.

Questions:

• Where to put all of our final design files?
• Where to put more of the working design files?
• Should we force everyone to use Git?

@jupyter/designers

@cameronoelsen is going to also design us Jupyter T-shirts!

Hello JupyterLab community! I am also part of a group from UC Irvine (we just recently dropped a Heuristic Evaluation and Competitive Analysis here) and as we continue with our research to design a new file browser experience, we we were hoping to gain some more input from the community.

To do that, our team has put together a survey to further understand the community's experience with JupyterLab. We believe the data collected from this survey will be very useful as we move forward in our research and design plans. Please take some time and complete it if you can; we would be very appreciative if you do!

https://forms.gle/1HAts3wNmmDk1JV38

Hey all - do we have any particular license for the Jupyter logo that's different from the codebase? I think we need to include this with the Binder blogpost. Maybe one of @ellisonbg @fperez would know?

Hey everyone!

Starting today, I am going to be shifting most of my focus to researching and designing the Jupyter Workbench's (name to be decided on) 1.0 initial release interface. @ellisonbg and I have started a Hackpad that outlines some common functionalities that we have seen users are accustomed to. Please feel free to add anything you might see to be a helpful feature/functionality to the end user for the initial release at https://jupyter.hackpad.com/Jupyter-Workbench-UIUX-m8yrTt4p5ZA. As I design the interface, it will be posted here for further discussion!

Hi!

A few changes or clarifications to the brand guidelines made it so the IRkernel logo (as well as a replacement by @cameronoelsen) don’t comply anymore:

But my programmer art really hits its limitations when i’m confronted with the task

Create a logo that adheres to the visual language of jupyter in a recognizable way without violating the brand guidelines

Would it be possible if you could help @takluyver, @JanSchulz and me out with a logo that fits those constraints?

As an inspiration: i really like the fact that the R logo fits the sidereus nuncius figure for jupiter that inspired the jupyter logo’s shells:

The branding guidelines available in the file brand_guide.pdf at

• https://github.com/jupyter/design/tree/main/brandguide

could be slightly improved:

• page 10, logo misuses:
  typo: obsured -> obscured
• page 11, condensed logo:
  vertical space above and below "jupyter" wordmark inside
  condensed logo should be labeled 1/15 H instead of H

See also: #38 #47 #54 #68 #69.

We have a "powered by" logo that needs to be added to the brand guidelines and this repo.

Over the last week, I have been doing a visual overhaul for both IPython and Jupyter. On the site I am sharing below, I simply took the content from the IPython site and did visual changes to make the site more modern. However, some of the content on the mockup provided is going to be moved over to the Jupyter site. The IPython site will be most likely less content heavy and more-so a direct to the Jupyter site once it is made. I have also allowed commenting on the mockup, so please feel free to provide feedback if you have any! The mockup is also very functional, so play around :) Cheers!

http://invis.io/KF3BRI8QU

This would be akin to what Python offers, and it would allow related projects to show that they use Jupyter in an essential manner, without trying to potentially create diluting logos.

What do folks think of this idea?