How to create and publish a Code Card

Code Cards you create in My Cards are saved to your account as private drafts first. They are not automatically visible in the Public Library. You decide when to publish them.

At minimum, a card needs:

You can also add useful optional information such as difficulty level, tags, environment or framework, operating system, architecture, what the code was tested with, source information, license, notes, and warnings.

If the code is your own, choose Original contribution.

If the code is adapted, excerpted, or taken from official documentation, identify the source. Code Card requires either a source name or source URL for these source types before the card can be saved.

If your language is not currently supported, choose Other / unsupported language and enter its name.

You can still create the card. Code Card will use a plain-text fallback for the code editor, and signed-in users can optionally indicate how important proper support for that language is.

When the form is complete, submit it. The card is saved to your account and appears in My Cards as a Private draft. Creating the card does not publish it.

Once published, the card becomes visible in the Public Library and may be viewed and copied by other visitors. Publishing also makes the card's contributor handle and source metadata visible.

Publishing a Code Card does not mean that Code Card Library has independently verified or moderated the code.

Before publishing, review the code itself, its source, licensing information, and any security or compatibility concerns.

You can use Mark tested to record that you personally tested the current revision. This is owner testing and is separate from independent verification.

Yes. From My Cards, select Unpublish and confirm the change. The card will leave the Public Library and become private again. Existing private forks created by other users remain in their accounts.