A Shields.io static badge URL compresses a short label, a message, a color, an optional logo, and style options into a single image address, and a focused form lets you assemble that URL without memorizing path escapes or query parameters. To get a Badge of Justice TBC display badge, you enter the visible text on each side of the divider, pick a named or hex color, select a supported style, optionally supply a Simple Icons slug, then preview the live Shields.io render and copy the URL, Markdown snippet, or HTML image tag that the form assembles for you. The whole flow runs client-side, so your badge content stays in your browser until you paste it into the destination document. This approach suits static documentation such as a World of Warcraft TBC fan project, a private guild roster, or a mod archive where you want to mark content with a consistent, recognisable label. Because Shields.io serves the preview image directly, the badge you see in the preview region is the same image your readers will eventually load.
Why Use a Generator for a Badge of Justice TBC Display
A small status badge can make a README, documentation page, release note, or project dashboard much easier to scan. The hard part is rarely the wording; it is remembering how a static Shields.io URL separates the label, message, and color, how spaces and literal separators must be escaped, and which query parameters control the final appearance. The Badge Generator turns those details into a focused form, so the Badge of Justice TBC badge you assemble renders the same way every time without you hand-editing the path. Hand-edited URLs are error-prone, especially when a label contains a literal dash or underscore, and the generator removes that risk by applying Shields.io's documented doubling rules for you.
How Shields.io Static Badge URLs Actually Work
A Shields.io badge URL follows a documented shape based on the static badge endpoint, with the visible parts and the color carried in the query string and optional style, labelColor, and logo parameters appended through URLSearchParams. Literal dashes and underscores in visible text are encoded with Shields.io's doubling rules, while other special characters are URL encoded. This prevents a dash inside a label from being mistaken for the separator between badge parts. Optional style, label color, and logo values are added as query parameters instead of being mixed into the path. The Badge Generator performs that encoding for you, validates each input, and shows you the canonical URL it would render. The reference documentation on shields.io/badges describes the same parameter set, so the output of the generator stays aligned with what the upstream service expects when the badge is loaded.
Enter the Label, Message, and Color for Your TBC Badge
This is the core task for getting your Badge of Justice TBC display badge ready. Follow these steps in order:
- Open the Badge Generator form and enter the left-side label that should appear on the badge. A short noun such as tbc, wow-tbc, or badge-of-justice keeps the rendered width tight. Anything visible you want to preserve as text goes here, and the form doubles any literal dash or underscore so the badge renders correctly.
- Enter the message that appears on the right side of the divider. Typical choices for this badge include justice, tier 5, phase 1, or a guild tag such as karazhan-ready. Keep the message short enough to fit cleanly beside the label, because the rendered width grows with every visible character.
- Choose a named color such as blue, brightgreen, or gold, or paste a three- or six-digit hexadecimal value. A leading hash is removed automatically before the URL is built. If you want the label section to use a different color, fill in the optional label-color field with another named or hex value.
- Click into the preview region and confirm the badge renders the way you expect. The preview loads directly from Shields.io using the URL the form assembled, so the image you see is the image your readers will see.
Pick a Style and Optional Simple Icons Logo
Choose a supported style from the dropdown: plastic, flat, flat-square, for-the-badge, or social. Each style draws the rounded ends, shadow, and typography differently, so preview several at the size the badge will actually appear. If you want a brand mark on the badge, enter a Simple Icons slug in the logo field. For a TBC project you might try wow, worldofwarcraft, or a related slug from the catalog. If the logo does not appear, verify the slug against the current Simple Icons catalog. These options become query parameters rather than path components, so adding or removing them does not break the rest of the URL.
For a project header that already uses several badges, flat-square reads cleanly next to other rectangular tags. For a single stand-alone badge on a landing page, for-the-badge produces larger, bolder text. plastic mimics the classic Shields.io look, while social suits badges that act as a count or a status row.
Preview, Copy, and Test the Badge in Your README
The Badge Generator returns three useful formats that all point at the same canonical URL. Compare them and pick the one that matches your destination.
| Format | Best for | What you get |
|---|---|---|
| Direct image URL | Systems that accept a remote image source | https://img.shields.io/static/v1?label=...&message=...&color=... |
| Markdown snippet | GitHub or GitLab README, issue template, documentation file |  |
| HTML image tag | Web pages, CMS content, and static site generators | <img src="..." alt="..."> |
Copy the form that matches your destination. For a GitHub or GitLab project that documents a TBC guild roster or a mod archive, the Markdown snippet is usually the right choice. For a personal website or blog post, the HTML tag renders the badge inside the markup. The image URL alone is useful when you want to drop the badge into a tool that only accepts a remote image link, such as a Discord embed or a static page generator that does not parse Markdown. After copying, test the rendered destination. Some target platforms proxy remote images, and changes may be cached outside this tool, so a hard refresh or a cache-busting query parameter may be needed when you update the message later.
Validation Rules and Practical Limits
The Badge Generator applies strict checks around ambiguous or unsafe input. The following rules govern what the form will accept and what the canonical URL will contain.
| Input | Rule | Notes |
|---|---|---|
| Label | Must contain visible text, stay within a practical length limit, cannot contain control characters | Empty labels are rejected before any URL is built |
| Message | Same visible-text and control-character checks as the label | Special characters are URL encoded automatically |
| Color | Compact named form or three- and six-digit hexadecimal value | Leading hash is stripped before the URL is built |
| Logo | Must look like a Simple Icons slug | Existence on the current catalog is not verified by the form |
These checks catch common typing mistakes without pretending to validate whether every possible named color or logo currently exists on an external service. The form also stays entirely client-side, requires no account, and does not save a badge history between sessions.
When a Static Badge Is the Wrong Choice
A generated badge is presentation, not proof. A manually entered passing, secure, or 100% message does not verify a build, audit, or coverage report. For the Badge of Justice TBC display, this is usually fine because the badge is a static label about a stable piece of content. Use static badges for stable labels, links, versions, or statements you are prepared to maintain. For automatically changing facts, use a badge backed by the relevant CI system, package registry, or verified endpoint instead, since those endpoints carry the live data instead of relying on a manually maintained string. Also add surrounding prose or a meaningful alt description where context matters, because color alone should never carry the full meaning of the badge.
For predictable results, begin with a short label such as build, docs, version, or license and a concise message, preview several styles at the size where the badge will actually appear, copy the Markdown for repository documentation or HTML for a web page, and then test the rendered destination. If a logo does not appear, verify its slug against the current Simple Icons catalog. If a target platform proxies remote images, remember that changes may be cached outside this tool.