Skip to content

ENES

Contribute a term

Write a new Tidbit entry in English and Spanish, check it against the same rules as every other entry, and send it for review.

Know a technology term that is missing? Write it here. The form checks your entry as you type, against the same rules every Tidbit entry follows, and shows how it will look. When it passes, you send it as a GitHub issue: the repository checks it again and a maintainer reviews it before it is published.

Every entry exists in English and in Spanish, so you write both. Not sure about one of them? Do your best and say so in the issue; reviewers help with the language. Sending it needs a free GitHub account.

This form needs JavaScript. You can also copy an existing entry from the repository, follow CONTRIBUTING.md and open a pull request. CONTRIBUTING.md

The term

Topic

Second topic (optional)

Level

Basic: anyone can read it cold. Intermediate: assumes the basic terms of its topic. Advanced: assumes the intermediate ones.

Basic Intermediate Advanced

URL

Lowercase ascii and dashes, from the English title. The page will be at /<slug>/.

The name is also an everyday word (Apple, Meta, Swift): link it only with its exact capitals

English

Title

The name of the concept, 1 to 4 words. Keep well-known acronyms as they are.

One-line definition

What it is, in plain words, under 90 characters.

Explanation

2 to 4 short paragraphs, separated by a blank line: what it is, what it is for, why it matters now. **bold** for the term the first time, `code` for commands and file names.

Everyday analogy

1 to 3 sentences.

Key points

3 or 4 facts worth remembering, one per line.

Sources

2 or 3 official docs or Wikipedia pages, one per line: Label | https://…

Other names

Plurals, acronyms or other spellings, separated by commas. Not the title itself.

Image description

What the illustration shows, for people who cannot see it.

Spanish

Title

The name of the concept, 1 to 4 words. Keep well-known acronyms as they are.

One-line definition

What it is, in plain words, under 90 characters.

Explanation

2 to 4 short paragraphs, separated by a blank line: what it is, what it is for, why it matters now. **bold** for the term the first time, `code` for commands and file names.

Everyday analogy

1 to 3 sentences.

Key points

3 or 4 facts worth remembering, one per line.

Sources

2 or 3 official docs or Wikipedia pages, one per line: Label | https://…

Other names

Plurals, acronyms or other spellings, separated by commas. Not the title itself.

Image description

What the illustration shows, for people who cannot see it.

Illustration

SVG code

A whiteboard sketch: 400×240, basic shapes and short labels in English, only the palette colors. Start from the template.

Check

Send

After you send it, the repository checks the entry and leaves a comment on the issue. If something needs changing, edit the issue; once a maintainer accepts it, a pull request with your name as co-author is opened and the term is published when it is merged.

Preview

This is how the page will look (term links are added when it is published).