AI Artifacts & Generated Sites

Generated HTML

Definition

The phrase covers several sources — a site generator's build output, a template engine, an export from a design tool, and now a model writing a page from a description — but the result is one kind of thing: a text file of tags that a browser can parse. Model-written HTML has a recognisable style. It is usually one document with a style block in the head and a script block before the closing body tag, it tends toward utility classes or long inline style attributes, and it often pulls a framework or a font from a CDN rather than shipping it. It also carries habits that are worth checking: comments left in, placeholder text, duplicated rules, and occasionally a tag that was opened and never closed. Browsers are forgiving of the last one, which is why a structural error can sit in a page for months without anybody seeing it.

Why It Matters

Because the output is plain HTML, it inherits every property of plain HTML — it caches well, it degrades gracefully, it can be read by a screen reader, and it costs nothing to serve. That is the good news, and it is why generated pages are so easy to publish. The less good news is that generated markup is often heavier than it needs to be. A page that could be 15 KB arrives at 90 KB because the same style is repeated forty times, and on a slow mobile connection that is roughly half a second of difference. Accessibility is the other thing to check by hand: generated pages frequently skip alt text, use a div where a button belongs, and jump from an h1 to an h4.

How It Works

A browser loading generated HTML does exactly what it does with any other page. It reads the bytes, applies the inline CSS as it encounters the style block, builds the DOM from the markup, then runs the script block. A static host contributes one thing: it returns the file with the correct MIME type, text/html, so the browser parses it as a page instead of showing it as text. Get that wrong — usually by saving the file as .txt — and the visitor sees the source code instead of the page. External references resolve from the address the page is served at, so an image at images/logo.png must exist at that path on the host.

Real-World Example

An accountant asks for a fee comparison table, gets a 60 KB HTML file with the styling inline, and uploads it to 99helpers as bright-fees. It renders correctly at bright-fees.99helpers.site on the first try, which is typical. The one fix needed was an image tag pointing at logo.png, a file that had never existed — she inlined the logo as an SVG instead and re-uploaded, and the broken icon disappeared.

Common Mistakes

  • Saving the file with a .txt extension or no extension — the host serves it as plain text and the visitor sees tags rather than a page
  • Publishing without opening the console once — a single script error can stop every interactive element on the page while the layout still looks perfect
  • Leaving generated placeholder content in place — lorem ipsum and an invented address are the two most commonly shipped mistakes
  • Skipping the accessibility pass — missing alt attributes and clickable divs are cheap to fix before launch and awkward to explain afterwards

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →