public-speaking-presentation

bygrace

INTRODUCTION This seventh module is designed as a comprehensive review of the foundational skills covered in Units 1-4, serving as your essential preparation for the midterm examination. We will revisit the core principles of public speaking, from overcoming stage fright and analyzing your audience to mastering the PEEP framework for persuasive delivery. By revisiting these early lessons, you will consolidate your ability to structure clear, impactful messages and deliver them with confidence. This content is based on Successful Presentations (pp. 4–27). ABSTRACT  Success in public speaking is built upon a solid foundation of preparation, audience awareness, and structural clarity. This seventh module provides a comprehensive review of the core concepts explored in Units 1-4 prior to midterm test. Students will revisit the core structure, the ABCD model, the PEEP principle, and signposting phrases. They will also revisit strategies for managing speech anxiety and using the right body language. By consolidating these essential skills, students will be confident to deliver well-organized and impactful presentations that resonate with listeners in professional and academic settings. PURPOSE Students are able to demonstrate readiness for the midterm test by identifying key concepts from Units 1-4. Students are able to construct a professional presentation by integrating several key elements, including the core structure, the ABCD model, the PEEP principle, and signposting phrases. Students are able to support their claims with clear examples. Students are able to handle public speaking anxiety and use the proper body language for their midterm test presentation. REFERENCES Hughes, J. and Mallet, A. (2012). Successful Presentation. Cambridge University Press Drafting Your Presentation Before stepping in front of an audience, the most critical step is organizing your ideas into a logical flow. Structuring your presentation using The Core Structure allows you to bridge the gap between having raw information and delivering a clear, persuasive message. By focusing on a core structure, you ensure that your delivery is not only professional but also easy for your audience to follow and remember. The Core Structure of a Presentation The Core Structure is a fundamental framework for any successful talk. A professional presentation is built on a solid three-part foundation. You can think of this as a strategic roadmap that ensures your audience stays engaged from start to finish. 1. Introduction (Greeting & Attention-Getter) The primary function of this section is to capture the audience’s interest, introduce yourself, and clearly state your purpose. You can begin with a formal greeting, followed by a hook such as a compelling story, a relatable question, a surprising statistic, or a relevant anecdote to draw the audience in. Finally, always provide a brief road map or outline of the points you intend to cover so the audience knows what to expect. 2. Key Messages (The Body) This section is designed to deliver your main arguments or information in digestible chunks. A common and effective strategy is the “Rule of Three”, which suggests that audiences are most likely to remember information presented in groups of three. While you may include more points if necessary, it is best to limit yourself to no more than 5 key messages. Research suggests that general audiences often remember only about 20% of a presentation, so keep your points focused. Ensure each message is supported by a solid fact, a clear example, or a relevant visual aid. 3. The Conclusion (The Recap & Call to Action) The conclusion serves to reinforce or recap your main points and leave a lasting impression. This final section should include a concise summary of your key messages and a clear call to action. Tell your audience exactly what you want them to do, feel, or think next based on the information you have shared. End with a strong closing statement to wrap up your presentation confidently. A - Get the Audience’s ATTENTION Before we even speak, we can get the audience's attention using non-verbal communication. Stand confidently: Relax your shoulders and stand tall. Make eye contact: Look at your audience and smile. Pause: Wait a moment before you start talking to create interest. Once you start talking, you can: Ask a question to the audience. Show a strong visual image or a picture. Tell a short story or mention a current news event. B - Explain the BENEFITS This is the most important part! The audience needs to know why they should listen. Explain how your presentation will help them. Show that you understand their values and concerns. Answer the question: “What is in it for me?” C - Establish your CREDIBILITY Why are you the right person to give this presentation? Share your experience or knowledge about the topic. Show that you have researched the information well. Connecting with your audience’s world helps them trust you. D - Provide DIRECTION Finally, tell the audience what to expect so they can follow your talk easily. Content: What topics will you cover? Are there any videos provided? Structure: How is the presentation organized? Timing: Tell them when they can ask questions (e.g., at the end of the talk). Using Positive Body Language in a Presentation Body language is a powerful way to communicate without using words. It plays a major role in how an audience feels about our presentation. Using our body effectively helps the audience follow the flow of our talk because our movements can act like a map for the listeners. For instance, moving to a different spot on the stage or using a hand gesture can signal that we are moving to the next part of our message. In addition to providing a clear structure, body language serves as a tool for emphasis to highlight the most important points. When a specific idea is significant, we can use our hands or a change in posture to show its value, which helps the audience remember the key information. Finally, positive body language is a way to stay connected and keep the audience interested throughout the session. When we look at people and smile, they feel more engaged and are much more likely to listen to what we have to say. We can use these five types of body language to improve our presentations and build better connections with our audience: Eye Contact: We should look at our audience to build trust and make them feel included in the conversation. Hand Gestures: We can use our hands to describe sizes, show emotions, or emphasize a point. It is important not to cross our arms. Instead, we should use open hand gestures to show that we are open and friendly. Movement: We can walk purposefully to different areas of the room to keep the energy high. However, we should not move too much, as this might distract our audience from the message. Posture: We should avoid slouching or looking tired. Instead, stand tall and keep an open posture to show confidence and a positive attitude. Facial Expressions: Give smiles and friendly expressions to show that we are excited and happy to share our topic with them.

LandingLoginSign UpReadiness CheckModule ReviewPresentation DraftSubmissions
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Successful Presentations

1. Introduction

Successful Presentations is a seventh-module review application for a university public-speaking course. It exists to prepare students for the midterm examination by consolidating the foundational skills covered in Units 1–4: the three-part core structure of a presentation, the ABCD model, the PEEP principle, signposting phrases, strategies for managing speech anxiety, and positive body language. The module content is based on Successful Presentations (Hughes & Mallet, 2012, pp. 4–27).

The product serves two audiences. Student presenters revisit the core concepts, construct a professional presentation that integrates the core structure, the ABCD model, the PEEP principle and signposting phrases, support their claims with clear examples, and demonstrate readiness for the midterm by identifying key concepts from Units 1–4. Course instructors assign the review module, check student readiness, and review submitted presentations for structure, examples and delivery.

The intent is confidence and clarity: students consolidate their ability to structure clear, impactful messages and deliver them with confidence in academic and professional settings.

Page 1 of 27

2. System Overview

Successful Presentations is a web application delivered as three provisioned services: a React frontend, a shared FastAPI backend that hosts all application APIs and domain modules, and a MariaDB database for application-owned persistent data. Students and instructors reach the module through an anonymous public entry, establish or verify an application-owned identity, and then work within role-restricted module surfaces. Students review the Units 1–4 concepts, draft a presentation against the required models with supporting examples, and complete a readiness check; instructors review the resulting submissions.

2a. Product Interpretation and Delivery Boundary

The application owns identity and durable state. A visitor can read the public entry without an account. A student creates an account through self-service enrollment; a returning student or an instructor verifies identity at login. Protected module work — review, drafting, readiness checking, and submission review — is available only after identity is established, and each protected surface is restricted to the role that owns it: students own Module Review, Presentation Draft and Readiness Check; instructors own Submissions.

All current behavior is delivered first-party by this application. There are no provider-owned or external destinations in the current scope, and no headless delivery. The module is a review and preparation tool for the midterm; it does not administer the midterm examination itself, and it does not add course-management capabilities beyond the accepted review, drafting, readiness and submission-review lifecycles.

Page 2 of 27

2b. Source Content Inventory

The module's authoritative content is drawn from Successful Presentations (Hughes & Mallet, 2012, pp. 4–27). The following facts, frameworks, and items must be preserved in the product.

Reference

  • Hughes, J. and Mallet, A. (2012). Successful Presentation. Cambridge University Press.

The Core Structure of a Presentation — a three-part foundation:

  1. Introduction (Greeting & Attention-Getter) — capture the audience's interest, introduce yourself, and clearly state your purpose. Begin with a formal greeting, followed by a hook such as a compelling story, a relatable question, a surprising statistic, or a relevant anecdote. Always provide a brief road map or outline of the points you intend to cover.
  2. Key Messages (The Body) — deliver main arguments or information in digestible chunks. The "Rule of Three" suggests audiences remember information best in groups of three; you may include more points if necessary, but limit yourself to no more than 5 key messages. Research suggests general audiences often remember only about 20% of a presentation, so keep points focused. Ensure each message is supported by a solid fact, a clear example, or a relevant visual aid.
  3. The Conclusion (The Recap & Call to Action) — reinforce or recap main points and leave a lasting impression. Include a concise summary of key messages and a clear call to action telling the audience exactly what to do, feel, or think next. End with a strong closing statement.
Page 3 of 27

The ABCD Model

  • A — Get the Audience's ATTENTION. Before speaking, use non-verbal communication: stand confidently (relax your shoulders and stand tall); make eye contact (look at your audience and smile); pause (wait a moment before you start talking to create interest). Once talking, you can ask a question to the audience, show a strong visual image or picture, or tell a short story or mention a current news event.
  • B — Explain the BENEFITS. The most important part: the audience needs to know why they should listen. Explain how your presentation will help them, show that you understand their values and concerns, and answer the question "What is in it for me?"
  • C — Establish your CREDIBILITY. Why are you the right person to give this presentation? Share your experience or knowledge about the topic, show that you have researched the information well, and connect with your audience's world to help them trust you.
  • D — Provide DIRECTION. Tell the audience what to expect: Content (what topics will you cover? are there any videos provided?), Structure (how is the presentation organized?), and Timing (tell them when they can ask questions, e.g., at the end of the talk).
Page 4 of 27

Using Positive Body Language in a Presentation — body language communicates without words, helps the audience follow the flow of the talk (movements act like a map), serves as a tool for emphasis, and keeps the audience connected and interested. Five types:

  • Eye Contact — look at your audience to build trust and make them feel included in the conversation.
  • Hand Gestures — use your hands to describe sizes, show emotions, or emphasize a point. Do not cross your arms; use open hand gestures to show you are open and friendly.
  • Movement — walk purposefully to different areas of the room to keep the energy high, but do not move too much, as this might distract your audience from the message.
  • Posture — avoid slouching or looking tired; stand tall and keep an open posture to show confidence and a positive attitude.
  • Facial Expressions — give smiles and friendly expressions to show you are excited and happy to share your topic.

Additional reviewed concepts — overcoming stage fright, analyzing your audience, and the PEEP framework for persuasive delivery.

2c. Page Content and Component Coverage

Page 5 of 27

Landing

  • Information/state: Anonymous public entry. Product name "Successful Presentations"; hero headline "Speak with a structure that holds"; subline "Review the core structure, the ABCD model and body language before your midterm."; call to action "Start review". Explains the Units 1–4 review module and its midterm-preparation purpose.
  • Primary action: "Start review" leads to Sign Up (new student) or Login (returning student or instructor).
  • Supporting actions: Navigate to Login; navigate to Sign Up.
  • Domain entities: Module description (static content).
  • Component responsibilities: Full-bleed black hero band with stacked uppercase headline and CTA; cropped monochrome speaker photograph with red vertical rule; numbered section labels; section openers introducing the core structure, ABCD model and body-language review.
  • States: Loading (static content renders immediately); empty/success not applicable; error (content unavailable → retry); recovery (retry or proceed to Sign Up/Login).
Page 6 of 27

Sign Up

  • Information/state: Anonymous self-service enrollment for a student presenter. Collects the identity details needed to create an account and binds the new account to the student role.
  • Primary action: Create account → on success, student enters Module Review.
  • Supporting actions: Navigate to Login if already enrolled.
  • Domain entities: Student account (identity, role = student).
  • Component responsibilities: Enrollment form; validation messaging; role assignment on creation.
  • States: Loading (submitting); empty (blank form); success (account created, redirect to Module Review); error (invalid or incomplete details, or account already exists → message and link to Login); recovery (correct and resubmit).

