Can a prompt replace Piktochart?

Build an infographic generator where charts are produced from data and styled by a theme.

Document model: a vertical poster of fixed width and variable height, composed of blocks in order. Block types: title, section heading, paragraph, key-figure (a large number with a caption), chart, image, icon row, divider, and a two-column container that can hold two blocks side by side. No free positioning — the layout comes from the block sequence and the theme.

Theme: a token file defining a type scale, a palette with a categorical sequence for charts, spacing, and a background treatment. Every block consumes tokens only, so changing the palette restyles the charts and the text together. Ship two themes and document writing a third.

Charts, which are the point of this build. A chart block takes pasted CSV or TSV, infers column types, and offers only chart types the data can actually support — a bar chart needs one categorical and one numeric column, a line chart needs an ordered dimension, a scatter needs two numerics. Render with Vega-Lite, styled from the theme tokens rather than the library's defaults, so the chart belongs to the poster rather than sitting in it. Support bar, grouped bar, stacked bar, line, area, scatter, and a proportion block (a row of icons or squares representing a percentage, which is the shape infographics actually use most). Refuse pie charts with more than five slices and say why.

Data hygiene, shown rather than hidden: after parsing, display the inferred types and the row count, and flag missing values, duplicated categories and numbers that failed to parse. A chart built silently on a column where a third of the values were text is the failure mode that makes an infographic wrong rather than ugly.

Sources: every chart block carries a source field rendered beneath it in small type, and export refuses to proceed if any chart has an empty source. An infographic without attributions is a rumour.

Export: PNG at a chosen scale, and PDF at print resolution with text kept as text and charts kept as vectors. Warn before export if any block overflows its width or if text falls below a minimum legible size at the export scale.

Storage: the document and its data as JSON on disk, so it lives in a repository and diffs.

Out of scope: a template marketplace, stock illustration libraries, real-time collaboration, hosted publishing, and animated or interactive output.