Project · Live
DWEEB
A visual builder for Discord messages. Design webhook messages, embeds and Components V2 layouts in the browser, see exactly how Discord will show them, and send them where they need to go.
Why it exists
Discord messages used to mean plain text plus, at best, an embed. Components V2 changed that: a message can now be a layout of containers, sections with thumbnails, text blocks, media galleries, separators, files, buttons and select menus. That is powerful and, written by hand as JSON, very easy to get wrong. Discord rejects a whole message for one misplaced component, and the error rarely says which one. DWEEB lets people build those messages visually, with a preview they can trust and validation that names the exact problem before anything is sent.
What it does
- Build visually. A component tree on one side, a live preview on the other. Every Components V2 component is supported, along with classic content and embeds.
- A preview measured against Discord. Colors, spacing, gallery layouts and markdown rules come from measuring Discord's own client, not from screenshots. How that's done.
- Validation before sending. Character limits are counted the way Discord counts them (in UTF-16 units), components are checked for where they're allowed to sit, and every issue links to the field that needs fixing.
- Send, update, schedule. Post through a webhook (DWEEB can create one for a channel you manage), edit a message you posted earlier, or schedule a post for later, including into threads and forum posts.
- Buttons that work. Interaction plugins give buttons and menus a job: support tickets, giveaways, polls, self-assignable roles, canned replies, forms in modals, server directories. A single dispatcher receives Discord's interactions and routes each click to the right plugin.
- Templates and a message library. 36 starting templates (rules, welcome messages, role menus, announcements and more), plus a per-server history of what was posted and a shelf of drafts.
- Code export. Any message can be exported as discord.js or discord.py code, or as a cURL, fetch or Python request. Each target is verified against the real libraries.
- Build together. DWEEB also runs as a Discord Activity: start it in a voice channel and everyone in the call can edit the same message live, then post it to the server.
- AI help, if you want it. A built-in assistant can draft or rework a message, and an MCP connector lets AI clients such as Claude build and send messages with your Discord permissions.
How it's built
The front end is a TypeScript and Preact single-page app served as static files, with a generated guides and templates site alongside it. Everything that talks to Discord on someone's behalf runs in Rust: an API server that handles sign-in, webhooks, scheduling and the message library (sensitive payloads are encrypted at rest), an interaction dispatcher, and one small service per plugin. They run in Docker on a single server behind Caddy, with SQLite for storage. Alerting is designed so that only faults in my own code or infrastructure page me, and the details of that took more work than most features.
DWEEB is free to use. Paid plans raise quotas, such as how many messages are kept in the server library or how many scheduled posts can be pending, but no feature is locked behind a plan.
Writing about DWEEB
- Nested deadlines: answering Discord interactions inside three secondsRouting Discord button clicks through a dispatcher to plugin services inside the 3-second window: failure classes, safe retries and nested timeouts.9 November 2026 · 7 min read · Discord API, Rust, Reliability
- Measuring how Discord renders a message instead of guessingKeeping a Discord message preview faithful by measuring Discord's own client: the workflow, media gallery layout rules, failure states and markdown quirks.9 November 2026 · 5 min read · Discord, Components V2, Front end
- When a deploy deletes the chunk an open tab still needs"Failed to fetch dynamically imported module" after a deploy: why code-split apps hit it, how to recover safely, and how to tell a stale tab from a bad release.9 November 2026 · 7 min read · Web, Deployment, Service workers
- Discord keeps your webhook's avatar_url, not the image, so host it foreverDiscord stores your webhook's avatar_url, not the image. Why uploaded avatars break later, the silent size limits, and how to host them permanently.9 November 2026 · 4 min read · Discord API, Webhooks, Rust
- Your crash reporter is paging you for someone else's codeExtensions and third-party scripts throw into your page's error handlers. How to attribute a JavaScript stack trace to its real owner, and why the server decides.9 November 2026 · 6 min read · JavaScript, Observability, Web
- Opening the Discord app from a web page without opening the website tooAn "Open in Discord" button should launch the app or the website, not both. The discord:// race, cold starts on Windows, and each browser's popup limits.9 November 2026 · 4 min read · JavaScript, Discord, Browsers
- Keeping a TypeScript validator and its Rust port in agreementThe same validation rules live in a TypeScript web app and a Rust server. A generated test corpus keeps them identical, and UTF-16 length is the first trap.13 November 2026 · 6 min read · Rust, TypeScript, Testing
- Cutting 30 KB from a boot bundle by moving module boundariesLazy loading didn't shrink my first-load JavaScript until I learned that a bundler places each module in one chunk, whole. How to find and split those modules.13 November 2026 · 6 min read · Performance, Web, Front end
- Two moderators click Close at once: a compare-and-swap state machine in SQLiteHow a Discord ticket bot stays correct under double clicks, stale buttons and restarts: every state change is one guarded UPDATE, and only the winner acts.13 November 2026 · 6 min read · Rust, SQLite, Discord API
- Preact's useId gave my dialogs the same ids as the page behind themuseId in Preact counts per render root, so a dialog rendered in its own root repeats ids already used on the page. How to detect duplicate ids and replace the hook.13 November 2026 · 5 min read · Preact, Accessibility, Front end
