Redesign logo for smaller screen sizes

caleb531 / automata

A Python library for simulating finite automata, pushdown automata, and Turing machines

https://caleb531.github.io/automata/

MIT License

338 stars 63 forks source link

Redesign logo for smaller screen sizes #199

Closed caleb531 closed 8 months ago

caleb531 commented 8 months ago

The favicon has also been regenerated based on this new logo. Let me know what you think! I wouldn't say it's a huge difference, but then again, it's challenging to fit two states and a transition into one 24x24 icon lol.

coveralls commented 8 months ago

coverage: 99.64%. remained the same when pulling 64cf8c63d2f3a8ec37458391c0608e8e6f9398ae on new-docs-logos into 9ddbbb94d1130bd65426ac3b330b0ab40e59fc71 on develop.

caleb531 commented 8 months ago

@eliotwrobson Yeah, you're right. I went with about the same blue as the original logo, but I agree it just doesn't work. I feel like orange might look a bit tacky—I was thinking for either white or some shade of yellow.

eliotwrobson commented 8 months ago

@caleb531 I think yellow is a good choice!

caleb531 commented 8 months ago

@eliotwrobson Okay, the transition color is now yellow per 64cf8c63d2f3a8ec37458391c0608e8e6f9398ae, and I think it's a big improvement indeed!

caleb531 commented 8 months ago

@eliotwrobson Yeah, let's save that for a separate PR, since we'll have to think about layout concerns and all. Merging this now, though!

caleb531 commented 8 months ago

@eliotwrobson BTW, I've thought more about the merge-to-main thing—I was reminded that you committed some citation metedata to main directly without subsequently publishing a release, and I was fine with that because they were just housekeeping changes. So by extension, merges to main without publishing a release should be quite fine as well if they're just housekeeping changes like these.

With that, I've merged in the favicon changes to main so they can reflect on the docs site! https://caleb531.github.io/automata/