Need a logo!

[Kikobeats]

I was checking nodejs logo issue that have very nice ideas from the community.

Why not create a logo that identify async library? 💪

[aearly]

It's hard to say, async is such an abstract concept.

Through years of exposure, I've come to subconsciously associate async with @caolan 's face. 😄

[jdalton]

Async started as a branch of Underscore. And both Underscore and Lodash have _ in their logos:

Maybe Async could be an ellipsis …

[aearly]

I think of something like a sequence diagram. Maybe this could be stylized more:

[Kikobeats]

Please artists contributors check this :-)

[crispen-smith]

Didn't we all agree (I mean the community at large) that logos are basically the worst type of bike shedding? It's Asynch, it does exactly what it says on the tin and it does it well. Does it need a logo to represent that?

If it really does, then a nice jpg of the name set in Helvetica is probably sufficient, maybe underscore it.

[aearly]

I liked the old iojs logo thread strategy last year. Just create a thread with a bajillion logo ideas, and see which one ends up printed on the most stickers.

[olizilla]

https://github.com/substack/hex-grid/blob/master/example/images/async.png

[jjhesk]

[jjhesk]

some more ideas.

[bOvOd]

why not something like

>|

because you can straighten your callbacks with async, you could visualize nested callbacks > and your straightened ones |. If you like, you can also interpret it as "going simple".

[ivanseidel]

I did some sketches.. Is it something like this?

[Kikobeats]

@ivanseidel awesome

[megawac]

Sweet, I really like the 3rd one

On Sat, Jun 18, 2016 at 6:49 AM, Kiko Beats notifications@github.com
wrote:

@ivanseidel https://github.com/ivanseidel awesome

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#975 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ADUIEJiZxUlEQFCnlLTB6ahrUIs0vkKHks5qM80dgaJpZM4G0Xfy
.

[ivanseidel]

Thanks! If you guys like it, I can work on improving the 3rd a bit more

[Gorzas]

Great logos @ivanseidel. I prefer the third one, it's great :D

[aearly]

The 3rd one is great. I also like the first square logo -- would be good for a favicon or other smaller logo.

The only critique I have is that the "a" looks a bit weird. The perfect circle looks odd compared to the square shape.

[piranna]

Third one for me too :-D

The only critique I have is that the "a" looks a bit weird. The perfect circle looks odd compared to the square shape.

Yes, maybe better replace the circle in the a with a semicicle, so it could mimic better conditional if as they are shown in flowcharts :-)

[ivanseidel]

A few A's options...

[piranna]

I was thinking about 2D with an open or closed horizontal termination, similat to the ones of 3A and 3B.

[aearly]

I like 2A and 2C the best. What does the logo look like at smaller sizes? Might need thicker lines when it is smaller.

[megawac]

I think 2a/2b with 3c's gap would look great. Otherwise I like 2b-2d.

[ivanseidel]

So, here is the final version (I took 2A as "a" by some sort of voting from the comments).

About the Icon, depending on the size (for generating an Favicon), we can tick the line a bit more of the outer-box, that shouldn't be a problem...

Should I change the README and also include the graphics in EPS in the github so that everyone can use/modify it later?

[megawac]

Should I change the README?

Yeah, send a pull request adding the logo and icons. put them in a /logo folder

and also include the graphics in EPS in the github so that everyone can use/modify it later?

How big is the EPS? might make sense to keep separate depending on size

[piranna]

How big is the EPS? might make sense to keep separate depending on size

It would be just enough by adding it to the .npmignore file, so they don't get uploaded to npm repository (nor downloaded when doing npm install afterwards...)..

[ivanseidel]

• Put both .AI in /logo.
• Add logo to the Readme
• Add .npmignore to /logo folder/files
• Generate Favicon for the site ( static doc site generation #1202 )
• Be happy

[ivanseidel]

There we go: ivanseidel/async

If all is ok, I will swap the readme header url to caolan. @piranna @megawac

[megawac]

Looks good to me, send a pull request and lets be happy

[ivanseidel]

@megawac Everything is just fine to merge: #1203