Learning path · Level 6 · Tutorial 1

Draft a Landing Page That Matches Visitor Intent

Draft an annotated landing-page outline that fulfills an incoming message's promise, presents a clear offer, and guides visitors toward one accessible, well-supported action. Practice uses text rather than a live website.

  • Level: Intermediate
  • Duration: 18 min
  • 8 steps
Start tutorial Back to the path
Draft a Landing Page That Matches Visitor Intent

What you will go through

  1. Define the Promise and the Primary Action Identify the visitor, promised resource, and completed action that anchor a focused landing page. 2 min
  2. Find and Repair Message Mismatches Compare a fictional incoming message with landing-page elements, then repair audience, offer, and action mismatches without changing the promise. 2 min
  3. Arrange the Page Around Visitor Questions Order a ClearWeek landing page so the offer and primary action appear before the supporting detail. 2 min
  4. Support Claims and Answer Real Concerns Use relevant, clearly labeled evidence and known facts to support the fictional ClearWeek landing-page draft without inventing outcomes or praise. 2 min
  5. Keep One Action in Focus Keep the fictional ClearWeek landing page centered on the action promised by its incoming message, without hiding useful support. 2 min
  6. Specify the Smallest Useful Form Specify the minimum information needed to request the fictional ClearWeek free weekly planning template, plus clear expectations before and after a successful request. 2 min
  7. Annotate Accessible Reading and Interaction Add concrete accessibility requirements to the fictional ClearWeek landing-page structure and request flow. 2 min
  8. Finish and Review Your Landing-Page Draft Complete and review a coherent annotated text wireframe that fulfills the incoming promise and supports one accessible action. 3 min

What you will learn

  • Compare an incoming message with a proposed landing page and identify mismatches in audience, offer, or expected action.
  • Draft a text wireframe that orders the offer, benefits, proof, objections, and primary call to action.
  • Choose credible evidence for the page's main claims without inventing testimonials or results.
  • Specify essential form fields, accessible interaction requirements, and what visitors should expect after acting.

Before you start

  • Build an Evidence-Informed Persona and Value Proposition
  • Map a Customer Journey and Marketing Funnel
  • Write Benefit-Led Marketing Copy
  • Create Readable Marketing Visuals with Free Tools

Step 1 of 8

Define the Promise and the Primary Action

Identify the visitor, promised resource, and completed action that anchor a focused landing page.

A focused destination

Start with the incoming promise

This fictional ClearWeek scenario starts with an incoming message—not with a general company introduction.

A landing page is a focused destination for one audience need and one primary conversion action. Its job is to carry the incoming promise forward and make the next step clear.

Incoming message:
“Free weekly planning template for freelance designers. Get it by email—no account needed.”

Here, the visitor should quickly recognize the relevant resource and one clear action. A call to action (CTA) tells the visitor what that action is. For ClearWeek, the primary CTA label is Get the free template.

A click begins an action; it is not proof that delivery has succeeded. The expected delivery happens by email after a successful request.

One promised path

A social post leads to a focused landing page, then to a successful request and confirmation.

Incoming message → Landing page → Successful request → Confirmation

Create a grounded page brief

Separate facts from assumptions

Use the case facts as the boundary of your draft. Do not turn a likely visitor motivation into a guaranteed result.

Provided case facts

  • Audience: freelance designers.
  • Offer: a free weekly planning template.
  • Format: copyable plain text.
  • Conditions: no account, payment, or marketing-email enrollment.
  • Delivery: by email after a successful request.
  • Template headings: Client/project, Next task, and Due day.

A safe way to describe the audience need is: a freelance designer looking for a weekly planning resource. Claims such as “save hours,” “never miss a deadline,” or “become more productive” are not provided facts.

Example

What the case supports

| Statement | Status |
| --- | --- |
| The template is free and copyable plain text. | Provided case fact |
| It contains a weekly planning structure. | Provided case fact |
| It will save every designer time. | [Evidence needed: guaranteed time savings] |
| Freelance designers may want a simpler week. | Assumption about visitors’ needs |

Keep the landing page grounded in the first two rows. An assumption can guide later research, but it is not supported copy.

Express the promise in a text wireframe

A text wireframe is a short, numbered outline of what a landing page says and does. It specifies decisions before visual design or implementation; it is not a live website.

