[styling] Consider keeping the branding of the JMESPath logo about jmespath.spec HOT 5 CLOSED

I took some artistic liberty to resolve some minor issues.

Everywhere else JMESPath is written, it is lowercase "ath". I felt it would be good to make it consistent and helps make it visually distinct from the JMES portion. I also extended the J to hang down to visually incorporate the "Community Edition" subheading. "JME" was made thicker to improve readability, especially when it is displayed at a smaller size. "Path" was changed to black from white to be compatible with a transparent background, this allows it to better integrate with surrounding styling rather than forcing a background color. I still need to produce a stylesheet for the svg that will allow swapping the colors for compatibility with a dark background.

Is there a downside to taking this opportunity to update the the branding? The changes are minor enough that it is still recognizable with the original. I think that we should make some effort to not confuse people between our fork and James'.

I am not married to any of these changes if you feel we really should stick to the original logo.

from jmespath.spec.

I guess you have some good reasoning behind the changes you made.
Maybe let's keep it as you've done. We will always be able to respond to feedback from the community, if any at all.

from jmespath.spec.

Here is a prototype with the uppercase path

from jmespath.spec.

Here is a prototype with the uppercase path
I admit to prefer this one 😏

from jmespath.spec.

sure, I will swap that one into the repo

from jmespath.spec.