added video

src/content/docs/project/index.mdx

@@ -3,5 +3,16 @@ title: Overview
 ---
 
 import DirectoryLinks from '/src/components/DirectoryLinks.astro';
+import projectOverview from "./images/project-overview.mp4"
+
+<video width="960" autoplay muted playsinline controls>
+  <source src={projectOverview} type="video/mp4" />
+</video>
+
+[Tests](https://docs.testomat.io/project/tests) is where your test cases are - suites, folders, steps, and the editor you write them in. [Runs](https://docs.testomat.io/project/runs) is where those tests are executed, by hand or from CI, and where the results are. [Plans](https://docs.testomat.io/project/plans) let you fix the scope once and launch it as a run again and again. [Import and Export](https://docs.testomat.io/project/import-export) brings tests in from your code or another tool, and takes them back out.
+
+Once results appear, [Analytics](https://docs.testomat.io/project/analytics) shows what keeps failing and which tests are flaky, [Defects](https://docs.testomat.io/project/defects) lists the tracker issues raised against those failures, and [Pulse](https://docs.testomat.io/project/pulse) records every change to a test, suite, plan, or run, so you can see who did what and undo it.
+
+[Steps and Snippets](https://docs.testomat.io/project/steps-snippets) keep repeated steps in one place, and [Comments and Notifications](https://docs.testomat.io/project/comments-notifications) keep the discussion on the test itself.
 
 <DirectoryLinks directory="project" />

src/content/docs/project/tests/index.mdx

@@ -3,10 +3,16 @@ title: Overview
 ---
 
 import DirectoryLinks from '/src/components/DirectoryLinks.astro';
+import testsOverview from "./images/tests-overview.mp4"
 
-The **Tests** page is where your test cases live. You can write them by hand, import them from your code, or do both in the same project.
-This section explains how that works: how a project stores tests, how suites and folders fit together, how you write and edit a test, and what to do once the project gets too big to edit tests one at a time.
-Start with the project type. Every project is either **Classical** or **BDD**. You choose it when you create the project, and you can't change it later. That one choice decides which editor you get, where your tags are kept, and how your tests connect to your code.
-Not sure which type you have? Start with Classical vs BDD.
+<video width="960" autoplay muted playsinline controls>
+  <source src={testsOverview} type="video/mp4" />
+</video>
+
+The **Tests** page is where your test cases are. You can write them by hand, import them from your code, or do both in the same project.
+This section explains how that works: how a project stores tests, how [suites and folders](https://docs.testomat.io/project/tests/suites-and-folders) fit together, how you [write](https://docs.testomat.io/project/tests/create-a-test) and [edit a test](https://docs.testomat.io/project/tests/edit-test-steps), and what to do once the project gets too big to [edit tests one at a time](https://docs.testomat.io/project/tests/bulk-test-selection).
+
+Start with the project type. Every project is either [**Classical**](https://docs.testomat.io/project/tests/classical-test-case-editor) or [**BDD**](https://docs.testomat.io/project/tests/bdd-test-case-editor). You choose it when you create the project, and you can't change it later. That one choice decides which editor you get, where your tags are kept, and how your tests connect to your code.
+Not sure which type you have? Start with [Classical vs BDD](https://docs.testomat.io/project/tests/classical-vs-bdd).
 
 <DirectoryLinks directory="project/tests" />

src/content/docs/tutorials/index.mdx

@@ -3,23 +3,12 @@ title: Overview
 ---
 
 import DirectoryLinks from '/src/components/DirectoryLinks.astro';
+import tutorialsOverview from "./images/tutorials-overview.mp4"
 
-A tutorial is a short, step-by-step guide that walks you through one real task in Testomat.io from beginning to end. You follow along, click as you go, and by the end you have actually done the thing, not just read about it. No prior knowledge needed. If you are new, start with the first one and work your way down.
+<video width="960" autoplay muted playsinline controls>
+  <source src={tutorialsOverview} type="video/mp4" />
+</video>
 
-- **Manual Testing - Classic** - create your first project, add test cases, run them by hand, and see the results.
-- **Manual Testing - BDD** - for teams that write tests as Given / When / Then scenarios.
-- **Working With Plans** - build a plan once, then launch it as a run again and again.
-- **Working With Jira** - connect Testomat.io to Jira to link tests to issues. Report bugs without leaving your run.
-- **Using AI in Testing** - let AI create test data, summarize a suite, and answer questions about tests.
-- **MCP - Connect Claude** - paste one connector URL into Claude and sign in with your Testomat.io account.
-- **MCP - Connect ChatGPT** - do the same in ChatGPT, with a custom MCP server plugin and OAuth.
-- **MCP - Connect with a Config File** - connect Cursor, Claude Desktop, or OpenCode by adding an MCP config file with your project token.
-- **Interacting via API** - pull tests and create runs from code.
-- **Set Up Read-Only Access** - give a client a safe way to look at your tests without changing anything.
-- **Migration from TestRail** - already have tests in TestRail? Bring them into Testomat.io.
-- **Migration from Qase** - moving from Qase? Export a CSV and bring your tests to Testomat.io.
-- **Playwright** - report Playwright results to Testomat.io.
-- **Java Integration** - report JUnit, TestNG, or Cucumber JVM results to Testomat.io.
-- **WebdriverIO** - report WebdriverIO results to Testomat.io.
+A tutorial is a short, step-by-step guide that walks you through one real task in Testomat.io from beginning to end. You follow along, click as you go, and by the end you have actually done the thing, not just read about it. No prior knowledge needed. If you are new, start with the first one and work your way down.
 
 <DirectoryLinks directory="tutorials" />