For this step, use brief annotations:

  1. Offer and primary CTA

Copy: Free weekly planning template for freelance designers.
Interaction: Get the free template starts the request for the same free template.

This outline names visible content and intended behavior without claiming that a visitor has already received anything.

Draft the concise brief

Practice: define the promise and action

Write a concise ClearWeek page brief in three labeled lines:

  • Audience need:
  • Offer:
  • Successful visitor action:

Use only the fictional case facts. State the action as a completed template request with expected email delivery—not merely a button click. Do not add productivity promises, payment, an account, or marketing-email enrollment.

Step 2 of 8

Find and Repair Message Mismatches

Compare a fictional incoming message with landing-page elements, then repair audience, offer, and action mismatches without changing the promise.

What must stay aligned

Message match protects the incoming promise

The fictional ClearWeek incoming message makes one connected promise:

“Free weekly planning template for freelance designers. Get it by email—no account needed.”

Message match means that the landing page preserves the substance of that promise. The wording may change, but visitors should still find:

  • the same audience: freelance designers
  • the same offer: a free weekly planning template
  • the same conditions: email delivery and no account
  • the same action: request the template by email

A polished headline is not enough if the landing page changes any of these commitments.

Trace each part of the promise

A social-post card connects by arrows to matching audience, offer, delivery, and action elements on a landing page; an account-signup card is marked as a mismatch.

Compare the incoming message with the landing page element by element—not only by headline wording.

Find the mismatch, then restore the promise

Compare the promise with the destination

Use a side-by-side check before drafting more of the landing page. A mismatch can affect the audience, resource, conditions, or requested action. The repair restores the original promise; it does not substitute a different conversion goal.

Four promise checks

The matching wording below is not required verbatim. It shows how each ClearWeek commitment can appear clearly on a landing page.

A landing page can vary its copy while keeping the incoming promise intact.
Incoming promiseMatching landing-page elementMismatchRepair
For freelance designersHeadline names freelance designers“Planning tools for every business”Name freelance designers clearly
Free weekly planning templateCopy describes a free, copyable plain-text template“Book a free planning consultation”Describe the free weekly planning template
Get it by email; no account neededRequest copy states email delivery and no account“Create an account to continue”Use an email-only request with no account
Request the templatePrimary CTA: “Get the free template”Primary CTA: “Start your account”Use the promised template-request action

Practice: match flaws to repairs

Repair the broken promise

Match each flawed landing-page element to the promise it breaks and the repair that restores it.

Tap an item and then its matching pair.

Step 3 of 8

Arrange the Page Around Visitor Questions

Order a ClearWeek landing page so the offer and primary action appear before the supporting detail.

Start with the visitor’s first questions

Use order to show hierarchy

In this fictional ClearWeek scenario, a text wireframe is a numbered outline of a landing page. It communicates what visitors encounter first, next, and later—before visual styling or implementation.

Start with the decision a visitor needs to make. The opening must quickly answer:

  • Is this for me?
  • What do I get?
  • Why might it be useful?
  • What should I do now?

For ClearWeek, the visitor is a freelance designer, the offer is a free weekly planning template, and the primary action is requesting it by email.

A visitor-question sequence

A five-part landing-page sequence: opening offer and action, benefits, a template preview, answers to questions, and a repeated action.

A useful sequence moves from the offer and primary CTA to supporting detail, then gives visitors the same action again.

Tip

Annotate the purpose of each section

This is a decision path, not a rigid universal template or a screen-height rule. If visitors need a different question answered sooner, adjust the order—but do not hide the audience, offer, or primary CTA behind later sections.

Use short annotations to separate what visitors read from what the page does:

  • Copy: visible words
  • Interaction: intended action, placement, or behavior
  • Evidence: the status of a preview or supporting material

Detailed evidence evaluation and accessibility requirements come later.

Turn the sequence into annotated sections

Example: a short ClearWeek text wireframe

The following text wireframe makes the offer and primary CTA understandable before its supporting details. It uses numbered sections rather than a visual mockup.

Example

1. Offer and primary CTA
Copy: Free weekly planning template for freelance designers. Keep each Client/project, Next task, and Due day together in copyable plain text.
Interaction: Primary CTA: Get the free template.

