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
Project logo #7
Comments
How about a sugar cube? |
@danielbayley nice :) But note that it is hard to draw white cube, so it will be clear that it is sugar cube :) |
Like the idea of the sugar cube. You can use brown sugar instead of white one to avoid this issue. |
White cube(s) can be on dark background
|
I actually like idea of simplistic smiling sugar cube:)
|
Some options:
But yeah if we can just appropriate that character from Adventure Time, that would be pretty good. |
Maybe we can make sugar cube more recognizable by some right texture. @corysimmons “SS” as animal face is awesome too :). |
@janmarek SugarSS is from CSS. Sugar Style Sheets. In Russia we are very obsessed about World War 2 (like a local religion), but I don’t hear any issues with this name. |
I didn't want to say anything in case I was just being crazy, but I agree with @janmarek It reads like Sugar-SS not like CSS. Can we just drop the SS completely and just call it Sugar? We can keep the Sorry, not trying to be hypersensitive, but it is kinda weird. |
Or something a little more abstract? I was messing around in Illustrator a little… ![1](https://cloud.githubusercontent.com/assets/7797479/13630148/9a215376-e5d5-11e5-98e7-0f63b11a894d.png) ![2](https://cloud.githubusercontent.com/assets/7797479/13630145/9a142110-e5d5-11e5-83b9-ebc537882fc0.png) ![3](https://cloud.githubusercontent.com/assets/7797479/13630146/9a190c52-e5d5-11e5-81e4-16e64e4550f2.png) ![4](https://cloud.githubusercontent.com/assets/7797479/13630149/9a230d74-e5d5-11e5-963f-700c4ac0cde7.png) ![5](https://cloud.githubusercontent.com/assets/7797479/13630147/9a1c0380-e5d5-11e5-9b04-c2404484be04.png) |
I think, you need use alchemical symbol of sugar :D |
I'm not keen on the 'Sugar StyleSheets' name as it removes 'Cascading', which is kinda an important/defining feature of (Post)CSS. Plus it would be better to avoid SS appearing alone for the obvious reason mentioned by others. PostCSS Sugar? That gives it context and doesn't remove anything.
...helps the medicine go down - from Mary Poppins. Maybe the snapping of fingers could be related to the nice and easy syntax? |
@pgrekovich I thought of that, but left it out of my list because 1. there are often multiple symbols different people used in alchemy to mean the same thing (i.e. no consensus) and 2. no one would actually recognize it, but the first result in google images does resemble two esses. (However, it also looks kinda like an H, so it wouldn't be great for readability if incorporated into the logo. (SugarH?)) Edit: but you could do a custom variation of it that could be a lot better for readability |
@corysimmons I am OK with calling it Sugar syntax. |
@danielbayley nice patterns. But I think that we should always try to find emotional background. Anyway we can use it if we will not find some better way. |
@pgrekovich @1j01 alchemy always will be better. But I really love “sugar” and “happy” thinks. Maybe we can combine alchemy and candy style in that Adventure Time way? This cartoon has persons, which looks nice, good and sweet from outside, but have dark background inside. Like Peppermint Butler. For example, if we put a smile on every edge of sugar cube it will be very “alchemy”. |
@ai Can you rename the repo to |
Sorry, photo is bad source for logo |
@corysimmons first proposal looks good |
The first option with the spoon is very nice, I don't know if you're intention was to put the sugar cube inside or to make it levitate, I would prefer the former as there would be a little magic in here. |
Yep, the levitating was intentional! |
@natemoo-re awesome work! I prefer the first option with spoon, because it is easy to understand that it is a sugar. Second and third options are great in colors and geometry, but looks too abstract. Abstract thing is awesome (Malevich!), but open source projects use abrsact logos too often. So especially in open source, I think, we should avoid a abstract things. The only thing with a first option (sorry, perfectionism :D, work is really great) — spoon and sugar have similar colors (light gray and white). Maybe because of my Dell XPS 13 screen colors. |
@ai Why close? Re: SS, we could keep it, but maybe we should write it out as @natemoo-re I like the first option the best out of everything as well. I wish the sugar cube were a cube instead of short though. |
Why not at least stencil the PostCSS logo on one side of the sugar cube for better association with the PostCSS project itself ? Or use the PostCSS logo as kind of 'summoning indecator' and summon a sugarcube displayed in the middle of the logos inner circle. maybe some cubes could already make a circle around it summoning a new follow ;) etc etc. |
@michael-ciniawsky originally I thought about using Sugar CSS outside PostCSS ecosystem too. Looks for example at Rework’s css-whitespace. Anyway, Autoprefixer, RTLCSS, Stylelint, CSS Modules has no PostCSS stencil in their logos. |
But let’s make a brainstorm. What if we call this project “PostCSS Sugar”? With |
+1000. After #7 (comment) I can't stop thinking about “SS” in “SugarSS”. |
Also, |
@Grawl Panic around of SS in “SugarSS” is a little bit madden. Look at this Chevrolet Camaro SS. If someone says you: “Hey, do you want to drive my Camaro SS?” you really answer him: “Oh no, man, it's all about Waffen-SS”, yep? I don't think so. And I don't think that Italians run around the desk screaming “Cristo! Mama mia! Le SS! Le SS!” when they see LESS. @ai If you want to separate SugarSS and PostCSS it can't be called “PostCSS Sugar”. And “SugarCSS” is not so good 'cause user can be confused by “SugarSS” and For brainstorm:
|
I fully agree with you |
The hysteria around 'SS' is a bit ridiculous… I mean aren't we past the war by now? Anyway, following on from @igoradamenko, what about Minimal CSS?
Also, |
I really think too that banning all But if someone if really sensitive to this topic, we can change name (anyway our feelings is a subjective thing and people feelings is always more important that project title). |
Guys. I am thinking right now of keeping old SugarSS name:
What do you think? |
OK. I add Maria’s logo to README |
So can we go with @natemoo-re's spoonful of sugar (cube)? I'm thinking just the icon, not the text, either above or below or replacing the PostCSS logo on the README. If we're going with a logo replacing the title of the README, I think the type should be changed (maybe to one of these options; probably shouldn't underline SS even though it's fine to be in the title), but I really like the icon. Edit: (posted too late) um, like I said on the PR, "SugarCSS"? |
SugarSS & |
If it's on the side like that, it probably shouldn't have text, and currently the text is inconsistent with the title of the project. |
@1j01 logo with title is better, because many article/keynotes authors will take logo from this page. And of course it will be better to take it with title. |
It'd be good if we could include the image with the text cut off on the README, with the (correct) text in the image file. I know it can be done on a webpage, but it probably can't be done with on GitHub... Oh! But we can have two versions, and have the image without the text link to the version with the text. |
Maybe try Inkscape? (I was gonna try to do it in a bit) |
#14 fixed |
I'll still do a PR for the linking I described (once that's merged). |
Opened #15 |
@corysimmons yeap, @1j01 @dbox are right, SVG file has some problem on Linux preview. It will be nice if somebody will fix it. |
@jt3k looks nice. But too closer for abstract logos, which, I think, will not work in open source. We need more emotions and story. |
yepp! i think, the character from the cartoons on the logo looks better |
I think this project need separated logo. But let’s avoid Schutzstaffel associations ;).
/cc @janmarek
The text was updated successfully, but these errors were encountered: