DEV Community

Cover image for How to Create Tutorial Videos for Your Laravel Admin Panel (Filament, Nova, Backpack)
Amer
Amer

Posted on Edited on Originally published at dashcast.net

How to Create Tutorial Videos for Your Laravel Admin Panel (Filament, Nova, Backpack)

You built the admin panel. Now the client, the new support agent and the finance team all ask the same questions: where do I approve an order? How do I export last month's invoices?

A written guide helps, but a 40-second video answers faster. The problem is that every deploy changes a screen, and a recorded video is outdated the moment it ships.

This post shows a workflow that avoids re-recording: plan the lessons by role, write them as scripts, and render them again after each release. The examples use Filament, but the same steps work for Nova, Backpack or any panel with a login.

Why scripts instead of screen recordings

A screen recording is a one-off. If a button moves, you record the whole thing again.

A script describes the steps (open this page, highlight that field, click this button) and the narration. A browser performs the steps and films them. When the UI changes, you fix one line and render again.

That also solves three practical problems:

  • Customer data. You film a staging copy with demo data, never production.
  • Your voice. Narration comes from text, so anyone can fix a sentence without re-recording audio.
  • Languages. The same script can be narrated in another language.

Step 1: Plan the course by role

Don't write one long "tour of the panel". Write short lessons, one task each, grouped by who needs them.

Role Example lessons
Every user Sign in, change your password, find a record
Editor Create an order, attach a file, add a note
Manager Approve an order, run a monthly report
Admin Add a user, set permissions

A lesson should end when the task ends. If it needs more than about two minutes, split it.

Step 2: Prepare a staging copy

The browser needs something it can open, so you need a staging copy that is reachable from the internet. Prepare it carefully:

  • Seed realistic demo data. Empty tables make poor tutorials.
  • Create one test user per role, with a simple password.
  • Reset the data before each rendering session.
php artisan migrate:fresh --seed
Enter fullscreen mode Exit fullscreen mode

Because this copy is public, protect it. Use test accounts only, never real customer records, and consider restricting access (for example, by IP or a basic-auth layer in front of the panel) once the videos are rendered.

Step 3: Generate the lessons

You have two practical options:

  1. Let your coding assistant write them. If you already work with Claude Code or Cursor, ask it to read your routes and resources and write a lesson per task. It already knows the panel, so the selectors and steps tend to be accurate. You import the result as a series.
  2. Let an AI write them from a link. Give a tool the panel URL, a test login and one sentence about what to show, and it drafts the lesson and checks each click.

In both cases, read the output. A lesson that clicks the wrong button teaches the wrong thing, and nobody reviews that for you.

Step 4: Polish and render

Before rendering, adjust the details that make a video easy to follow:

  • Zoom into the part of the screen that matters.
  • Highlight the field or button being explained.
  • Blur anything that should not be seen.
  • Reword the narration so it matches how your team talks.

Then render the MP4 and the subtitles, and put them where people already look: a "Help" link in the panel, the client handover document, or your internal wiki.

Step 5: Keep them current

This is the step that makes the whole approach worth it. After each deploy, run a check on the lessons to see which steps no longer find their target, fix only those, and render only those lessons again.

A few habits that help:

  • Name each lesson after the task ("Approve an order"), not the screen.
  • Keep the demo data consistent between lessons.
  • Re-check after any release that touches the UI.

Common questions

Can I film an app running on localhost?
Not with a cloud service, because it cannot reach your machine. Use a staging copy that is publicly reachable.

What about two-factor login?
Create test accounts without 2FA on staging, or use a dedicated test flow for videos.

Does my code leave my machine?
Your coding assistant reads your project the way it always does, and you should check what it sends to its provider. The lesson file you import contains steps and narration, not your source code.

A tool for this

I used DashCast for the workflow above. It renders lessons with a headless browser, adds an AI voice and subtitles, and can re-render a lesson after you fix a step. There is a free tier with 10 minutes of video, and paid plans start at $9 a month.

If you build tutorials for your own panel, I would like to hear which role gave you the most questions to answer.

Top comments (0)