Login

  • Information/state: Anonymous verification for a returning student or an instructor.
  • Primary action: Verify identity → student lands on Module Review; instructor lands on Submissions.
  • Supporting actions: Navigate to Sign Up (students without an account).
  • Domain entities: Account (identity, role).
  • Component responsibilities: Credential form; role-aware routing after verification.
  • States: Loading (verifying); empty (blank form); success (routed by role); error (invalid credentials → message, retry); recovery (retry or go to Sign Up).
Page 7 of 27

Module Review

  • Information/state: Role-restricted to students. Presents the Units 1–4 review content: the three-part core structure, the ABCD model, the PEEP principle, signposting phrases, strategies for managing speech anxiety, and the five types of positive body language.
  • Primary action: Read and move through the review sections; continue to Presentation Draft.
  • Supporting actions: Jump between review sections via numbered labels; continue to Readiness Check.
  • Domain entities: Review sections and their content items (core structure parts, ABCD letters, PEEP, signposting phrases, anxiety strategies, body-language skills).
  • Component responsibilities: Section openers (full-bleed black band, white serif reading text); ABCD four hard-edged letter tiles in a single row on black; body-language list as one wide ruled row per skill with the skill name in heavy grotesk; red vertical rule with numbered label marking each section change.
  • States: Loading (content fetch); empty (content unavailable → message); success (all sections readable); error (fetch failure → retry); recovery (retry).
Page 8 of 27

Presentation Draft

  • Information/state: Role-restricted to students. A durable, student-owned draft of a presentation that integrates the core structure (Introduction with greeting and attention-getter, Key Messages body, Conclusion with recap and call to action), the ABCD model, the PEEP principle and signposting phrases, with each claim supported by a clear example.
  • Primary action: Compose and save the draft.
  • Supporting actions: Edit sections; add supporting examples per claim; submit the draft for instructor review.
  • Domain entities: Presentation draft (owned by the student; sections; key messages; ABCD elements; PEEP elements; signposting phrases; claims with examples; submission status).
  • Component responsibilities: Sectioned editor mapped to the core structure; ABCD and PEEP entry areas; signposting-phrase entry; per-claim example fields; save and submit controls; status indicator.
  • States: Loading (draft fetch); empty (new draft with section scaffolding); success (saved; submitted); error (save/submit failure → message, retry); recovery (retry; unsaved changes preserved in the editor).
Page 9 of 27

Readiness Check

  • Information/state: Role-restricted to students. A check in which the student identifies key concepts from Units 1–4 to demonstrate readiness for the midterm test.
  • Primary action: Answer the concept-identification items and submit the check.
  • Supporting actions: Review results; return to Module Review to revisit weak concepts.
  • Domain entities: Readiness check attempt (owned by the student; items; responses; result).
  • Component responsibilities: Item presentation; response controls; result summary; link back to Module Review.
  • States: Loading (items fetch); empty (no items available → message); success (result shown); error (submission failure → retry); recovery (retry; revisit Module Review).
Page 10 of 27

Submissions

  • Information/state: Role-restricted to the course instructor. Lists student presentation drafts submitted for review, with each student's readiness status.
  • Primary action: Open a submission and review it for structure, examples and delivery.
  • Supporting actions: Move between submissions; record review outcome.
  • Domain entities: Submission (student, draft content, readiness status, review outcome).
  • Component responsibilities: Submission list; submission detail view showing the draft's structure, examples and delivery notes; review-outcome control.
  • States: Loading (list fetch); empty (no submissions yet → message); success (list and detail render); error (fetch or save failure → retry); recovery (retry).
Page 11 of 27

3. Functional Requirements