2. Benefits
Copy: Use the template to record the current project, its next task, and its due day for the week.

3. Preview or proof
Evidence: Illustrative preview
Copy: Client/project | Next task | Due day
Studio North website | Draft homepage outline | Tuesday

4. Questions before requesting
Copy: Free, with no account or payment. The template is delivered by email after a successful request; the email address is used for delivery only.

5. Repeat primary CTA
Interaction: Repeat the same primary CTA: Get the free template.

Tip

Keep support close to the decision

The preview helps a visitor inspect what the template contains. Its label identifies it as an Illustrative preview; deciding what evidence can support broader claims is a later task.

Order the supporting detail after the offer

Practice: sequence the page

Arrange these supplied text-wireframe sections into the most coherent order for the ClearWeek landing page.

  1. Preview or proof
  2. Benefits
  3. Offer and primary CTA
  4. Repeat primary CTA
  5. Questions before requesting

Apply the sequence to a new text wireframe

Draft the page skeleton and opening

Create a compact ClearWeek text wireframe.

  1. Write five numbered section names in a coherent order, covering the offer and primary CTA, benefits, a preview or proof, visitor questions, and a repeated primary CTA.
  2. Then draft Section 1 using both Copy: and Interaction: annotations.

Your opening must identify freelance designers, the free weekly planning template, a useful feature of the template, and the primary next step. Keep it understandable without relying on later sections.

Write at least 300 characters (0/300).

Step 4 of 8

Support Claims and Answer Real Concerns

Use relevant, clearly labeled evidence and known facts to support the fictional ClearWeek landing-page draft without inventing outcomes or praise.

Use evidence for the exact claim

Evidence must fit the claim

This fictional ClearWeek landing page can show what the free weekly planning template contains. It cannot prove an outcome that the case does not document.

Match the proof to the claim:

  • An accurate preview supports a claim about the template’s format and headings.
  • A Provided case fact supports claims about cost, account requirements, delivery, and email use.
  • A result claim needs documented results. An authentic testimonial needs a real source, permission, and useful context.

Do not turn a preview into a promise such as guaranteed productivity or time savings.

Place proof near what it supports

Diagram showing a template claim placed next to a template preview, while unrelated proof is far away on the page.

A preview is most useful beside the claim about the template’s contents, not isolated in a generic trust area.

Label evidence and answer concerns

Label what the draft can support

Use evidence-status labels in the text wireframe so readers can distinguish known facts from an example and from a gap.

Provided case fact is available for ClearWeek’s free cost, no-account requirement, copyable plain-text format, email delivery, and delivery-only email use.

Illustrative preview can show a realistic example of the template. It demonstrates the layout and headings, not a measured outcome.

For an unsupported statement, write [Evidence needed: specific claim], narrow the wording, or remove it. Never substitute fictional praise or an unsupported statistic.

Claim-to-evidence examples

These annotations could appear in the relevant numbered sections of the fictional text wireframe.

Evidence should be adjacent to the claim or concern it addresses.
Page claim or concernNearest supportStatus
The template includes three planning headingsA visible sample with the three headingsIllustrative preview
The request is free and needs no accountKnown offer conditionsProvided case fact
This template guarantees faster planningNo documented result is supplied[Evidence needed: guaranteed faster planning]

Answer relevant concerns factually

Answer concerns with facts the visitor needs to decide: what the template contains, whether it costs anything, whether an account is required, how it arrives, and how the email address is used.

For example, a numbered section can separate visible wording from behavior:

4. Request details
Copy: State the known offer conditions plainly.
Interaction: The request uses the visitor’s email address for delivery.

A concern response should clarify a real uncertainty; it should not add a benefit that ClearWeek has not established.

Practice matching claims to support

Choose support that fits

Match each fictional ClearWeek claim to the evidence status or response it needs.

Tap an item and then its matching pair.

Apply the evidence and concern rules

Add support and a concern response

Complete two additions to this fictional ClearWeek text wireframe.

  1. Add an Evidence: annotation for a preview claim. Use the correct evidence-status label and the supplied illustrative row.
  2. Add a factual response, using Copy: or Interaction:, to this visitor concern: “Do I need an account, and what happens to my email address?”

