About DWEEB and how it is tested

Who makes DWEEB

Faizo designs, develops and maintains the editor, its Discord Activity, the delivery service and the public guides. Product claims are tied to workflows that exist in the shipped application. The repository exposes the implementation, issue history and automated tests so technical statements can be checked rather than taken on trust.

DWEEB is an independent project and is not affiliated with Discord Inc. Discord is the authority for API behavior; the editor translates that behavior into a visual workflow and links to primary Discord documentation where a guide depends on it.

How preview fidelity is measured

The preview is calibrated against the live Discord web client, not styled from memory. A representative Components V2 payload is built in DWEEB, posted to a private test channel, and compared with the same message in the editor. Colors, spacing, typography, button geometry, containers and media-gallery layouts are checked from Discord's rendered DOM and computed styles.

1. Use the same payload. Build representative text, container, section, media, button and select-menu cases.
2. Render it in Discord. Send the payload through the documented webhook API and inspect the current desktop and narrow layouts.
3. Measure, then implement. Record computed values and image geometry before updating preview tokens or layout rules.
4. Protect known behavior. Regression tests cover Discord-specific markdown, payload normalization, limits, conversion and component validation.

A browser preview can still differ in native emoji artwork, fonts installed on the device and changes Discord rolls out after the latest review. Those boundaries are treated as limitations to re-test, not reasons to claim perfect equivalence without evidence.

How product and guide claims are reviewed

Guides begin with Discord's developer documentation and are checked against the editor's actual import, validation, send, restore and update paths. Dates on a page change only after a substantive content review. Security and privacy copy distinguishes local browser data from optional connected services, and the Privacy Policy lists those boundaries.

Errors and edge cases are tested before release through TypeScript checks, unit tests, generated validation corpora shared with the server, a production build and a post-generation SEO audit. The audit checks canonical URLs, sitemap coverage, metadata, structured data, internal links, content depth and social assets across every indexable page.