FR-1 — Review the Units 1–4 foundational skills. As a student presenter, I should review the foundational skills from Units 1–4 as preparation for the midterm examination, so that I consolidate the core principles of public speaking. (explicit)

  • Trigger: student opens Module Review after login.
  • Observable result: the review content for Units 1–4 is presented.
  • Failure/recovery: content fetch failure shows a message with retry.
  • Continuation: student proceeds to Presentation Draft or Readiness Check.

FR-2 — Identify key concepts to show readiness. As a student presenter, I should identify key concepts from Units 1–4 to demonstrate readiness for the midterm test. (explicit)

  • Trigger: student opens Readiness Check and submits responses.
  • Observable result: a result is shown reflecting the student's concept identification.
  • Failure/recovery: submission failure shows a message with retry; the student may return to Module Review.
  • Continuation: result is available to the instructor in Submissions.
Page 12 of 27

FR-3 — Construct a professional presentation integrating the required models. As a student presenter, I should construct a professional presentation that integrates the core structure, the ABCD model, the PEEP principle and signposting phrases. (explicit)

  • Trigger: student composes a draft in Presentation Draft.
  • Observable result: a saved, student-owned draft containing the core structure, ABCD elements, PEEP elements and signposting phrases.
  • Failure/recovery: save failure shows a message with retry; unsaved edits remain in the editor.
  • Continuation: student submits the draft for instructor review.

FR-4 — Support claims with clear examples. As a student presenter, I should support my claims with clear examples. (explicit)

  • Trigger: student adds a supporting example to each claim in the draft.
  • Observable result: each claim carries a clear example in the saved draft.
  • Failure/recovery: save failure shows a message with retry.
  • Continuation: examples are visible to the instructor in Submissions.

FR-5 — Handle public speaking anxiety and use proper body language. As a student presenter, I should handle public speaking anxiety and use the proper body language for my midterm test presentation. (explicit)

  • Trigger: student reviews the anxiety-management strategies and the five body-language skills in Module Review.
  • Observable result: the strategies and the five skills (eye contact, hand gestures, movement, posture, facial expressions) are presented for the student's preparation.
  • Failure/recovery: content fetch failure shows a message with retry.
  • Continuation: student applies the guidance while drafting and preparing.
Page 13 of 27

FR-6 — Cover the three-part core structure. As a student presenter, I should learn the three-part core structure — Introduction with greeting and attention-getter, Key Messages body, and Conclusion with recap and call to action. (explicit)

  • Observable result: all three parts and their guidance are presented in Module Review and reflected in the draft's section scaffolding.

FR-7 — Cover the ABCD model. As a student presenter, I should learn the ABCD model — Attention, Benefits, Credibility and Direction. (explicit)

  • Observable result: all four letters with their guidance are presented in Module Review and available as draft entry areas.

FR-8 — Cover the five types of positive body language. As a student presenter, I should learn the five types of positive body language — eye contact, hand gestures, movement, posture and facial expressions. (explicit)

  • Observable result: all five skills with their guidance are presented in Module Review.

FR-9 — Attribute content to the source. As a student presenter, I should see that the module content is based on Successful Presentations (pp. 4–27) by Hughes and Mallet (2012). (explicit)

  • Observable result: the reference is shown with the module content.

FR-10 — Self-service enrollment. As a student presenter, I should complete self-service enrollment before protected module work. (required_inference)

  • Trigger: visitor selects "Start review" on Landing and chooses Sign Up.
  • Observable result: an account bound to the student role is created and the student enters Module Review.
  • Failure/recovery: invalid or duplicate account shows a message and a link to Login.
  • Continuation: student proceeds to Module Review.
Page 14 of 27

FR-11 — Returning verification. As a returning student or instructor, I should complete verification before protected module work. (required_inference)

  • Trigger: visitor opens Login and submits credentials.
  • Observable result: identity verified; student routed to Module Review, instructor routed to Submissions.
  • Failure/recovery: invalid credentials show a message with retry.
  • Continuation: role-appropriate protected work.

