π Lesson 5: Your First Project β Slides & the Component/Block Model
Welcome to Part 2 β the part where you stop reading about Captivate and start building. Today you'll create your very first project in the all-new Adobe Captivate, take a calm tour of the workspace, and learn the one idea that everything else rests on: a slide is built from components β reusable blocks that reflow to fit any screen. By the end you'll have a real, tiny course saved to your drive.
π What You'll Learn
By the end of this lesson, you will be able to:
- Start a new project in the all-new Adobe Captivate All-New and find your way around the workspace
- Explain the component/block model β and how slides, components, and reflow fit together
- Add and edit Text, Image, and Button components using the Visual Properties panel
- Save your work as a
.cptproject, understand autosave, and organize your files - Build a working two-slide "hello course" β a title slide and a content slide with a Next button
β±οΈ Estimated Time: 40 minutes
π― Project: Create a new project and build a 2β3 slide mini-course with a title, a line of text, an image, and a button β the first bricks of the course you'll grow all the way to the capstone.
In This Lesson
π Starting a New Project
Assuming you've installed Captivate from Lesson 2, opening the all-new Adobe Captivate All-New Trial / Paid drops you on a Home / Start screen. This is mission control: recent projects on one side, and big, friendly choices for starting something new β a blank project, a quick-start project (a ready-made template, which we'll explore in Lesson 10), or opening an existing file.
For your first build, choose blank project. Starting from nothing sounds harder, but it's actually the clearest way to learn β nothing on the screen is there unless you put it there, so every piece makes sense. Give the project a name you'll recognize later, like My First Course. The all-new tool is responsive by default, so you don't have to pick a fixed pixel size the way you would in an older tool β Captivate assumes your course should adapt to phones, tablets, and desktops, and it sets you up for that from the first click.
π§ Mindset
The blank canvas can feel intimidating β that flicker of "okayβ¦ now what?" is completely normal, and it fades the moment you drop your first component. You are not behind. Nobody builds a beautiful course on their first afternoon; you build a working one, then make it better. Treat today's project as a sandbox, not a masterpiece. Mistakes here are free, undoable, and genuinely how the learning happens β you're not bad at this, you just haven't done it yet.
One reassurance before we go further: Captivate runs natively on both Windows and macOS Win + Mac, and the all-new tool looks and works essentially the same on each. The menus sit where you'd expect for your platform, keyboard shortcuts follow your system's habits (β on Mac, Ctrl on Windows), but the concepts, panels, and steps in this lesson are identical. If you're on a Mac, you're not on some second-class port β you're on a first-class citizen.
π§ A Calm Tour of the Workspace
When your blank project opens, you're looking at the Captivate workspace. It can feel like a lot of panels at once, so let's name the four areas that matter and ignore the rest for now. Think of it like sitting down at an unfamiliar car: you only need to find the wheel, the pedals, and the gearstick to drive β the fancy dashboard buttons can wait.
Figure 1 β All-new Captivate (a simplified mock-up, not a real screenshot): the toolbar, the slide canvas built from component blocks, the device chips, and the Visual Properties panel.
Here are the four things to know:
- The Toolbar (top). Your launchpad for adding things. In the all-new tool you'll spend most time in Slides (add and manage slides), Components (drop in text, images, buttons, shapes, and more), Interactions and Media (later lessons), and Preview (see it as a learner would).
- The Slide Canvas (center). The stage β what a learner will actually see. You build a slide by placing components here. Notice the little device chips beneath it (Desktop, Tablet, Mobile): they let you check how the same slide looks on different screens. We'll live in those in Lesson 7.
- The Slides / Filmstrip list. A running list of every slide in your project, in order. This is how you move between slides, reorder them, and add or duplicate them. A course is just slides in sequence, so this list is your table of contents.
- Visual Properties (right). The most important panel to befriend. Whatever component you have selected, this panel shows its settings β text style, color, size, alignment, and so on. Select nothing, and it shows properties for the whole slide. The golden rule: select first, then change it on the right.
π‘ Adobe moves things around. Adobe updates the all-new Captivate often, so a panel might be renamed, or a tool might sit in a slightly different spot than the mock above. Don't panic if your screen isn't pixel-identical β the concepts (a canvas, a toolbar to add things, a properties panel to change them, a list of slides) are stable. When something has clearly moved, that's your cue to glance at Adobe's current help pages rather than assume you broke something.
π§± The Component/Block Model
Here's the single idea that makes the all-new Captivate click. You don't draw a course β you assemble it from blocks. Every visible thing on a slide is a component (many people call them blocks): a Text component, an Image component, a Button component, a Shape, a Video, and so on. A slide is simply a container that holds a stack of these components in an order.
The best analogy is building with interlocking plastic bricks. You don't sculpt a spaceship out of one lump; you snap together standard pieces. Captivate components are those pieces. And because they're standard, Captivate knows how to do something powerful with them: when the screen gets narrower β say, a phone β the blocks reflow, stacking and resizing to stay readable, instead of spilling off the edge. That automatic reflow is the whole reason the modern tool exists, and it's why we build from components rather than by dragging freeform boxes to fixed pixel positions.
Title"] P --> S2["πΌοΈ Slide 2
Content"] S1 --> C1["π€ Text component
(heading)"] S1 --> C2["π Button component
(Start)"] S2 --> C3["π€ Text component
(body)"] S2 --> C4["ποΈ Image component"] S2 --> C5["π Button component
(Next)"] style P fill:#bbf7d0,color:#1e293b style S1 fill:#bfdbfe,color:#1e293b style S2 fill:#bfdbfe,color:#1e293b style C1 fill:#f1f5f9,color:#1e293b style C2 fill:#f1f5f9,color:#1e293b style C3 fill:#f1f5f9,color:#1e293b style C4 fill:#f1f5f9,color:#1e293b style C5 fill:#f1f5f9,color:#1e293b
Figure 2 β The hierarchy: a project holds slides, and each slide holds a stack of components (blocks).
To add a component, you open Components in the toolbar and choose the type you want β Text, Image, Button, Shape, and friends. Captivate places it on the slide, and it slots into the slide's stack. Because components live in a stack rather than floating at random coordinates, you rarely fuss over exact positions the way you might in a graphics program; you focus on order and content, and let responsiveness handle the rest. (If you've used the older Captivate Classic Classic, this is a real shift β Classic places objects at fixed positions on a timeline; the all-new tool thinks in adaptable blocks instead.)
β Slides vs Components β the two-sentence version
A slide is a screen a learner lands on β one step in the journey. A component is a single piece on that screen β a heading, a picture, a button. You navigate between slides; you build within a slide by stacking components. Get this pair straight and the whole interface stops being mysterious.
Why this matters for real courses and real careers: when a client says "make sure it works on phones," a component-based course already does, because the blocks reflow. When they say "the legal team changed the wording on slide 4," you select one Text component and retype β no re-laying-out the screen. Building from standard, reflowing blocks is what makes modern e-learning fast to build and cheap to maintain, and that speed is exactly what employers are paying an author for.
ποΈ Editing with Visual Properties & Saving
Once a component is on the slide, you shape it with the Visual Properties panel on the right. The rhythm never changes: select the component, then adjust it on the right. Click a Text component and the panel offers font, size, alignment, color, and a style (like "Heading 1" or "Body") β styles are a shortcut to consistent formatting we'll lean on hard in Lesson 6. Click an Image component and you'll see options to swap the picture, add alternative text for accessibility (a habit worth starting now β Lesson 14 makes it a discipline), and adjust the fit.
Double-clicking a Text component usually lets you type straight into it, which feels natural. Buttons work the same way: add a Button component, then use Visual Properties to change its label (say, from the default to "Next"), its color, and β later β what it does when clicked (Lesson 8's interactions). For now, a button that simply reads "Next" and looks the part is a perfect win.
πΎ Saving, autosave, and staying organized
The all-new Captivate saves your project as a single .cpt file β that's the modern format
(Captivate Classic uses .cptx Classic). Use
File β Save early and often; the keyboard shortcut is your friend
(Ctrl/β + S). Captivate also offers autosave as a
safety net, but treat it as a backup, not a substitute β save deliberately when you finish something.
Make a dedicated folder for this course now β something like Captivate Projects / My First
Course β and keep your .cpt file plus any images you import together. Captivate project
files are binary (you can't diff them like a text file), so the pro habit is simple: save often, and once
a project matters, keep dated copies (MyCourse_2026-09-15.cpt). We'll formalize versioning in
Lesson 21, but starting tidy today saves real pain later.
A quick word on Preview. The Preview control (in the toolbar) lets you experience the slide the way a learner will β buttons become clickable, and you can page through. You don't need the full power of it yet (Lesson 7 goes deep on previewing across devices), but do give it a try after you build today; seeing your own slide come alive is the moment this stops feeling abstract.
β οΈ A gentle warning about perfectionism
It's tempting to nudge every component by a pixel and tweak every color on day one. Resist it. In a responsive, component-based tool, "perfect placement" is partly Captivate's job, not yours β and we haven't even applied a theme yet (that's Lesson 6, and it'll instantly make things look polished). Today's goal is a working project you saved, not a finished one. Done beats perfect, every time.
π― Try It: Build Your Hello Course
ποΈ Activity: Your first real project (about 20 minutes)
Objective: Create a new project and build a 2β3 slide mini-course, so the component/block model becomes muscle memory β and so you have a foundation to theme, style, and grow in the lessons ahead. Use the topic you named back in Lesson 1.
Steps
- Open the all-new Adobe Captivate and start a blank project. Name it something like My First Course and save it into a dedicated folder. (β±οΈ 3 min)
- On Slide 1 (your title slide): add a Text component and type your course title. Set its style to a heading in Visual Properties. Add a Button component and label it "Start." (β±οΈ 5 min)
- Add a second slide from the Slides list. On it, add a Text component with a sentence or two of real content, and an Image component (any picture you have β give it alt text while you're there). (β±οΈ 6 min)
- Add a Button labeled "Next" to the content slide. Don't worry about wiring up what it does yet β just get it on the slide and styled. (β±οΈ 3 min)
- Save (Ctrl/β + S), then hit Preview and page through your two slides. Congratulations β that's a course. (β±οΈ 3 min)
π‘ Hint
Stuck finding where to add a component? Look in the Components area of the toolbar and pick the type (Text, Image, Button). If your screen doesn't match the mock exactly, that's fine β Adobe rearranges things between versions; hunt for the word ("Text," "Button") rather than a specific location. If a component lands somewhere odd, remember it lives in the slide's stack β you're adjusting order and content, not chasing pixel coordinates. And if you can't decide on a topic, use "Coffee Machine Basics" or "Office Fire Safety" as a friendly placeholder.
β Activity Complete Whenβ¦
- You have a saved
.cptproject with at least two slides - Slide 1 has a heading (Text) and a "Start" button; slide 2 has text, an image, and a "Next" button
- You previewed the project and paged from the title slide to the content slide
- You can explain, in your own words, the difference between a slide and a component
π― Quick Quiz
Question 1: In the all-new Adobe Captivate, what is a "component" (block)?
Question 2: What file type does the all-new Adobe Captivate save your project as?
π Learning Journal
Keep your Learning Journal going β a note in your favorite app, a doc, or a paper notebook. It's where you turn "I read that" into "I can do that." After each lesson, jot down:
- Key concepts you learned
- Things that clicked for you
- Questions or confusion points to revisit
- Ideas you want to try
- Your progress and how you feel about learning this
βοΈ This lesson's prompt: Describe the component/block model in your own words as if you were explaining it to a colleague who's only ever used PowerPoint. What surprised you about building a slide from blocks that reflow? And how did it feel to preview your very first project β what one thing do you already want to make better?
π Lesson Summary
π Key Takeaways
- You start a course in the all-new Captivate with a blank project; it's responsive by default, so you don't pick a fixed pixel size.
- Learn four workspace areas and ignore the rest: the toolbar (add things), the slide canvas (what learners see), the slides/filmstrip list (your sequence), and Visual Properties (select first, then change on the right).
- The component/block model is the core idea: slides hold a stack of components (Text, Image, Buttonβ¦), and because components are standard, they reflow to fit any screen.
- Save as
.cpt(Classic uses.cptx), save early and often, keep your files organized, and preview to see your slide come alive.
π What You've Accomplished
You just went from reader to builder. You created a real project, met the workspace without being overwhelmed by it, understood the single idea (components that reflow) that the entire modern tool rests on, and saved a working two-slide course to your drive. That's a genuine milestone β the blank canvas isn't scary anymore, because you've filled one.
β Common Questions at This Stage
My screen doesn't look exactly like the mock-up. Did I do something wrong?
Almost certainly not. Adobe updates the all-new Captivate frequently, so panels get renamed and tools move. The concepts β a canvas, a toolbar to add components, a properties panel to change them, a list of slides β are stable. Look for the words ("Text," "Button," "Preview") rather than an exact location, and glance at Adobe's current help pages if something has clearly moved.
Do I need to position every component perfectly?
No β and trying to is a trap in a responsive, block-based tool. Components live in a stack and reflow for different screens, so you focus on order and content, not exact pixel coordinates. We'll make it look polished with themes in Lesson 6 and fine-tune per-device in Lesson 7.
Should I be building my "real" capstone course already?
Build it in spirit, not in pressure. Use your chosen topic so the practice feels real and your work carries forward, but treat these Part 2 projects as a sandbox. You'll formally plan the capstone in Lesson 22 β for now, the goal is fluency with the tool, not a finished product.
π Looking Ahead
Your hello course works, but it's plain. In Lesson 6: Themes, Styling & Brand, you'll apply a theme and set brand colors and fonts β and watch your bare-bones project transform into something that looks professionally designed in just a few clicks.
β Before the Next Lesson
- Make sure your two-slide project is saved in a dedicated folder
- Write this lesson's journal prompt β explain the block model in your own words
- Optional: add a third slide and one more component, just to build confidence with the flow
π Additional Resources
- Course Glossary β every term in plain language (see Component, Slide, and .cpt)
- Quick-Reference Cheat Sheet β including the component/block quick list
- Captivate Help & Support β official documentation for the all-new tool
π Encouragement for the Journey
You built a course today. Not a mockup, not notes β an actual project saved to your drive, with slides and components and a button that says "Next." Everything from here is just more of what you already did. The hardest slide you'll ever make is the first one, and it's behind you now. Onward.