Use short numbered sections. Do not add a result promise, testimonial, or statistic.

Write at least 120 characters (0/120).

Step 5 of 8

Keep One Action in Focus

Keep the fictional ClearWeek landing page centered on the action promised by its incoming message, without hiding useful support.

Make the promised action easy to find

One promised action

The incoming message promises one thing to one audience: a free weekly planning template for freelance designers, requested by email with no account needed.

A call to action (CTA) turns that promise into an action. For ClearWeek, the primary CTA is Get the free template. It should keep that wording and refer to the same request wherever it appears.

Repeat this primary CTA when a visitor has enough context to act: near the opening offer and again after useful supporting detail. Repetition is not competition when both buttons lead to the same request.

Avoid giving unrelated goals equal emphasis, such as a webinar, a paid service, or a general account signup. Those choices can pull attention away from the promised task.

Focus versus competition

Diagram comparing a focused landing page with repeated matching primary action buttons and quiet supporting links against a crowded page with competing buttons and prominent navigation.

A focused page repeats one primary CTA after relevant context. Helpful supporting links remain available but do not compete with that action.

Place context before each CTA

Example

Annotated text wireframe example

Use a text wireframe to state where the action belongs and why. This fictional ClearWeek example keeps the incoming promise intact.

1. Offer and primary CTA
Copy: Free weekly planning template for freelance designers. Get it by email—no account needed.
Interaction: Primary CTA: Get the free template.

2. Benefits and preview
Copy: A copyable plain-text template for organizing client work and next tasks.
Evidence: Illustrative preview — Client/project | Next task | Due day; Studio North website | Draft homepage outline | Tuesday.

3. Template details and primary CTA
Evidence: Provided case fact — The template costs nothing and requires no account or payment.
Interaction: Repeat the same primary CTA: Get the free template.

4. Supporting links
Interaction: Provide quieter links for Privacy details and Help with the template. These help visitors evaluate the request without becoming alternative conversion goals.

Apply the focus rule

Choose the focused arrangement

Which page arrangement best fulfills the incoming message while keeping one action in focus?

Step 6 of 8

Specify the Smallest Useful Form

Specify the minimum information needed to request the fictional ClearWeek free weekly planning template, plus clear expectations before and after a successful request.

Keep the request focused

Request only what delivery requires

In this fictional ClearWeek scenario, ask for a field only when it is necessary to fulfill the primary CTA. The visitor is requesting a free weekly planning template by email, so an email address has a direct delivery purpose.

Do not add a field merely because it could be useful later. Marking a name or phone field “optional” does not make it necessary. The request does not need an account, payment, company details, or marketing enrollment.

Necessary versus unnecessary request fields

A comparison between a compact email-only request form and a form crowded with extra personal and account fields.

For this offer, the compact form supports delivery; extra fields do not help fulfill the request.

Field decision table

Use the stated delivery purpose to decide what belongs in the form.

ClearWeek field choices for the free template request
Potential field or requirementDelivery purposeInclude?
Email addressWhere to send the templateYes
First nameNot needed for deliveryNo
Phone numberNot needed for deliveryNo
Company detailsNot needed for deliveryNo
Account creationNot needed to request or receive itNo

Make the next step explicit

Specify the full request flow

A form should set expectations before the visitor acts, then confirm what happened afterward. In a text wireframe, specify both messages rather than assuming that a button click proves success.

Incoming message → Landing page → Successful request → Confirmation

The form and confirmation below are text specifications only. No personal data is submitted and no real email is sent in this practice.

Text wireframe: form and confirmation

  1. Offer and primary CTA

Copy: Free weekly planning template for freelance designers.
Evidence: Provided case fact — the template is copyable plain text and costs nothing.

  1. Request form

Copy: Email address
Copy: Get the free template
Interaction: Before submission, state: “Receive the free weekly planning template by email. No account or payment needed. Your email address is used for delivery only; this request does not enroll you in marketing emails.”
Evidence: Provided case fact — delivery is by email only, with no account, payment, or marketing enrollment.

  1. Successful request

Interaction: After a successful request, show: “Request received. The free weekly planning template will be delivered by email. Check your inbox.”
Evidence: Provided case fact — the template is delivered after a successful request.

Tip

Separate clicking from success