FR-12 — Instructor role assignment. As a course instructor, I should have an assigned instructor role before submission review. (required_inference)

  • Observable result: the instructor account carries the instructor role and reaches Submissions after login.

FR-13 — Review student submissions. As a course instructor, I should review student presentations for structure, examples and delivery. (required_inference)

  • Trigger: instructor opens Submissions and selects a submission.
  • Observable result: the submission's draft content and readiness status are shown; the instructor records a review outcome.
  • Failure/recovery: fetch or save failure shows a message with retry.
  • Continuation: instructor moves to the next submission.

4. User Personas

Page 15 of 27

Student presenter

  • Product context: A university student enrolled in a public-speaking course, preparing for the midterm examination. The seventh module is their review of Units 1–4.
  • Primary goal: Demonstrate readiness for the midterm by identifying key concepts from Units 1–4 and by constructing a professional presentation that integrates the core structure, the ABCD model, the PEEP principle and signposting phrases, with claims supported by clear examples.
  • Distinct responsibilities: Reads and consolidates the review content (core structure, ABCD, PEEP, signposting, anxiety strategies, body language); composes and saves a durable presentation draft; adds a clear example to each claim; submits the draft; completes the readiness check.
  • Inputs and decisions: Chooses a hook for the Introduction (story, question, statistic, anecdote); limits key messages to no more than 5 (Rule of Three preferred); decides the call to action; selects signposting phrases; decides which examples support each claim.
  • Interactions with other participants: Submits the draft and readiness result to the course instructor for review.
  • Observable success: A saved, submitted draft containing all required models and per-claim examples, and a readiness-check result, both visible to the instructor.
Page 16 of 27

Course instructor

  • Product context: The instructor of the public-speaking course who assigns the seventh review module and checks student readiness for the midterm.
  • Primary goal: Confirm that students are ready for the midterm and that their presentations meet the required structure, examples and delivery standards.
  • Distinct responsibilities: Reviews submitted student presentations for structure, examples and delivery; records a review outcome; sees each student's readiness status.
  • Inputs and decisions: Judges whether the core structure, ABCD model, PEEP principle and signposting phrases are integrated; whether claims carry clear examples; whether delivery guidance (anxiety management, body language) is reflected.
  • Interactions with other participants: Reads student presenters' submitted drafts and readiness results.
  • Observable success: Each submission reviewed with a recorded outcome; readiness status visible per student.

5. Core User Flows

Page 17 of 27

Flow A — New student enrolls and begins review

  1. Visitor opens Landing and reads the module purpose and hero copy.
  2. Visitor selects Start review and chooses Sign Up.
  3. Student completes self-service enrollment on Sign Up; the account is created with the student role.
  4. Student lands on Module Review and begins reading the Units 1–4 content.
  5. Failure/recovery: invalid or duplicate details show a message and a link to Login; the student corrects and resubmits.

Flow B — Returning student or instructor verifies identity

  1. Visitor opens Login.
  2. Student or instructor submits credentials.
  3. On success, a student is routed to Module Review; an instructor is routed to Submissions.
  4. Failure/recovery: invalid credentials show a message; the visitor retries or, if a student without an account, goes to Sign Up.
Page 18 of 27

