remnynt / noundry

A community-sourced Noun trait workshop

Noundry

Welcome to the Noundry, a community-sourced Noun trait workshop.

Submit trait artwork now for potential inclusion in the Nouns protocol!

Introduction

The Nouns protocol code and artwork are upgradeable and extensible, both of which are controlled by the Nouns DAO.

Noun artwork, called traits, can be voted into the protocol via a Nouns DAO proposal. This repository exists as a centralized storage solution for potential Noun traits.

Acceptance into this repository does not equate to acceptance into the protocol.

Contributing Traits

1. Fork this repository

• Using GitHub Desktop:

  • Getting started with GitHub Desktop will guide you through setting up Desktop.
  • Once Desktop is set up, you can use it to fork the repo!

• Using the command line:

  • Fork the repo so that you can make your changes without affecting the original project until you're ready to merge them.

• GitHub Codespaces:

  • Fork, edit, and preview using GitHub Codespaces without having to install and run the project locally.

2. Commit your artwork

• Noun traits must be submitted as 32x32 pixel PNG images. Each image must contain a single trait, which is placed in the correct trait sub-folder. The following trait types are accepted, with the first being the lowest layer: bodies, accessories, heads, glasses. A trait which proceeds your custom trait may paint over some or all of it.
• Ensure Noun trait files are named appropriately. For example, a file containing a boat head should be called boat.png.
• By contributing to this repository, you release all committed artwork under a Creative Commons license; waiving all copyright and related rights to the artwork. Read the contributor license agreement here.
• Keep it nounish. Artwork that is explicit, hateful, or otherwise inappropriate will not be accepted.
• Only the initial contributor, or a user with the consent of the initial contributor, can replace exising artwork. Otherwise, artwork should be added as a separate image.

3. Create a Pull Request

When you're finished with the changes, create a pull request, also known as a PR.

• Fill in the pull request description, which summarizes the traits being added.
• Enable the checkbox to allow maintainer edits so the branch can be updated for a merge.
• We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.