A successful-request note has two jobs: confirm that the request worked and tell the visitor what happens next. Avoid implying that clicking the primary CTA alone means delivery succeeded.

Apply the form specification

Draft the smallest useful request flow

For the fictional ClearWeek landing page, draft the request-flow specification in four labeled lines:

Fields: list only the fields or requirements to include.
Why required: explain why the included field is necessary.
Before submission: write a concise expectation note.
Successful request: write a concise confirmation and next-step note.

Use the fixed primary CTA and case facts. Do not add marketing enrollment, account creation, payment, or unsupported promises.

Write at least 180 characters (0/180).

Step 7 of 8

Annotate Accessible Reading and Interaction

Add concrete accessibility requirements to the fictional ClearWeek landing-page structure and request flow.

1. Preserve the page’s reading path

Reading order preserves meaning

Accessibility requirements make the landing page’s meaning and action available in a sensible sequence—not only in a wide visual layout.

For the fictional ClearWeek page, a visitor reading from top to bottom should understand the same path:

Incoming message → Landing page → Successful request → Confirmation

Use numbered sections and headings so the offer appears before the request details that depend on it. On a narrow screen, sections may stack, but their order should still explain who the template is for, what it is, how to request it, and what happens next.

A text wireframe can specify this intended experience. It cannot prove that a later implementation works accessibly.

A page that still makes sense when stacked

Diagram of a landing page in a logical vertical sequence: offer, supporting details, email request form, and confirmation, with a visible focus outline on a button.

The sequence keeps the offer and primary CTA understandable before the Email address request and confirmation.

2. Add interaction and form annotations

Make requirements concrete

Write accessibility requirements as explicit annotations in the text wireframe.

Descriptive links
A link should name its destination or purpose. “Click here” depends on nearby visual context; a phrase such as “Read how ClearWeek uses your email” remains meaningful when read on its own.

Visible form labels
The field needs the persistent visible label Email address, plus clear required-field information. Placeholder text can disappear when someone types and is not a label.

Keyboard behavior
Specify that links, the Email address field, and Get the free template can be reached and operated by keyboard in the same logical order as the page. Also specify a visible focus indicator so a keyboard user can tell where they are.

Example

Annotated text wireframe: sections 1–3

  1. Offer and primary CTA

Copy: Free weekly planning template for freelance designers.
Interaction: Get the free template takes the visitor to the request form.
Accessibility: This is the first heading and is read before supporting sections.

  1. Benefits and preview

Copy: Copyable plain-text template with Client/project, Next task, and Due day.
Evidence: Illustrative preview — Studio North website | Draft homepage outline | Tuesday.
Accessibility: This section follows Offer and primary CTA in the reading order.

  1. Request form

Copy: Email address — required. Get the free template.
Interaction: A successful request sends the free weekly planning template by email; the email address is used for delivery only.
Accessibility: Email address remains visibly displayed as the field label. Keyboard focus reaches the field and button in this order and is visibly indicated.

Example

Annotated text wireframe: section 4 and links

  1. Confirmation and help

Copy: Check your email for the free weekly planning template. Requesting the template does not enroll you in marketing emails.
Interaction: Show this confirmation only after a successful request.
Accessibility: The confirmation follows the request in the reading order.

Copy: Read how ClearWeek uses your email.
Accessibility: The link wording identifies its purpose without relying on its position or nearby text. Every interactive element is keyboard-operable, and its visible focus indicator remains clear.

These are intended requirements, not proof. A future implementation still needs to be checked with its actual content, keyboard behavior, and interface.

3. Separate intent from proof

Specification versus verification

Which statement accurately describes an accessibility annotation in a text wireframe?

4. Apply the accessibility requirements

Annotate the draft

Review this fictional ClearWeek draft:

  1. Request

Copy: [field placeholder: “Enter email”] [button: Get the free template]

  1. Offer and primary CTA

Copy: Free weekly planning template for freelance designers. Get it by email—no account needed.

  1. More information

Copy: Click here

Write a short accessibility annotation set for this text wireframe. Identify the inaccessible patterns, state the logical section order, provide a descriptive link purpose, specify the visible required-field information, and state keyboard and visible-focus requirements. End by distinguishing these intended specifications from verified implementation behavior.

