# AI will soon replace GUIs: rebuilding an InDesign leaflet through conversation, not clicks

*About repetitive, structured document-layout work — calendars, price tables, contact lists — not graphical interfaces in general.*

Will conversational AI interfaces replace graphical desktop applications for document layout design? Traditional GUIs hide layout markup behind visual frames, panels, and drag handles. Replacing mouse-driven layout editing with conversational AI commands turns visual adjustments into explicit code transformations.

Enters natural-language document engineering. Converting a complex InDesign leaflet into a single-source YAML and LaTeX pipeline replaces manual text frame editing with automated build execution.

![A line-art illustration of a device feeding a maze of manual controls into a PDF, contrasted with a programmable keypad](https://redaction-technique.org/images/blog/ai-will-soon-replace-guis-illustration.webp)
*From GUI maze to conversational document engineering: structured data in, PDF out. With a human still checking the result.*

> **Human judgment remains essential:** Conversational automation replaces manual data entry while leaving final layout review in human hands.

## InDesign layout limitations

Rebuilding annual print publications in InDesign requires repetitive manual edits across text frames: updating calendar dates, price tables, and contact details frame by frame.

While LaTeX handles multi-page books efficiently, hand-coding bespoke two-page leaflet grids from scratch requires substantial initial setup time. Using LLM coding agents removes the initial barrier to entry for custom LaTeX layout generation.

## Interface model comparison

GUIs require authors to locate specific menu options and edit separate text frames manually. Conversational interfaces translate high-level intent directly into structured source code updates:

<div class="not-prose my-6 flex justify-center">
  <span class="rounded-lg border border-gray-200 dark:border-slate-700 bg-gray-50 dark:bg-slate-800/70 text-gray-700 dark:text-slate-200 text-xs sm:text-[0.8125rem] font-semibold leading-snug px-3 py-2 text-center">
    Human intent: "update the leaflet"
  </span>
</div>

<div class="workflow-comparison not-prose grid gap-5 sm:grid-cols-2 my-6">
  <div>
    <h3 class="text-sm font-bold text-gray-900 dark:text-white mb-3">GUI path</h3>
    
  </div>
  <div>
    <h3 class="text-sm font-bold text-gray-900 dark:text-white mb-3">Conversation path</h3>
    
  </div>
</div>

## Spreadsheet data mapping

Importing structured spreadsheet data directly into YAML files replaces manual transcriptions:

- **Schema mapping:** Parsing CSV columns into structured YAML key-value pairs.
- **Single-source population:** Populating calendar grids, event cards, and contact references from single YAML definitions.
- **Automated compilation:** Rebuilding LaTeX PDFs automatically from updated YAML data.

Updating structured YAML files guarantees consistency across all rendered output surfaces.

## Conversational layout iteration

Initial LLM layout generations provide basic document structures while requiring iterative refinement:

- **Initial scaffolding:** Compiling calendar grids and basic column structures automatically.
- **Visual review:** Identifying spacing discrepancies, font alignment defects, and color profile mismatches.
- **Conversational feedback:** Issuing targeted correction requests to refine layout parameters.

Iterating through plain-text feedback prompts replaces repetitive mouse clicks with direct code modifications.

## Spatial judgment boundaries

Conversational interfaces excel at structural data transformations, while direct visual manipulation remains essential for spatial fine-tuning.

<div class="not-prose grid gap-5 sm:grid-cols-2 my-6">
  <div>
    <h3 class="text-sm font-bold text-gray-900 dark:text-white mb-2">Well suited to conversational automation</h3>
    <ul class="text-sm text-gray-700 dark:text-slate-300 leading-relaxed pl-5 list-disc space-y-1 m-0">
      <li>Structured data transformation: CSV columns into YAML key-value pairs.</li>
      <li>Repetitive edits across text frames, via single-source population.</li>
      <li>Iterative layout refinement through conversational feedback.</li>
      <li>Automated LaTeX compilation from updated YAML data.</li>
    </ul>
  </div>
  <div>
    <h3 class="text-sm font-bold text-gray-900 dark:text-white mb-2">Still requires visual human judgment</h3>
    <ul class="text-sm text-gray-700 dark:text-slate-300 leading-relaxed pl-5 list-disc space-y-1 m-0">
      <li>Visual alignment: adjusting crop boundaries and image placements by eye.</li>
      <li>Human verification: reviewing generated PDF outputs to catch subtle spacing defects.</li>
    </ul>
  </div>
</div>

Conversational automation replaces manual data entry while leaving final layout review in human hands. The next step is connecting LLM generation scripts directly to pre-commit linting hooks to flag layout overflow errors automatically.

## External sources

- [Graphical user interface](https://en.wikipedia.org/wiki/Graphical_user_interface)
- [Natural-language user interface](https://en.wikipedia.org/wiki/Natural-language_user_interface)
- [Claude Code](https://code.claude.com/docs/en/overview)

<small>*Hero image: ["Wurlitzer Theatre Organ Console"](https://www.flickr.com/photos/55231259@N00/5680267777) by [Alexander Baxevanis](https://www.flickr.com/photos/55231259@N00/), licensed under [CC BY 2.0](https://creativecommons.org/licenses/by/2.0/).*</small>

---

Source: https://redaction-technique.org/ai-will-soon-replace-guis