Key features that make up the main value proposition for Lore


Wizards are a complex multi-step version of a form. And similar to dialogs, while the behavior of wizards tends to be fairly similar across applications, the visual appearance and content can drastically based on an application's branding.

Because of that, Lore doesn't provide a built-in solution for wizards per se, but there's a side-project called lore-forms that illustrates some patterns for building wizards that you may find helpful. It also includes implementations of those patterns for the Bootstrap and Material UI component libraries.

You can read more about lore-forms here.

However, wizards do have some common needs that Lore accounts for. For example, sometimes you have a wizard that creates data, and needs to wait until the server confirms that data is created before moving on to the next step, or display an error to the user if there was a problem creating the data.

Being able to solve that problem simply, without requiring components to make those server calls directly, and being done in a way that also functions properly in a real-time app is non-trivial. But a solution can be found in the overlap between Optimistic Updates (using client-side ids) and the Data Structure used by Lore that supports Visual Cues and Error Handling.