Fluent Commerce Logo
Docs

New UI Page Generation

Use CaseExamples that showcase what's possible with the platform. These use cases focus on feature and capability discovery and may not include implementation details.

Author:

Fluent Commerce

Changed on:

6 Apr 2026

Problem

Building a new page in a Fluent Commerce Mystique application requires knowledge of which components are available, how they nest correctly within one another, how to structure the data query that feeds them, and how to express the full composition as valid manifest JSON. For developers newer to the framework, this knowledge is not yet in place, and the documentation available does not always provide a clear, prescriptive path from a page requirement to a working manifest definition. Writing manifest JSON by hand is exacting work: an incorrect component alias, a missing required prop, or a malformed query reference can cause the page to fail in ways that produce unhelpful errors, and tracing those errors back to their source in a large manifest is time-consuming. Even experienced developers working without a guided process make independent structural decisions that produce inconsistency across pages, making the application harder to maintain as it grows. Without an automatic validation step following the build, structural problems in a newly created page often go undetected until the manifest is deployed and the issue is visible in the live application.

A developer is asked to build a new order detail page for the OMS application showing order summary information, customer details, line items, and fulfilment status. Working from the component documentation, they assemble a manifest definition by hand over several hours, referencing examples from other pages in the application for guidance. The page deploys without an error but renders incorrectly: one card component is nested at the wrong level, causing it to display without its expected data, and a tab component intended to separate items from fulfilments is not rendering because the alias used does not match the registered component name. A second developer reviewing the manifest identifies the structural issues but notes that the data query is also missing a field required by one of the attribute components, which will cause a silent rendering gap on orders with multiple fulfilments. The total time spent building, deploying, identifying, and correcting the issues is approximately four hours, most of which would have been eliminated by a plan and validation step before the manifest was written.

Solution Overview

Building a new UI page starts with a plain-language description of what the page needs to show. The tool evaluates that description against the available out-of-the-box components and presents a plan covering the route structure, component hierarchy, data query, and composition pattern before any output is generated. This review step is valuable for developers at both ends of the experience spectrum: newer developers get a clear picture of how the framework thinks about the problem, while experienced developers can catch anything that needs adjusting before committing to the build.Once the plan is approved, the manifest JSON definition is generated automatically, with components assembled in the correct structure. A validation step runs immediately after to confirm the output is sound before it is used.The result is a complete, deployment-ready page definition produced without manual JSON authoring and without needing to know from memory which components to use or how to arrange them.

Solution