Month: July 2026

If your Adobe Captivate Classic project looks clean on desktop but falls apart on a phone, this guide to Fluid Boxes will fix that fast.

Fluid Boxes are Captivate’s responsive layout system, and once you understand how containers, wrapping, and alignment work together, you can build slides that behave predictably instead of fighting you.

Start With A Responsive Project

Fluid Boxes only work in a responsive project. Open Captivate and create a Responsive Project, not a blank non-responsive project. If you already built slides in a non-responsive file, you cannot simply turn Fluid Boxes on later. You will need to rebuild those slides in a responsive project.

After the project opens, go to the first content slide and switch to the Fluid Boxes view if needed. Captivate may add Fluid Box placeholders automatically. Think of each box as a container that controls where objects can live and how they resize.

Build Your First Fluid Box Layout

Start simple. Insert a vertical parent Fluid Box so the slide is split into stacked sections, such as a header, content area, and footer. Then select the middle section and divide it into horizontal child Fluid Boxes if you want side-by-side content.

This parent-child structure matters. A parent box controls major layout areas. Child boxes control the objects inside those areas. If your slide gets messy, it is usually because too many objects were dropped into one box without a clear structure.

Add Content The Right Way

Drag text captions, images, and buttons into the correct Fluid Box, not just onto the slide. When the object is inside the box, Captivate highlights the container. That visual cue matters because objects that are not properly assigned may overlap or resize in unexpected ways.

Use one main object type per box when possible. For example, place a heading in one box and an image in another. You can mix objects, but dense boxes are harder to control on smaller screens.

Set Alignment And Distribution

Select a Fluid Box and use the Properties Inspector to control alignment. You can center objects vertically or horizontally, justify them to edges, and adjust padding. Padding is one of the fastest ways to make a slide look professional because it keeps content from touching box edges.

If objects appear cramped, increase padding before changing object sizes. If objects are unevenly spaced, check the distribution setting for the box instead of manually moving items. Manual positioning works against the Fluid Box system.

Control Resizing And Wrapping

Here is the part most developers miss in a guide to Captivate Fluid Boxes: wrapping controls responsiveness more than object size does. Select the Fluid Box and decide whether objects should wrap to the next line as the screen narrows. Wrapping is useful for groups of images or buttons. If wrapping is off, objects keep trying to fit on one line and may become too small.

Also review whether an object can grow or shrink. For logos and icons, lock the aspect ratio so they do not distort. For text-heavy captions, allow enough space for expansion. A layout that works on desktop can break on mobile if the text box cannot adapt.

Use Static Fluid Boxes When Needed

Not every object should resize. If you have a banner, logo area, or navigation strip that should keep its shape, consider setting that box to Static. A static box gives you more control, but there is a trade-off. Too many static boxes reduce flexibility on smaller screens.

Use static boxes only when consistency matters more than adaptability. For most body content, regular responsive Fluid Boxes are the better choice.

Preview Before You Keep Building

Preview early, not after ten finished slides. Use the device preview options and test desktop, tablet, and phone sizes. Watch for three common issues: text that wraps awkwardly, images that scale too aggressively, and stacked objects that become too tall.

When something fails, fix the container first. Most layout problems are caused by the box settings, not the object itself.

Troubleshoot Common Fluid Box Problems

If objects overlap, confirm they are inside separate boxes or that wrapping is enabled. If text is cut off, allow the caption more vertical space or reduce the amount of text. If a slide feels unstable across devices, simplify the hierarchy by using fewer nested boxes.

A good rule is to build the slide in broad regions first, then place content, then test responsiveness. That order saves time and gives you a layout you can trust.

Fluid Boxes work best when you stop treating slides like fixed-position canvases. Build with containers, test often, and let the layout system do its job. That is how you create responsive projects that hold up under real-world pressure.

If your Storyline slide has three layers, four triggers, and a pile of duplicate objects just to show feedback, this is the moment to fix it. The easiest answer to why use storyline states is simple: states let one object behave like many objects, which makes your project easier to build, edit, and troubleshoot.

Why Use Storyline States

In Articulate Storyline 360, a state is a different appearance or condition for the same object. Instead of copying a button five times, you can give one button multiple states such as Normal, Hover, Visited, Selected, or Disabled. You can also create custom states for feedback, reveal interactions, and click-to-explore content.

