ESPHome vs PDFMonkey

February's release introduced a drag-and-drop builder written from scratch — components dropped onto the page, styling done visually, and loops, conditions, and variables exposed through panels rather than template code, with custom CSS still available underneath. Around it sits API-side work: a Ruby SDK 1.0 with full CRUD, typed exceptions, persistent connections, and multi-tenant credential scoping, and password-protected output where adding a _password field to a document's meta object produces an AES-256 encrypted PDF across every template type, every integration, and every plan including free. Earlier entries cover template restore and self-service Boost Pack purchases.

Two audiences are being served from one engine. The builder opens template authoring to people who do not write HTML, which is the constraint that has kept document-generation tools inside engineering teams; the SDK and meta-field work keep the developer path uncluttered, with encryption arriving as a one-field change rather than a configuration screen. The pattern in both is minimal ceremony — no template changes, no account setup, works everywhere — which is what a product does when it is trying to remove reasons to look elsewhere rather than add reasons to upgrade.

Expect the builder to keep absorbing what previously required the code editor, since a visual editor's value depends on how rarely a user has to drop out of it. The entries stop in March, so where the API side goes next is not readable.