For the complete documentation index, see llms.txt. This page is also available as Markdown.

Institutional Landing Pages

Generate, edit, preview, publish, and unpublish a structured institutional landing page from the Console.

The institutional landing builder is available in the Acceleration Program inside the signed-in Console.

It creates a structured institutional page with AI assistance. The landing belongs to the Console scope rather than to an individual workspace.


Generate a landing

Start the institutional landing accelerator and provide the requested business context.

Zaia generates a structured draft from supported templates, blocks, styles, color settings, and a scheduling call to action.

The generated result is structured content. The builder does not generate or accept arbitrary HTML or React code.

Only HTTPS scheduling links are accepted for the call to action.


Review and edit

The builder provides an authenticated preview before publication.

You can update supported fields directly in the editor or request contextual changes through the AI assistant. Field targets and content lengths are validated before changes are saved.

Regenerating or refining the landing keeps the existing landing data that is not replaced by the requested change.


Publish and update

Publishing makes the current landing available through a public URL.

  • If the Console has an active White Label domain, the public URL uses that domain.

  • Otherwise, Zaia uses a stable pages.zaia.app/l/{slug} address.

  • Publishing again updates the public version with the current landing.

  • Unpublishing removes public access while preserving the editable landing in the Console.

The public page can be opened without signing in.


Remove a landing

Removing the current landing deletes its editable Console state. Unpublishing and removing the landing are separate actions.

Use Unpublish when you want to take the page offline but keep it available for future editing.


Access and isolation

Landing generation and management follow the existing Console permissions.

Each Console can access only its own institutional landing data. A landing or public address from one Console is not exposed in another Console.