Write at least 250 characters (0/250).

Step 8 of 8

Finish and Review Your Landing-Page Draft

Complete and review a coherent annotated text wireframe that fulfills the incoming promise and supports one accessible action.

Build the review path

Assemble one traceable draft

This final step assembles the fragments you have drafted into one coherent annotated text wireframe. It does not introduce a new page-building task.

Review the complete path:

Incoming message → Landing page → Successful request → Confirmation

At each point, check that the page asks for no more and promises no less than the incoming message: “Free weekly planning template for freelance designers. Get it by email—no account needed.”

A finished text wireframe makes the copy, evidence status, interaction behavior, and accessibility requirements explicit. It is ready for design or implementation discussion, but it does not prove usability, accessibility, or conversion performance.

Trace the promise through the page

A vertical flow from an incoming social post through Offer and primary CTA, Benefits and preview, Concerns and answers, Request form, and Confirmation, with Accessibility applying across the sequence.

Review the same path from Incoming message to Confirmation. Each section should support the one promised request.

Use the assembled reference

Reference text wireframe: offer through concerns

Use short numbered sections so the decision flow is visible before any visual design.

  1. Offer and primary CTA

Copy: Free weekly planning template for freelance designers.
Copy: Get it by email—no account needed.
Interaction: Get the free template leads to the Request form.
Accessibility: Use a clear page heading. Make the primary CTA keyboard-operable with a visible focus indicator.

  1. Benefits and preview

Copy: Use copyable plain text to organize Client/project, Next task, and Due day.
Evidence: Illustrative preview. Studio North website | Draft homepage outline | Tuesday

  1. Concerns and answers

Copy: Free. No account or payment required. Your email address is used for delivery only. Requesting the template does not enroll you in marketing emails.
Evidence: Provided case fact.
Interaction: A repeated Get the free template refers to the same Request form, not a different offer.

Reference text wireframe: request through confirmation

  1. Request form

Copy: Get the free template.
Interaction: Request only one field: Email address. Explain that the template is delivered by email after a successful request.
Accessibility: Keep the visible Email address label persistent, identify it as required, and preserve a logical keyboard order and visible focus indicator.

  1. Confirmation

Copy: Check your email for the free weekly planning template.
Interaction: Confirm that the request succeeded and state the delivery next step.
Accessibility: Make the confirmation understandable when read in sequence, including on a narrow screen.

Evidence boundary
Evidence: Evidence needed. [Evidence needed: evidence that the template improves planning outcomes.] Do not add that performance claim unless suitable evidence becomes available. The accurate preview supports what the template contains; it does not prove an outcome.

Summary

Completion criteria

Before calling the draft complete, verify that:

  • the audience, free offer, delivery method, and no-account condition still match the incoming message;
  • one primary CTA, Get the free template, remains the focused action;
  • the preview, case facts, and any evidence gap are labeled honestly;
  • the request form asks only for Email address and explains delivery and confirmation; and
  • interaction and accessibility requirements are written as requirements, not assumed outcomes.

Explicit decisions make this a useful handoff draft. They do not guarantee that a future page will be accessible, usable, or high converting.

  • Trace the incoming promise through every section.
  • Separate Copy, Evidence, Interaction, and Accessibility annotations.
  • Use Provided case fact and Illustrative preview only for the claims they support.
  • Mark unsupported claims with [Evidence needed: specific claim].
  • Treat the text wireframe as a specification, not performance proof.

Write the final annotated wireframe

Final application: present and review your draft

Create your revised ClearWeek text wireframe in short numbered sections. Include the matched offer, benefits, relevant proof, objection responses, focused primary CTA, essential form, confirmation, and accessibility requirements.

Use Copy:, Evidence:, Interaction:, and Accessibility: where relevant. Label evidence honestly. Identify one inconsistency and its repair, or state why your draft passes the consistency check. End by explicitly noting a remaining evidence gap in the required bracketed format. Do not invent testimonials, statistics, or results.

Write at least 650 characters (0/650).

Finish

Tutorial complete

Congratulations! You completed: Draft a Landing Page That Matches Visitor Intent

You completed an annotated text wireframe for the fictional ClearWeek offer. Your draft can now support a design or implementation discussion while keeping its evidence limits explicit.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate