GuidedTrack Docs

Page Breaks🔗

Often, the program content that is displayed to users will not be presented all at once. There are some instances in which a page break will occur automatically, requiring that users push a button to be shown the next segment of the program. Page breaks are caused automatically by questions, buttons, and the *page keyword (a method of putting multiple questions on one screen, click the link to learn more).

Questions🔗

Each time you ask the user a question, the remaining content of your program will not be displayed until the question is answered.

*question: Is a fork happier than a boat?
Thank you!

In this example, the users will see a question on their screen, but nothing below it. Once they answer it, the question and anything else on the screen with it will disappear. They will then see the text "Thank you!"

Buttons🔗

If you have a lot of text, you may want to break some of it up by adding a *button keyword. The text of your button can be anything you like, such as "Next," "Continue," "Read More" or "Duck and cover!" and should be written as *button: text. Here's an example:

That was a lof of information! Let's move onto the next lesson.
*button: Yippee, let's go!
All about ham sandwiches.

In this example, users will be shown the first sentence, then they will see the button "Yippee, let's go!" Once clicked, the button and the first sentence will disappear, and the second sentence will be displayed.

The Clear Keyword🔗

The *clear keyword does not force a button to appear on the page, though it is a method of removing old content that is on the screen to make way for new content. To learn more about the *clear keyword, click here.