cfomodz / misbrands Goto Github PK

• May 2019: @samdbeckham's legendary javascript-java sticker (website) (tweet)
• Aug 2019: @mkrl's misbrand repo (repo)
• May 2022: @ohmyhub's fork (repo)
• Feb 2024: @pReya's fork (repo)
• Mar 2024: This fork!

Of course, that's why those are here.

Yes, you can! Not from me, but from any custom sticker vendor of your choice.

This is a fork of the original repo that hadn't been updated in some time. I'm working on adding new logos that were submitted as pull requests to the original repo.

To make a misbrand, choose two existing brands. Generally the fanbase for the brands have as much overlap (eg: Rust & Golang) and/or contention (eg: Vim & VSCode) as possible or the brands have similar market niches (eg: OpenVPN & NordVPN).

Once the two victum brands are chosen. Take the style (eg: theme/design) of one brand and join it with the text of the other brand. Viola!

Check the FAQ for more resources on DIY-ing a misbrand

• Look for the 'Press' or 'Media' section on the website, there will usually be assets that make a good starting place
• Search the codebase for svg

If you don't know where to start, use Inkscape (website) (gitlab). There are tutorials and resources online, just search for 'How do I do XYZ in inkscape?'

There are two ways to submit a misbrand:

• Issue: Create an issue on this repo with the image!
• Pull Request: Click the fork button, add the image to your copy of this repo, go to 'Pull Requests' and click 'New pull requests'
  • Pleae follow the file and commit conventions below

There are two naming conventions:

• One for files to make them easier to find and understand
• One for submitting images you didn't create

For all the images, our convention is

• {text}-{style}.svg

Example: The text says python in the logo style of php. python-php.svg

If there is a file with that name already existing simply add a dash and a number starting with 02 and incrementing up from there.

Example: You submit a misbrand that says emacs in the style of the vim, there is already an emacs-vim.svg in the repo. Name your file emacs-vim-02.svg.

• If you created the image, do whatever you want for the commit message!
• If you are adding an image you didn't create, structure the message like so:
  • {text} in the style of {style} (credit @{user}) <{url}>
  • Where {user} is the user who created the image
  • And {url} is the repo/website the image came from