A project is structured in Stages. Stages contain layout, media and other components. And some of these components… also have stages.
Confused? Worry not, just keep reading.
When you start a new project, and arrive at the Editor you will always see an initial Page Stage. This is where the experience you are creating will always start.
You can later add more Page Stages to your project, but more often than not you will only need the intial Page Stage.
Let’s say you have chosen a template. You will often find that among the layout, media and other components of the initial Page Stage… there is a marketing app.
Marketing Apps also have stages, and they also have an initial stage (such as the first question of a Quiz).
Here are a few examples to explain what app stages are:
- a Quiz app will have Questions, which are stages, and a final Score stage
- a Personality Test app will have Questions (stages) and a Personality stage for each personality you configure
- and a Calculator app will have a sequence of Input stages up to a Result Stage
When you are editing an app, you can create, clone, delete and rename its stages. But to get there, you must first know how to navigate the Editor.
What Controls Which Stage To Show?
Actions! You can use actions to manipulate which stage to show.
Every component that has stages will have “Go to stage” actions available. You can use those actions to tell the component to go to a certain stage.
You can also use the actions “Navigate: Back” and “Navigate: Forward” to switch between previously visited stages. This is the same pattern as browser’s pages where you can go back and forward between the pages you visited.
And although most templates already include the logic needed for their stages, there are situations where you for example may want to tweak the default logic.
Example: you want to add a Lead Form gate after all the questions of a Quiz, but before the results are shown.