W Whoila Join the beta
whoila.com · a play on voilà

Ask once.
It appears.

Whoila is the make tool for publishers. One brief becomes the article, the 800×1200 jacket, and the 6×9 book — then those three artifacts go out through the endpoints on your own site.

Not a CMS.

Not a chat with an export button.

A publisher’s make bench.
Three artifacts, one brief

Write it. Jacket it.
Send it to the site.

Whoila does not host your journal. Your journal stays on designforever.com, weddinghosts.com, or wherever you already publish. Whoila is the bench that makes the work and hits your API.

01 · BLOG

The article

Markdown/HTML with a lede, optional roster or stat strip, sourced sections, and a Sources list. Posted to your existing /api/admin/blog.

POST /v1/make { kind: "blog" }
02 · THUMBNAIL

The jacket

An 800×1200 cover as SVG + HTML5. Pushed to your thumbnail hook, or fetched from Whoila’s artifact URL.

GET /v1/jobs/:id/cover.svg
03 · PDF

The book

A 6×9 pamphlet: foil-rule cover, then the same body set as interiors. Binary on your PDF hook.

GET /v1/jobs/:id/book.pdf
Already hooked up

Two houses, same bench.

Each product keeps its brand, its /blog, and its keys. Whoila is the shared make tool underneath.

Journal · templates

DesignForever.com

The public journal at /blog. Whoila posts the article through x-vae-service-key, then the jacket and 6×9 book ride the same job. Same shape the in-house Make tool already used.

Open the journal →
Built to connect

Your site already has the door. Whoila knocks.

Adapters for DesignForever and WeddingHosts. For everyone else: three signed webhooks — blog JSON, thumbnail bytes, PDF bytes. HMAC in X-Whoila-Signature.

Read the API Open /admin 
# Make a piece for a connected site
curl -X POST https://whoila.com/v1/make \
  -H "Authorization: Bearer whl_live_…" \
  -d '{"site":"designforever","kind":"blog","brief":"…"}'

# Then publish article + jacket + book
curl -X POST https://whoila.com/v1/jobs/JOB/publish \
  -H "Authorization: Bearer whl_live_…"
Private beta

Leave an email.
We’ll open /admin.

Paying customers sign in with Google, connect a host, and paste their own blog / thumbnail / PDF endpoints. Agents use the same API.