HTML business card from a JSON profile

What changed. A shareable card is generated in seconds as one file that opens offline, with no build step and no third-party runtime.

Stack. JSON profile · single-file HTML · inline CSS · system fonts

Context

Freelancers, consultants, and small teams still need a card they can send before a call. Agency design for a one-page presence is slow. Online generators watermark the export or lock the file behind an account. The operator wanted something fast, owned, and usable without a network.

Task

Accept a JSON profile — name, title, contacts, tagline, skills — and emit a finished HTML page in a chosen style. One input file, one output file, no build toolchain. The page must open in any browser, including offline. Teams should be able to regenerate cards in bulk when people join, without hiring a designer per name.

What we built

A generator that reads the profile and writes a self-contained HTML file. CSS and layout are inline. Fonts are system fonts, so the file does not wait on a CDN. Three styles cover different rooms: a quiet minimal card, a high-contrast bold card, and a more expressive creative card. Dark theme is supported.

The file is typically between a few kilobytes and half a megabyte — small enough to attach or host anywhere. There is no runtime dependency and no watermark. Generation finishes in seconds.

What changed

A conference card exists before the trip, not after a design ticket. A team can mint consistent cards for new hires from the same profile schema. The page still works on a train with no signal.

What we would do differently

Keep the model out of the layout. The first loop asked a language model to invent the whole page, which made style regressions cheap to ship and hard to diff. A fixed template per style, with the model filling copy fields only, would have made the card a product instead of a prompt lottery.

Related service: Websites