uglydocsRequest API access

Every document
starts out ugly.

The ugly duckling was a swan all along. It had only hatched in the wrong nest. Your data is the same.

Send it as a tree of blocks. uglydocs lays it out on real A4 pages, carries tables across page breaks and hands you back the PDF it was meant to be.

Page 2 behind it: a running head with the Kurbelwerk logo, and the price table carrying on with its header row repeated.
Page 1 of the Kurbelwerk dealer catalog, rendered by uglydocs: cover illustration, title, ordering details and the first product with key facts and a price table.
  1. Running head from page 2
  2. Header row repeats
  3. Rows never cut in half
  4. Page numbers know the total
A dealer catalog, five pages, rendered by uglydocs from one list of blocks. See page 2 up close

Chapter I · The wrong nest

A swan's egg rolled into a duck's nest. The chick that hatched was too big, too grey and too clumsy, and the whole farmyard laughed at it.

The content was never the problem

Your data hatches in the wrong nest, too: a Word template, an HTML-to-PDF export, a spreadsheet printout. It comes out looking wrong, and everyone notices.

  • A table row is cut in half by the page edge.Tables split between rows, never through one.
  • Page 2 starts with numbers and no column names.The header row repeats on every page the table reaches.
  • A heading sits alone at the bottom of a page.Headings never end up alone at the bottom of a page.
  • "Page 3". Of how many?Page 3 of 5.
The duckling: html-to-pdf
The same catalog page rendered by uglydocs.
The swan: uglydocs, same data

Chapter II · The long winter

The duckling ran away and spent a long, hard winter alone. One night the pond froze around it, and it could not move.

Pages break. Your tables don't

For documents, winter is the page break. It's where tables tear, headings get stranded and nobody knows which page they're on. uglydocs gets your content through it: you send one long list, the engine decides where each page ends.

Catalog page 2, rendered by uglydocs: a running head with logo and title, the cassette table continuing with its header row, two more products with price tables, white space at the bottom, and the footer reading Seite 2 / 5.
  1. The running head starts on page 2The first page stays clean. Rules can differ for the first page, the rest, or every nth page.
  2. The table carries on with its header rowRow KW-1204 didn't fit on page 1. It moves on whole, and the column names come with it.
  3. No heading left alone at the bottomThe next section didn't fit, so it starts on page 3. White space instead of a stranded heading.
  4. Page numbers that know the total"2 / 5", worked out after the whole document is laid out.
Kurbelwerk catalog, page 2 of 5, unedited engine output.

Chapter III · Spring

When the sun came back, the duckling spread its wings and found that they had grown strong. They carried it up and away, without it knowing how.

Your data gets its feathers

34 designed blocks that combine freely. You don't design anything; you combine. A product catalog needs no special product-card block: it's a title, an image, a key-value list and a table.

Text
title, title-rule, paragraph, figure, table, key-value-list, key-value-stack
Layout
columns, stack, card, divider, spacer, spread
Media
image, icon, map, logo-list, tag-cloud
People & timelines
headline, portrait, contact-line, entry-*, level-list, skills-*
Page
running-head, page-number, signature
Catalog page 1 with the blocks it is built from labelled: image, title, key-value list, title with rule, image and table.
  1. image
  2. title
  3. key-value-list
  4. title-rule
  5. image
  6. table

Chapter IV · The reflection

It landed on a lake and bent its head to the water, expecting to see a grey duckling. Looking back at it was a swan.

Same bird, new feathers

Content and design are separate, so the same document can show itself in a different light. Switch the theme and the look changes; the content stays. Brand colour, fonts, text size and margins are tokens on each document, so a new customer doesn't need a new theme.

Theme
atlas
CVs, clean sans with a strong accent
skald
CVs, serif headings, quiet navy
liquidimmo
Property valuation reports
ledger
B2B product catalogs and price lists
Invoice rendered with the liquidimmo theme: purple accent, Open Sans.
Invoice, liquidimmo theme.

Interlude · Five folds

The swan in our logo is folded from a single flat sheet of paper. Every uglydocs document is made the same way.

From a flat sheet to a swan

You make the first fold. uglydocs makes the rest.

  1. Step 01

    Your data

    Records from your shop, CRM or app. A flat sheet.

  2. Step 02

    Block tree

    You map it to JSON blocks, a theme and tokens.

  3. Step 03

    Engine

    Lays out the blocks and breaks them across pages. Live in an iframe via postMessage.

  4. Step 04

    Print server

    Renders the same pages headless. Images travel with the document.

  5. Step 05

    PDF

    Finished A4 pages. A swan.

// POST /print
{
  "locale": "de",
  "theme": "ledger",
  "tokens": { "accent": "#e2661b" },
  "content": [
    { "block": "title", "text": "Antrieb & Bremsen" },
    { "block": "key-value-list", "items": [ … ] },
    { "block": "table", "columns": [ … ], "rows": [ … ] }
  ]
}

Readable by machines, too

GET / publishes the block catalog, themes, fonts and the JSON schema. Other systems, or an AI agent, can read it and fold valid documents without a human in between.

Cross-origin access is limited to the origins you allow.

Chapter V · Among swans

Three swans glided towards it across the lake. They did not laugh. They welcomed it as one of their own.

Already flying

Liquidimmo
Property valuation reports and exposés
CorraV
CVs, tailored per application

"It matters not to have been born in a duck's yard, if one has been hatched from a swan's egg."

Hans Christian Andersen, The Ugly Duckling, 1843

Your data was a swan all along

Tell us what you need to generate. We'll set you up with API access and a theme in your colours.