Flow C — Student reviews the Units 1–4 concepts

  1. Student opens Module Review.
  2. Student reads the three-part core structure (Introduction with greeting and attention-getter; Key Messages body with the Rule of Three and the limit of no more than 5 key messages, each supported by a fact, example or visual aid; Conclusion with recap and call to action).
  3. Student reads the ABCD model as four letter tiles: Attention (stand confidently, make eye contact, pause; then ask a question, show a strong image, or tell a story or current news event), Benefits (explain how the presentation helps, show understanding of values and concerns, answer "What is in it for me?"), Credibility (share experience and knowledge, show research, connect with the audience's world), Direction (Content, Structure, Timing).
  4. Student reads the PEEP principle and signposting phrases, and the strategies for managing speech anxiety.
  5. Student reads the five body-language skills, one ruled row each: eye contact, hand gestures (open, not crossed), movement (purposeful, not excessive), posture (tall, open, not slouching), facial expressions (smiles, friendly).
  6. Student continues to Presentation Draft or Readiness Check.
  7. Failure/recovery: content fetch failure shows a message with retry.
Page 19 of 27

Flow D — Student drafts the presentation with examples

  1. Student opens Presentation Draft; a new draft shows section scaffolding, or an existing draft loads.
  2. Student composes the Introduction with a formal greeting, a hook and a road map.
  3. Student composes Key Messages, limiting to no more than 5, each supported by a fact, example or visual aid.
  4. Student composes the Conclusion with a recap and a clear call to action and a strong closing statement.
  5. Student fills the ABCD elements, the PEEP elements and signposting phrases.
  6. Student adds a clear example to each claim.
  7. Student saves the draft; on save failure a message appears and unsaved edits remain for retry.
  8. Student submits the draft for instructor review; the submission appears in Submissions.

Flow E — Student completes the readiness check

  1. Student opens Readiness Check.
  2. Student identifies key concepts from Units 1–4 by answering the items.
  3. Student submits the check; a result is shown.
  4. Failure/recovery: submission failure shows a message with retry; the student may return to Module Review to revisit weak concepts.
  5. Continuation: the readiness result is visible to the instructor in Submissions.
Page 20 of 27

Flow F — Instructor reviews submissions

  1. Instructor logs in and lands on Submissions.
  2. Instructor sees the list of submitted student drafts with each student's readiness status.
  3. Instructor opens a submission and reviews it for structure, examples and delivery.
  4. Instructor records a review outcome; on save failure a message appears and the instructor retries.
  5. Instructor moves to the next submission.
  6. Empty state: when no submissions exist, a message is shown.
Page 21 of 27

6. Visuals Colors and Theme

Authoritative creative direction: editorial confidence after Tobias van Schneider — oversized type, one hot accent, sharp edges, no softness.

Palette (light mode)

  • Background: #F4F0E8 (warm off-white ground)
  • Surface: #FFFFFF
  • Text: #101010
  • Primary: #101010
  • Accent: #E8341C (red; used on less than 10% of the area — one element per screen)
  • Muted: #8A857C

Typography

  • Headings: Archivo Black — heavy grotesk, tight uppercase for display lines.
  • Body: Newsreader — light serif for reading text.
  • Scale: 1.5 modular — 56 / 40 / 28 / 20 / 16 px.
  • Display headline: clamp(56px, 12vw, 160px).

Shape language: Sharp corners, hard edges, full-bleed colour blocks. No rounded cards, no soft shadows.

Layout: Asymmetric editorial grid — a wide left column for display type, a narrow right column for small numbered labels.

Imagery: Large monochrome photographs of a speaker on a stage, cropped hard at the edge, with one accent bar cutting the frame.

Motion: Slow crossfades and word-by-word type reveals; hover swaps a small image; nothing bounces.

Page 22 of 27

Readability rule: Headlines, wordmarks, labels, numbers, card text and controls stay entirely inside the viewport and their container at 375px, 768px and 1280px, wrapping or scaling to fit; imagery and decoration may be cropped or bled off edges instead.

7. Signature Design Concept

The public entry (Landing) is a full-bleed black band on the left holding the stacked uppercase headline "Speak with a structure that holds" at clamp(56px, 12vw, 160px), spanning the viewport height. A red vertical rule separates it from a hard-cropped monochrome photograph of a speaker on a stage on the right. The subline "Review the core structure, the ABCD model and body language before your midterm." sits in white serif beneath the headline, and the "Start review" call to action sits under it in white on black. A small numbered label rides the red rule. The composition recomposes only accepted content and the accepted entry action — it introduces no new behavior.

Page 23 of 27

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat

Landing Hero Motion Brief

  • Focal subject: the stacked uppercase headline against the black band, with the cropped speaker photograph on the right.
  • Thesis: on load, the headline reveals word by word (input) → the red vertical rule draws down and the photograph crossfades in (transformation) → the composed first frame settles with the CTA visible (outcome).
  • Motion vocabulary: slow crossfades, word-by-word type reveals, a hover swap of the small photograph; nothing bounces.
  • Composed first frame: black band left, red rule, cropped photograph right, headline fully legible, CTA under the headline.
  • Reduced-motion state: all elements appear immediately in their final positions; the hover image swap is disabled and the static photograph remains.
Page 24 of 27

9. Non-Functional Requirements

  • Source fidelity: Module content must faithfully reproduce the Units 1–4 concepts from Successful Presentations (pp. 4–27), including the Rule of Three, the limit of no more than 5 key messages, the ~20% retention note, all four ABCD letters, and all five body-language skills with their do/don't guidance. (explicit)
  • Durable state: Student drafts, readiness results and instructor review outcomes persist in MariaDB and are bound to the correct account. (required_inference)
  • Access control: Module Review, Presentation Draft and Readiness Check are restricted to the student role; Submissions is restricted to the instructor role; Landing, Sign Up and Login are anonymously reachable. (required_inference)
  • Readability: Text and controls remain whole and inside their containers at 375px, 768px and 1280px. (explicit, from creative direction)
  • Accessibility: A usable static arrangement is provided under prefers-reduced-motion. (explicit, from creative direction)
  • Visual constraints: No rounded cards with soft shadows, no blue or indigo accents, no gradient blobs, no centred hero with a small button, no pastel colours, no decorative icons. (explicit, from creative direction)
Page 25 of 27

10. Tech Stack

  • Frontend: React application UI.
  • Backend: shared FastAPI process hosting all application APIs and domain modules (identity, review content, drafts, readiness checks, submissions).
  • Database: MariaDB for application-owned persistent data.
  • Deployment: Docker/docker-compose with the three provisioned services (frontend, backend, database).

11. Assumptions and Constraints

  • The module is a review of Units 1–4 and serves as preparation for the midterm examination; it does not administer the midterm itself. (explicit)
  • Content is based on Successful Presentations (pp. 4–27). (explicit)
  • Identity is application-owned; students self-enroll and returning users verify at login. (required_inference)
  • The instructor role is assigned to instructor accounts before submission review. (required_inference)
  • The PEEP principle and signposting phrases are named in the source as reviewed concepts; their detailed content is presented as part of the Units 1–4 review. (explicit)
  • No provider-owned or external destinations are in current scope.
Page 26 of 27

12. Glossary

  • Core Structure — the three-part presentation foundation: Introduction (greeting and attention-getter), Key Messages (body), Conclusion (recap and call to action).
  • ABCD Model — Attention, Benefits, Credibility, Direction.
  • PEEP — the persuasive-delivery framework reviewed from Units 1–4.
  • Signposting phrases — verbal cues that guide the audience through a presentation's structure.
  • Rule of Three — the guidance that audiences best remember information presented in groups of three.
  • Readiness Check — the student activity of identifying key concepts from Units 1–4 to demonstrate midterm readiness.
  • Submission — a student's submitted presentation draft reviewed by the course instructor.
Page 27 of 27
Live
Landing design preview
Landing: Read module purpose
Login: 1. Verify instructor identity
Login: 2. Retry credentials
Submissions: View submission list
Submissions: 1. Open a submission
Submissions: 2. Review structure and examples
Submissions: 3. Check readiness status
Submissions: 4. Record review outcome
Submissions: 5. Retry save
Submissions: 6. Move to next submission
Live
Landing design preview
Landing: Read module purpose
Login: 1. Verify instructor identity
Login: 2. Retry credentials
Submissions: View submission list
Submissions: 1. Open a submission
Submissions: 2. Review structure and examples
Submissions: 3. Check readiness status
Submissions: 4. Record review outcome
Submissions: 5. Retry save
Submissions: 6. Move to next submission