That matters because fewer objects usually means fewer triggers, less clutter on the timeline, and less time spent hunting for the thing that broke.

Create A Simple State-Based Interaction

Start with a slide that contains a button or image. Select the object, go to the States panel, and click Edit States. You will see built-in states first. Click New State if you need a custom one.

For example, create a custom state named Correct. While editing that state, change the object’s fill color, add a checkmark, or insert text that says Nice work. When finished, click Done Editing States.

Now add the behavior. Create a trigger that changes the state of the object to Correct when the user clicks it. Preview the slide and test it. You now have feedback without adding a new layer or a duplicate object.

Use States Instead Of Duplicate Objects

A common mistake is stacking similar objects on the same slide and showing or hiding them with triggers. That works, but it gets messy fast. If the only thing changing is appearance, use states instead.

Here is a practical example. Suppose you want a character to react when learners click different response options. Keep one character on the slide and create states such as Happy, Concerned, and Neutral. Then add triggers that switch the character to the matching state when each option is clicked.

This approach is faster to maintain. If you need to move the character, resize it, or update alt text, you do it once.

Add Hover And Visited Feedback

States are especially useful for navigation and exploration. Select a button, edit the Hover state, and change the color or add a glow. Then preview the slide. Learners instantly get visual feedback that the object is interactive.

Next, customize the Visited state. After a learner clicks the object, Storyline can automatically show that it has been visited. This is useful for tabs, hotspots, and menu items because learners can see what they have already explored.

If needed, add a trigger to change the object to Disabled after it is clicked. That prevents repeated clicks and keeps the interaction controlled.

Know When States Are Not Enough

States change an object’s appearance. They do not replace every use of layers. If you need separate audio, complex animations, or multiple independent objects appearing together, a layer may still be the better choice.

Use this rule: if one object is changing, use states. If the whole slide experience is changing, consider layers.

Build Faster And Edit With Confidence

If you have been asking why use storyline states, the real benefit is production speed with fewer moving parts. Your timeline stays cleaner, your triggers stay simpler, and your edits take less time under deadline.

In real-world Storyline 360 development, that is what makes you faster and more dependable. Start with one slide in your current project. Replace one duplicate object or one unnecessary layer with states, preview it, and compare the result. You will likely not go back.

The best Storyline files are not the ones with the most tricks. They are the ones you can open a month later and still understand in minutes.

Need to reuse a lesson you’ve already created? Instead of rebuilding it from scratch, copy the entire lesson to another Rise course in just a few clicks.

If you develop Articulate Rise courses regularly, chances are you’ve created lessons that you’d like to reuse. Maybe it’s a course introduction, a knowledge check, a company policy, or a standard resources page.

While you could recreate the lesson—or even copy blocks one at a time—there’s a much faster option. Rise lets you copy an entire lesson from one course to another, preserving all of the text, images, interactions, and formatting.

It’s a simple feature that can save a tremendous amount of development time.

Why Copy Lessons?

Copying an entire lesson is ideal when you have content that appears in multiple courses, such as:

• Course introductions
• Learning objectives
• Navigation instructions
• Accessibility information
• Knowledge checks
• Company policies
• Resource pages
• Contact information
• Course conclusion pages

Instead of rebuilding these lessons each time, copy them and make any minor edits needed for the new course.

How to Copy a Lesson to Another Course

Copying a lesson takes less than a minute.

1. Locate the lesson you want to copy.
2. Click the three-dot menu next to the lesson.
3. Choose Copy to Another Course.
4. Select the destination course.
5. Open the destination course.
6. Drag the copied lesson to its desired location in the course outline.

That’s all there is to it.

What Gets Copied?

When you copy a lesson, Rise copies everything in it, including:

• Text
• Images
• Videos
• Interactive blocks
• Knowledge checks
• Buttons
• Flashcards
• Labeled graphics
• Accordions
• Process interactions
• Formatting

The copied lesson becomes part of the destination course, so you can edit it without affecting the original.

Create Your Own Lesson Library

Here’s a productivity tip: create a dedicated Rise course that serves as your personal lesson library.

Populate it with lessons you use repeatedly, such as:

• Welcome pages
• Course introductions
• Learning objectives
• Navigation instructions
• Accessibility information
• Frequently used interactions
• Knowledge checks
• Resource pages
• Course conclusion pages

When you begin a new project, simply copy the lessons you need into the new course and arrange them as desired. Over time, you’ll build a library of polished, reusable content that can dramatically speed up course development.

Final Thoughts

Copying lessons between Rise courses is one of the easiest ways to eliminate repetitive development work. Instead of recreating an entire lesson—or copying assets one at a time—you can move complete lessons into another course in seconds.

If you routinely build multiple Rise courses, this feature is well worth adding to your workflow. You’ll spend less time rebuilding content and more time creating engaging, effective learning experiences.

Rise Training

If you need to learn Rise fast, check out my 2-hour virtual instructor-led Rise class.

If you need to show learners exactly where to click, how to enter data, and what happens next, knowing how to create software simulations is one of the fastest ways to build training that actually gets used. The trick is not recording everything. The trick is recording the right task, then editing it into a clean demo, a guided practice, and a scored assessment.

Choose The Right Task First

Before you open any authoring tool, pick one business task, not an entire application. Good simulation topics are short and measurable, such as creating a customer record, submitting an expense report, or updating a ticket status.

Write the task as a simple sequence of steps. Then clean up your screen before recording. Close chat tools, hide notifications, increase display scaling only if text is hard to read, and decide whether you want captions, highlight boxes, or both. This prep work saves far more time than trying to fix a messy capture later.

How To Create Software Simulations In Storyline 360

In Articulate Storyline 360, start a new project and choose Record Screen. Select the application area you want to capture and record the task at a steady pace. Do not rush. Small pauses between actions help Storyline create cleaner step slides.

When the recording ends, import it as step-by-step slides instead of a single video. Storyline can generate view mode, try mode, and test mode. For most projects, create all three, then delete what you do not need.

View mode works for demonstration. Try mode adds prompts so learners can practice. Test mode removes hints and scores the interaction. That structure gives you three deliverables from one recording.

Edit The Slides, Not Just The Recording

Open each slide and tighten the timing. Replace vague captions like Click Here with action-based text such as Click Submit to save the request. Check every hotspot. Auto-generated objects are fast, but they are not always precise.

If a field requires text entry, confirm the typing box is large enough and the acceptable answer matches what the learner should enter. If multiple answers should count as correct, add alternate text entries. Also verify the tab order and focus states if keyboard access matters in your environment.

Build The Same Workflow In Adobe Captivate

If you are using Adobe Captivate, record the task in demonstration, training, or assessment mode. Captivate follows the same logic as Storyline 360, but the editing approach is slightly different. You will typically work with click boxes, text captions, highlight objects, and success or failure actions on each slide.

After recording, review every slide for timing, cursor path, and object placement. Captivate often captures more detail than you need, which is useful but can clutter the lesson. Delete extra captions and shorten long pauses. A shorter, cleaner simulation usually performs better than a perfect but slow replay of the entire process.

Add Practice Without Frustration

A software simulation should feel guided, not punishing. In practice mode, give learners enough support to succeed the first time. Use hint captions, visual emphasis, and clear feedback when they click the wrong area.

For assessment mode, be stricter. Remove hints, limit attempts, and score only the steps that matter. If your real-world task allows variation, your simulation should too. For example, if users can reach the same result from two menus, it depends whether you are teaching the exact path or the business outcome.

Test Like A User, Not A Developer

Previewing is not enough. Publish the simulation and complete it as a learner would. Test mouse clicks, text entry, slide timing, feedback layers, and score reporting. Pay close attention to steps that involve scrolling, small icons, or dynamic menus. Those are common failure points.

If the simulation will be viewed in an LMS, test it there as well. A simulation that works locally can behave differently after upload, especially when completion depends on quiz reporting or browser settings.

Keep The Final Version Tight

The best answer to how to create software simulations is usually this: record once, edit aggressively, and publish only what supports the task. Learners do not need every screen. They need a fast path to correct performance.

When your simulation shows the task clearly, lets learners practice safely, and confirms they can do it on their own, you have built more than content. You have built something people can rely on when the work is real.